Search results

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.

In addition to Peters reply, have you tried? # journalctl -xe and # journalctl -u httpd.service might help to find out the reason for Apache stopped.

Is this SERVER.B.DOMAIN behind any proxy? such as CloudFlare? Usually the CloudFlare keeps this port 8080 open while the rest such as 465 closed.

dig @8.8.8.8 yourdomain.tld It works. Doesn't seems to be blocked.

Do you have this ftpuser2 in the psa database? SELECT * FROM `sys_users`; Tools and Setting > Database Servers > Select the Plesk Database Server > Webadmin (the small icon) > psa database > sys_users table

I tried to recreate this issue but couldn't. CentOS Linux 7.9.2009 (Core) Version 18.0.56 Update #4

Once the Migration Tool complete the task, There is no connection between the new server and old server. On the new server, You can click on the "Finish Migration" (It would be a good idea to take a full server backup and save it locally from the old server before deletion.)

We can mark this as resolved for now.

Please note complete DNS propagation can take up to 48 hours. Also your PC/Browser might using your local DNS cache.

In "tiredofit/freescout" settings, try 127.0.0.1 for DB_HOST

Thank you @Peter Debik. Currently this sever is running Plesk 18.0.57 #2. This issue only happened twice on one server out of all my server running Atomic Mod Security. Only similar post I found is Resolved - ModSecurity (once again)