Search results

Personally, I wouldn't recommend this. There is a better chance of IP and the domain name being blacklisted across many blacklists. Please see - How do I send an email blast without getting blacklisted? This explains some guidelines to follow. I'd recommend to use a service such as MailChimp...

Try, sub vcl_recv { if (req.http.X-Forwarded-For) { set req.http.X-Real-IP = req.http.X-Forwarded-For; } else { set req.http.X-Real-IP = client.ip; } } In your vanish VCL.

Sorry.. I couldn't help you with this. Please see my post - Instruction - How to Install Magento 2.4 on Plesk for complete installation. I'm not sure how the Softaculous install Magento. We use Plesk for many Magento 2 installations and the Plesk has made this process really easy to do.

Ok. The Plesk Default Page might be a different issue. Would you be able to run, #plesk repair web yourdomainname.tld as root? Magento 2 Document Root should be httpdocs/pub. Sorry, It seems I wont be able to help you without actually looking into this server/M2 installation.

Not httpdocs, It should be httpdocs/pub

I'm wonder why do we get the "main.CRITICAL: Can't create directory" since we have set the directory and files to 777. Also Have to set the document room to httpdocs/pub ? (This is unrelated to the File Permission issue).

Could you please send me a ls -l of within /var/www/vhosts/example.com/commerce.example.com/ I'm wonder if we have to change the bash user to eg - www-data before running the Magento 2 commands in Softaculous. I haven't used Softaculous. su -s /bin/bash www-data

Very strange. What is in the system.log now? Please check if the following modules are loaded in Apache : mod_env, mod_version

So you have a file permission issue. I'm not sure about the File and Directory permission required by Softaculous. We set the files and directories to 777 for testing. Within this directory, /var/www/vhosts/example.com/commerce.example.com/ Run, chmod -R 777 . Then, bin/magento...

Also try to correct the directory/file permission. find * -type d -print0 | xargs -0 chmod 0755 find . -type f -print0 | xargs -0 chmod 0644 chmod u+x bin/magento Then, bin/magento setup:upgrade bin/magento deploy:mode:set developer

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.