Search results

So it turns out that you're inside a Docker container? And that the whole question is about serving a website via Nginx? Is Proxy mode on or off in the web server settings? If it is off and you are serving the site form Nginx, you need to select the Nginx PHP handler instead of the Apache PHP...

Make sure that index.php is indeed spelled index.php, not 1ndex.php, Index.php, index.PHP or anything similar. Also make sure that your /httpdocs is owned by your webserver user, group psaserv and that it has permissions 0750.

THIS!

A restart of sw-engine is immediate, there is no wait. What's shown in /var/log/sw-cp-server/error_log and sw-engine.log at the time of failure?

Forwarded messages are not DKIM signed. GMX and other United Internet freemail services are famous for temporarily banning IPs from where excess traffic is seen. There is nothing one can do about it and GMX are nit interested in changing that either. It's nit at all DKIM issue. That's just...

Removal is easy, simply click on "phpMyAdmin" in the webspace control panel "Databases" menu, then go to the table and edit the structure. Re-creating the index should also be easy, because in phpMyAdmin you can simply do this by GUI. The only thing you'll need to know is what the index was...

"Web Application Firewall" only affects web server traffic (ports 80, 443). It does in no way influence database port 3306. Yes, contacting your hosting company might help.

Proper DKIM configuration is only required for web.de and GMX if the incoming traffic from your IP is high (e.g. if you are sending mass mails to their services). As I understand from the documentation of Postfix and other sources, outgoing messages are signed when it is attempted to transmit...

Let's first get the terminology clear. With "web server" you probably mean the host computer. Let's call it "host" or "host computer", because the "web server" opposed to "mail server", "ftp server", "database server" are just separate services (software) on the host computer. These do not have...

The web server message is unrelated to the ODBC connection issue. Discard the web server aspect. If you cannot connect to port 3306 while on your server the database server is listening, make sure that no firewall is blocking port 3306 on your server. When I test your IP from my computer, I...

With Postfix and OpenDKIM, the DKIM signature is added at the moment the message is sent via the smtp transport, not when the message is queued. Postfix sends the message to OpenDKIM via milter during the "smtp" delivery phase. OpenDKIM signs the message and passes it back to Postfix. The signed...

The index must be removed and recreated. If this doesn't work (e.g. maybe the index cannot be removed, because it is corrupt), the whole table must be removed and recreated (from a backup peferrably).

WP Toolkit can handle installations in subdirectories, but it is a bad practice, because if an .htaccess file exists in any folder above the Wordpress installation, such as in your case in / instead of /wordpress-here, the directives in that .htaccess file will influence all subdirectories. For...

You can block access to port 8443 (the internal Plesk webspace control panel webserver) with an iptables rule, e.g. # iptables -A INPUT -p tcp -s 192.168.0.2 --dport 8443 -j DROP In this example, traffic directed to 192.168.0.2 and port 8443 will be blockd while traffic to 192.168.0.1 and port...

I can confirm that this is still an active issue and would also like to have it fixed. The number of support tickets Plesk receives on an issue can determine whether a fix is prioritized. So if you are able to file a support case for it, please do so.

Confirmed bug as EXTWPTOOLK-13356 Workaround: Restore the backup without the "Delete existing data before restoring" option. While testing, we noticed that this issue only occurs when the newly added "Delete existing data before restoring" option is marked. If you leave this option unchecked...

I was able to reproduce the issue on a test server. That test server runs a default Alma 8, an (almost) default Plesk installation. I created a test domain, then a default Wordpress installation from the WP Toolkit, then backed up, then restored. The restore showed the same error that the...

MariaDB 10.11.13, but that should not influence anything. Maybe the issue is caused by a plugin or theme, e.g. that after a restore some "after_restore" function is triggered in Wordpress?

PHP 8.3.22, in the "additional PHP directives" section, add disable_functions = proc_open,proc_close

It ain't. We're seeing the download warning messages again on several servers nightly.