Search results

A custom password. I have tried both updating it and using plesk's encryption key though. Still getting the same error.

Hitting "Bcrypt password must not contain null character" whenever daily config backup is trying to run. That's all I get. Nothing else, no mention of which password entry it is, so I have no way of knowing which password to reset. How do I go about diagnosing this?

Going to run "plesk repair installation" and see if that fixes it since httpd is now rinning properly

no Lightspeed but strace did point at why httpd was failing: openat(AT_FDCWD, "/var/www/vhosts/system/domain.tld/logs/access_log", O_WRONLY|O_CREAT|O_APPEND|O_CLOEXEC, 0666) = 1023 openat(AT_FDCWD, "/var/www/vhosts/system/domain.tld/logs/access_ssl_log", O_WRONLY|O_CREAT|O_APPEND|O_CLOEXEC...

Nope # systemctl reset-failed httpd # systemctl start httpd Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xeu httpd.service" for details.

Already tried debug. It showed nothing. Its' loading all modules just fine and then just stops [Fri Nov 14 15:18:57.480455 2025] [so:debug] [pid 1181207:tid 1181207] mod_so.c(266): AH01575: loaded module access_compat_module from /etc/httpd/modules/mod_access_compat.so [Fri Nov 14...

Keep getting an Apache error and can't seem to figure out how to fix it: New configuration files for the Apache web server were not created due to the errors in configuration templates: Can not restart web server: apache_control_adapter[1133370]: Apache is down, start it instead of...

I have to restart it, not just start. Mariadb process is still running and showing (Active status) when I do that. I do get the shutdown dump as well. Should have worded that more clearly 2025-05-14 11:37:01 43001 [Warning] Aborted connection 43001 to db: 'db' user: 'usr' host: 'localhost'...

Absolutely nothing in the logs with the time of the issue until I manually restart the service. Then I just get the typical startup dump I did try a few thing to no avail. I increased InnoDB buffer pool thinking it might be too small - no change. Increased max connections, error still happening.

Nothing criminal here other than a bunch of sleeps and a few SELECTs +--------+-------------+-----------+------------------------+---------+------+--------------------------+-------------------------------------------------------+----------+ | Id | User | Host | db...

For a few weeks now we've been having this weird issue with all sites hosted on Plesk (except the pain one with no database) - all sites would suddenly show a database connections error until I restart mariadb service on Plesk. Even the ones with external DB server. It looks like a mysql.sock...

SOLVED (I think). For anyone looking to automate this: Step 1. Make sure you have the target dir set up on the FTP server - it needs to exist when the settings are validated and doesn't get created automatically Step 2. Set up the FTP target and credentials (in my case the target is a domain...

Correction: the settings are added, but the Backup Manager still shows FTP inactive, so it doesn't appear in the Scheduler as an option. Edit: Seems like it needs to be explicitly enabled by running:

Yes, the test cURL works fine, but it asks for the passwords explicitly when you run it. This doesn't return anything - no errors and no success messages - and seems to run. However, when I go in to the domain's backup manager to check the FTP settings, nothing has been added. Also,

even after setting the FTP_PASSWORD env var.

I found this topic: https://support.plesk.com/hc/en-us/articles/12377218996631-Is-it-possible-to-create-scheduled-backup-tasks-in-Plesk-via-CLI-API but it doesn't seem to work. When trying to configure FTP for a subscription: $ sudo plesk bin backup-storage --configure ftp -subscription...

Trying to figure out how to automate backups to FTP for each new domain. As it stands, the only way I can see is doing it for each domain manually: go to the domain, click Backup & Restore, add remote storage settings, schedule backups. I was hoping there was a better way of automating it so...

Pretty sure the standalone certbot install has a local list of certs to renew (a bunch of .conf files kept in /etc/letsencrypt/renewal). This list has to exist in Plesk install as well. Just not sure where it's kept.

Same issue. Deleted the cert, set the domain to HTTP only. Still getting "could not renew" notifications every day

WP Toolkit cloning no longer working. Instead we're just getting a timeout: Task is not responding: id=7945, pid=26158, type=ext-wp-toolkit-clone-instance, currentStepProgress=-1, currentStepText=, initialTaskParameters=Array, isRestarted=1, publicParams=Array...