Search results

It sounds like nothing to do with LiteSpeed since it running with its own service. If you curl it from the server with http(s)://127.0.0.1:3000, does it work?

Thanks for sharing

Hi, Did you also add the domain mapping to the port 443 listener? Have you applied the new domain to the WordPress site? What's the page return content if you visit the new domain, a litespeed 404 error or?

Good to know that.

Multiple cache systems may cause such an issue. In your case, it seems you have Ezoic CDN cache enabled, please use either Ezoic cache, or LSCache.

Check this one https://stackoverflow.com/questions/63496078/php-what-is-lsphp

LSPHP has LiteSpeed API included in order to work with OpenLiteSpeed.

If it's blocked by OLS, you should see it in the error log. If it's something else, then I am not sure.

Good to know it works.

Do you have any other CDN service active at the moment, e.g. Cloudflare?

Not pretty sure actually. Please try to restart the LSWS from the console (systemctl restart lsws), then restart the browser and try again. You can also monitor the admin log "tail -f /usr/local/lsws/admin/logs/error.log" see if there's any hint from there.

I feel that did not explain the issue though.

Do you have a php info page to verify the memory size is large enough?

I remember the behavior of switching web server is, that after switching to the LSWS, then openlitespeed will be uninstalled, so downgrade OLS should not work.

Please try to install the repo again, and see if it helps. sudo wget -O - https://repo.litespeed.sh | sudo bash More https://docs.openlitespeed.org/installation/repo#install-the-litespeed-repository

I don't think CyberPanel has built-in any method to allow you to switch back and forth between OLS and LSWS. Maybe that's the reason you got 521 issue. Please reinstall CyberPanel. or use pure openlitespeed this time.

mm, I am not a CSF export, you might also want to post the question on their forum.

Hope this helps https://forum.configserver.com/viewtopic.php?t=6998

So I guess you are talking about the domain https://stake.tycoondefi.com/ has the cert issue. In the Virtual host mappings, please update Domains "stake.tycoondefi.com stake.tycoondefi.com/admin" to "stake.tycoondefi.com" and it should start working. Because the current "stake.tycoondefi.com...

ok, updated the title.