Search results

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.

Hi, juanma@***dec.es is a Google Workspace email address? Domains that use Google Workspace hosted email addresses or other 3rd party mail services must have the mail service Disabled for incoming or Not configured (removes existing email addresses and server stored emails). The log entry...

Check the tasks in Tools & Settings. You might need to remove those 2 long running tasks from the psa database.

/var/log/plesk-roundcube/errors should contain only PHP errors: /usr/share/psa-roundcube/config/php.ini.tpl:display_errors = Off /usr/share/psa-roundcube/config/php.ini.tpl:log_errors = On /usr/share/psa-roundcube/config/php.ini.tpl:error_log = "/var/log/plesk-roundcube/errors" You can try to...

By default all additional FTP users can connect only via FTP and FTPS (on port 21). They have /bin/false shell which is not a valid shell for SSH or SFTP access (on port 22). You can grant access using SSH-Keys and the system user. This will grant access to the developer to the entire webspace...

Try to reinstall Roundcube by removing it from Plesk Installer. Afterwards, install it back from Plesk Installer.

The screenshot shows the entire server disk usage, not just the disk usage of your website. Furthermore, the disk usage is not in /opt/psa. /opt/psa is just an import folder on that disk. Since this shows the entire server disk usage, including newly received emails, new data stored in the...

Can you share a screenshot of the statistics you are seeing in Plesk?

Thank you. Use the following to update the resolvers for your public interface. systemd-resolve --interface ens6 --set-dns 127.0.0.1 Afterwards please check resolvectl --status before and after a service restart systemctl restart systemd-resolved.service.

OK Is the output of du -sh /var/www/vhosts/technightowl.live around the same value displayed in the Plesk statistics? Can you share the Plesk statistics and the output of the du command?

Yes. Can you also share the full path with us?

Hi, Please check the Rouncube error log in /var/log/plesk-roundcube/errors. For additional information about Rouncube in Plesk please see https://support.plesk.com/hc/en-us/articles/12377744787991-Plesk-for-Linux-services-logs-and-configuration-files#roundcube Roundcube uses the global Apache...

Can you share the statistics shown in Plesk and the output of the following commands? HTTPD_VHOSTS_D=$(grep HTTPD_VHOSTS_D /etc/psa/psa.conf | awk '{print $NF}') du -sh $HTTPD_VHOSTS_D/WebspaceName

Can you please confirm what issue you are encountering? If your system can't resolve domain names, please check the status of /etc/resolv.conf: cd /etc/ ls -l --color=auto resolv.conf If you see something like this: If it's displayed in red or /run/systemd/resolve/resolv.conf doesn't exist...