Search results

I am using cPanel since 10 years and I never will use anything else.

WHM/cPanel has a better protection for such attacks: https://trycpanel.net/cphulk.html

I'm not up2date with CyberPanel, but you should check if fail2ban is availabe for CyberPanel. There are some discussions about it in CyberPanel forum. To prevent brute force attacks against SSH LiteSpeed isn't responsible.

Which control panel do you use?

This is for everyone who thinks about how to get faster pagespeed. In upcoming Chrome versions Google will place a hint in Chrome browser if a requested page is slow or fast based on Chrome User Experience Report. Webmasters should already know that if they check their Google Search Console...

@Andrey Download attached test.txt, rename it from test.txt to test.php. Upload test.php to you domain_root, request it in browser and post what will be displayed.

Andrey, if you don't do what I suggest I can't help you, sorry. I am out here....

Either Journal 3 logic or LiteSpeed logic (code) must be changed, but disable Pagespeed, disable inline styles, disable mobile view and try mobile friendly test again. I can't believe that Journal 3 has a device detection. Journal 3 uses media queries for different screen sizes/resolutions, but...

Possible reasons: - Journal 3 and LiteSpeed cache plugin may have differently working logic to detect devices - You have Pagespeed active. Pagespeed has no function to detect devices - You have still inline styles enabled - You missunderstand what a algorithm for device detection is. - wrong...

You only have to uncomment it if your app has PHP function to detect kind of device. As I know Opencart has no such device detection. Mobile View in OpenCart will be handled by media queries and not by device detection. Btw. disable Pagespeed. Pagespeed doesn't work correctly and forces too...

What you need is not PHP related. Again, you need to change "Connection Timeout " in LiteSpeed WebAdmin Console and nowhere else! Ask you provider what to do. Or try this: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:run-without-timeouts?s[]=connection&s[]=timeout

You need to increase "Connection Timeout" that can be changed in LiteSpeed WebAdmin Console. If you cannot access to LiteSpeed WebAdmin Console and if you have "Shared Hosting Server" ask your provider.

Do you have access to LiteSpeed WebAdmin Console?

LiteSpeed with Lscache plugin offers a webserver based cache engine. LiteSpeed cache plugin (function) is only the control panel for the webserver cache. W3 plugin and all other cache plugins are PHP based, so such plugins cannot offer a performance like LiteSpeed. If you want "Warp Speed"...

To combine and minify CSS doesn't solve it and hasn't something to with inline css. Disable inline css switch! If you don't get answer from support regarding your issue with cache on manufacturer pages, use OpenCart forum. There are a lot of users they also use LiteSpeed cache.

Cache reduces time to generate the content before it can be sent to the client. Cache doesn't reduce data. If you embed all your styles (css) inline instead of storing it in css files, styles cannot be cached in browser cache and forces to load all data foreach page request again, again and...

Get the answer for your manufacturer caching problem from support and if you want I tell you why you are wrong how you use LiteSpeed cache. In my mind you should solve this wrong use first before you try to get your manufacturer pages get cached.

I don't know the answer to your question, but the way you use LiteSpeed cache doesn't make sense. If you embed all your styles inline it will increase page load time dramatically. You should have less than 100ms for loading main document and not > 1500ms!

Okay, I start from the end. -c parameter works for me if I have defined a vary cache rule based on site's cookie, so it helps for me or whatever you mean with "help". Please explain if a missunderstand this question. -c parameter isn't the same like setting an extra cookie for specific vary...

There are more improvements they can easily added. For example if someone uses cookies and have vary cache rules defined in .htaccess. Add --cookie "cookie_name=" //with double quotes to CURLRESULT define, but take care of "=" suffix. Without this suffix cache rule will not work.