Search results

Hello again! The cause of the issue is that in Debian 12 part of the DNS utilities were moved to another directory. The current behavior was confirmed as a bug that is yet to be fixed. In the meantime, there is a simple workaround available: 1. Connect to the server via SSH. 2. Create a link to...

Hi @klowet ! I was able to reproduce the issue on Plesk 18.0.57.1+Debian12. At the same time, it does not appear on Debian11 and RHELbased OSes (like Alam8), so it looks like OS-specific. I'll try to dig into it and let you know.

Hi @Groo ! On the Plesk side, we don't have any special guides on that since it's not the desired scenario (i.e. it's considered a customization and security risk). I understand that it's needed to maintain an old website, however, the main intention to move to a newer OS is to use newer...

Hello @bssrjai Try to check these 2 things as a starting point: 1. Make sure that the server hostname is set up correctly at Tools & Settings > Server Settings and click OK to re-apply the changes. 2. Make sure that the correct URL is set up in Tools & Settings > Customize Plesk URL and click...

Hi @tanasis It's up to you to decide what are the optimal values for your server for certain services. These thresholds (and the alerts) are set just for monitoring and notification reasons and are adjustable per your needs. According to your htop output, there should be enough memory though so...

Hi @valko The issue with the MySQL roundcube user is usually connected with an absence of such a user or other things like the user is corrupted, having an invalid password or not having enough permissions. The easiest way is indeed to reinstall the webmail or fix the database issue. However...

Also, I'd recommend checking if there is any free space left since some websites (or their databases) tend to eat up a lot of space when left intact without any limits. See https://support.plesk.com/hc/en-us/articles/12377562126743 for reference.

Hello! Looks like the issue is more or less related to the Redis configuration in Docker than to Plesk itself. But anyway let's try to figure out what is going on here. Could you paste the env variables here so I could try to reproduce the issue?

Hello @Kulturmensch , Seems that nextcloud instance is located in a subfolder that the nextcloud database does not understand. What is the document root of the domain in Plesk > Domains > cloud.tenckhoff.de > Hosting Settings and where is the nextcloud installed inside the domain?

Hello! You can do it via Subscriptions > example.com > Users > User Accounts > John Doe > Change Settings However, the initial user's role cannot be changed.

Hello @dgarcia90 , I would begin by checking the logs for the timeframe when the issue appeared. The logs I would check for: The logs of a few affected websites (Domains > example.com > Logs) - maybe there is a pattern, e.g. similar errors on different websites that were down. The webserver...

Hi! In the current implementation, you can't disable Apache at all on the server level. However, you can do it for a single domain or service plan: https://support.plesk.com/hc/en-us/articles/213924385 The timeouts above are to be added in Plesk > Domains > example.com > Apache & nginx settings...

Hello @FutureX Since port 8443 is another service, the SSL warning is expected when you use a customer's domain name. When accessing https://clientdomainname.com:8443 the browser uses the hostname's certificate and sees the mismatch. So you have 3 options here: Use https://servername.com:8443...

Hello @mudassar You can find the WP database name in Plesk > WP Toolkit > your instance name (e.g. example.com) > Database. The other option is to go to Plesk > Domains > your website > Databases and find there a database of the instance. By default, it is named like wp_***.

Hello @Kyuhunter Since there was a migration, I would suggest checking the DNS settings of the domain. It may be that the domain resolves to the different IPs. You may use DNS Checker - DNS Check Propagation Tool for that if you like.

Hi @Bence98, Seems that the reinstallation of SpamAssassin didn't help you. Most likely the packages are not configured now. You can check it by running: dpkg -l | grep spamassassin dpkg -l | grep sa-compile The packages will be marked either with iU or iF flags. There can be 2 different...