Search results

Sorry for the previous command. Please try the following: journalctl -n100 --no-pager -xeu mariadb

The issue is above line 54. Your screenshot has only the shutdown part. You might have an InnoDB corruption.

Try this comand and provide the output: journalctl --output=cat -xeu mariadb

Can you ping localhost from your server? Does localhost resolve to 127.0.0.1?

Try to access the challenge URL from a different IP address than your usual IP. Your IP address might be whitelisted in the hardware firewall.

Do you allow http:// via the hardware firewall? Let's Encrypt will try to access the challenge URL via HTTP.

Hi, The error indicates all connection slots to the database service have been used up. By default, that is 200 connections and 150 per any single database user. If plesk db fails then you need to restart MariaDB systemctl restart mariadb

Check the passive ports set in Proftpd: grep Passive /etc/proftpd.* -r /etc/proftpd.conf:PassivePorts ????? !!!!! Check the Plesk firewall if the ports are enabled: iptables -S INPUT | grep <?????? = first port from the previous step> -A INPUT -p tcp -m tcp --dport ?????:!!!!! -j ACCEPT The...

Are the passive ports opened in the firewall?

Can you share a screenshot of the options that are selected? Do you get anything logged in /var/log/plesk/panel log when the backup fails?

Those are not a problem. What did you select in the Backup Manager when the backup was created? Do new backups trigger the same error?

The map directive is valid only in the http context: Module ngx_http_map_module The Additional nginx directives are included in the server context which is within the http context. In order to set map directive, create a .conf file in /etc/nginx/conf.d/

The permissions look ok. Check if you have files and folders not owned by example.com_b7qdtl2wu8n: find /var/www/vhosts/example.com ! -user example.com_b7qdtl2wu8n

Hi, What are the actual permissions? ls -ld /var/www/vhosts Ls -ld /var/wwwvhosts/example.com You can run Plesk repair to fix permission and ownership: plesk repair fs -v

Yep. That is the way to do it.

Yes, it's an SSH command and it will affect only the SSH session it was run in. Export will update the SSH environment. The PATH environment variable designates the folders where the shell will look for binaries, including php. By prepending the location of PHP 8.4 in $PATH, php will be found...

The simplest approach is to: export PATH=/opt/plesk/php/8.4/bin:$PATH This will change the PHP version for the current session. However, if you set the PHP version to 8.4 for the website, phpenv should use that PHP version.

Hi, Please check if you have this conf file: /opt/plesk/php/8.3/etc/php-fpm.d/test.glodek-edv.de.conf Plesk forgot it but might have also left behind a PHP-FPM configuration file. If you do and you no longer have that subdomain in Plesk, simply remove it.

The default serial is built like this yyyymmddxx. I assume you made 99 changes to the parent domain DNS zone.

I'm glad to hear the task is no longer displayed. Usually, a failed task is not a big issue. The failed tasks are not running processes. You can run the failed task again and it might complete successfully. However, the dropdown will provide additional details regarding the failed task.