Search results

@imrelaszlo84 Just checked on your configuration (Plesk 18.0.57.1 on Ubuntu 22.04.3 LTS) No issues with "admin" login or additional admin login to Mobile app. Please submit a ticket to Plesk Support...

Do not think so. Topic-starter had the issue a year before product changes that caused PMBL-652. @imrelaszlo84 If you changed admin name (that become possible since Plesk 18.0.57) and used new name for login, that most probably you faced with PMBL-652 and there is no fix for it yet. Try to...

@itknowledge Hello, I can confirm that currently such configuration is not supported by Plesk mobile app. The item to investigate and fix the issue PMBL-652 created. Thank you for pointing our attention on that.

Hello @goodmen021 , Could you please elaborate what goal are you going to reach? If you face the issue when after entering login credentials, the login screen re-appears, that means the server hostname is not filtered by Cloudflare, which uses multiple IP addresses. You can try to enble option...

Hello @klamort, From the information you provided I see that most probably the configuration of mailserver incorrect thy the solution from this article to reinstall it https://support.plesk.com/hc/en-us/articles/12377288758167 In case it would not help - submit a ticket to Plesk Support...

@lessborders Use no relay restrictions for the following networks is available for Plesk for Windows only Tools & Settings > Mail Server Settings in case MailEnable or SmarterMail installed as mail server:

Changes and checks that were mentioned should be performed on Windows server. Since message "551 This mail server requires authentication..." comes from recipient.

Hello @mudassar. There are might be several causes of the issue: 1. The sender's domain exists on the destination server and is considered as a local domain. In this case sender's domain should be deleted from the receiving mail server. 2. Email was sent from a user who did not authenticate...

Hello, @joep842 I suggest you look to the "Dedicated PHP-FPM handler" option that allows you to run website in separate PHP master process.

Hello @justinforga Looks like the issue is related to Akeeba software. In their thread https://www.akeeba.com/support/site-restoration/30112-database-support-no.html was suggested to enable "mysqli" or "mysqlnd" for the PHP. You may try to apply the Resolution part from this article...

@GlennT no risk at all, since webhosting files and email stored in different places. As for disabling HSTS you can try to execute the following command, connected to the server via SSH as root: # plesk ext sslit --hsts -disable -domain example.com

Hello @GlennT Looks like the issue you faced and ways how to resolve it described here: Let's Encrypt can not issue certificate for webmail only in Plesk if domain is hosted on another server: An SSL / TLS certificate could not be issued for example.com If provided solution will not help...

Hello @Stef You may also inspect your .env file and check if everything specified correctly, it might be helpful to change DB_HOST parameter/ Specify IP address of the server A instead of hostname

Hello @alexyz4 Please take a look here relay options

Hello @Stef I suggest you check if IP address and hostname of server "A" is available from server "B" using network tools (such a curl or telnet) to exclude network issues. Further there is a small probability that password of database user contains characters (such a ? or " ) that escaped...

Hello, @jojod as far as I understand there are 2 issues: 1. Incorrect ownership it can be fixed recursively by execution of this commands: # find /var/www/vhosts/example.com/httpdocs/ -type f -exec chown user_example:psacln {} \; # find /var/www/vhosts/example.com/httpdocs/ -type d -exec chown...

Hello @benshikari, please make sure that Plesk Task Manager is running, to do that, open Plesk Service Monitor in System Tray:

Hello @Krydos Please refer to Plesk Migration and Transfer Guide and Migrating via the Command Line documentation pages

Hello @loveunitesus Looks like there were some issues during Netdata installation, so the requires system entities were not created. Please try to add "netdata" group: # groupadd netdata

Hello @Geraldo V Vieira, The mentioned behaviour is related how the browser interprets some symbols, and not directly related to Plesk. For example: IP address - 203.0.113.2 User - admin Password - ABC123&abc the following URL should be used...