Search results

Sorry, I don't have a VCL for Wordpress Varnish configuration which I use. Please see Configuring Varnish for WordPress for the VCL. It might work for you. Make sure to change "backend default" and the "acl purge" as I have described in my post. I'm not sure about the "The plain HTTP request...

Please run bin/magento setup:upgrade

Have you ran the bin/magento setup:install with all the info required? It seems your Magento 2 installation is not able to connect to MySQL. Please correct the MySQL DB info in app/etc/env.php

Do we have anything in the logs related to this?

Please remove the configuration you have done such as "disabled the symbolink" try again. Usually, with Plesk and Magento 2, there is no need of additional configuration such as permission or Apache and Nginx settings.

Please see my post - Input - Magento 2 | Plesk | Varnish Setup in a Docker This for Magento 2, but please see if this post help you.

Have you ran the installation command? (bin/magento setup:install) https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/composer.html?lang=en

How about if we try find the directory sizes and go from there? # find / -maxdepth 1 -mindepth 1 -type d -exec du -h --max-depth=0 {} \;

Dave is right. Sounds like there is some other issue going on. FYI, it is possible to add the subdomain as a separate subscription then assign a dedicated IP, separate system user etc..

Glad to hear that! ) Yes, I think #journalctl will help. I had a similar issue recently caused by Actomic Mod_Security. The Apache stopped working when the AUM updating the ruleset but your issue might be totally different.

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