Search results

Final words. You sound like ... [redacted]

Which part you are confused about? a one click away? So you are complain about one mistake I have made for the reply? This forum replies are not paid work! Also it should have worked without the 'http_cache_hosts" Just learn how to ask for support from the community in a forum. Dont talk...

This is completely wrong! Why would you request NGINX to PURGE /? This is nothing to do with NGINX. If you followed my instructions in the "Input" thread regarding the Varnish Docker for Magento 2, You do not have to specify http_cache_hosts in env.php. In my instructions, I have mentioned it...

By looking at this Litespeed installation guide - Configuring LiteSpeed Web Server with Plesk | LiteSpeed Documentation As Peter mentioned, I also agree It would be ideal to reinstall the server and restore from a backup. You can try to change the PHP Handlers to FPM etc.

How about if you try to disable HTTP/2, #plesk bin http2_pref disable

https://support.plesk.com/hc/en-us/articles/12377869111319--How-to-change-default-location-of-mailboxes-in-Plesk-for-Linux

What is the actual error when you are trying to login to the server?

# plesk repair web domainname.tld should have fixed this issue as this command re-writes the default configuration files for the vhost using Apache and NGINX. Do you have any additional settings in Additional Apache directives or Additional nginx directives? Also please check the .htacess file.

In this case what is the purpose of call a vhost by IP? This is why use different ports. Actually its the Matches the PURGE request. I can confirm that instructions should work as it is working across many of our Magento 2 servers. Yes, It works with Plesk with a single IP.

https://www.digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-22-04

Please see - Instruction - How to Install Magento 2.4 on Plesk

Did you run? # plesk repair web domainname.tld Also what is the error now?

Eg - /etc/host 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 127.0.0.1 guest ::1 guest 127.0.0.1 SERVER.B.DOMAIN DOMAINNAME ::1 SERVER.B.DOMAIN DOMAINNAME 172.17.0.3...

Usually this is 127.0.0.1 (localhost)

No problem at all. Glad to hear your issue is solved.

Sorry, I have misunderstood issue. This is the Plesk extension/composer not related to the Wordpress.

Please go to Wordpress Toolkit and Detach this domain.

Please try, If you have completely removed the LiteSpeed, have you re-enabled the NGINX? Once re-enabled the NGINX, Please restart both NGINX, Apache and any FPM services in use under Tools & Setting > Services Management. Then, # plesk repair web domainname.tld

Please try to add under [mysqld] in my.cnf, innodb_buffer_pool_size = 256M and restart the MariaDB.

Please check if you have SERVER.B.DOMAIN in Tool & Settings > Server Settings. How about if you ping SERVER.B.DOMAIN from the SERVER.B.DOMAIN server itself. Do you receive a response? To me this sounds like SERVER.B.DOMAIN not resolving to a IP within the server itself. Please check.