Recent content by Sebahat.hadzhi

Please try: systemctl status firewalld plesk bin extension --list | grep firewall Meanwhile, I would also suggest checking with your hosting service provider for a network firewall on their end that could be potentially blocking the requests.

Thank you for the confirmation. So, it indeed looks like IPv6 outbound traffic is blocked on the server in question. The firewall rules need to be adjusted in order to allow IPv6 outbound traffic. If you are not sure how, please let us know what firewall are you using.

Hi, @myat.m2024 . This usually happens when outbound traffic is blocked, thus, WP Toolkit's requests fail. Please login into your server via SSH, execute the following commands, and provide us with the output: nc -zv wordpress.org 443 nc -zv api.wordpress.org 443

Do you get the same result when you run apt-get update? If not, what I can suggest as a workaround is to to disable the system updates notification with the following command: plesk bin notification --update -code admin_pum_updates -send2email false What else I can suggest is to changing the...

Hello, @hsoheili . What you can do is connect to the server via SSH as the root user and change the Plesk admin password with the following command: plesk bin admin --set-admin-password -passwd 'your_new_password' If you don't have root access yourself, please ask the server...

@emilyy3 Plesk does not restrict email accounts to either IMAP or POP3. The user who initially reported the issue mentioned that the same is related to Thunderbird. Have you tried testing the scenario with another email client?

Thanks, please try running the following command: echo 'APT::Key::Assert-Pubkey-Algo ">=dsa1024,rsa4096,rsa3072,rsa2048";' | tee /etc/apt/apt.conf.d/99weakkey-warning I will ignore errors for weak repository signature keys. Once done, please try re-running the update.

Hi, @frundaa . Similar issues are typically caused by incomplete Plesk updates. What I can suggest is trying to run the update manually with the command below. Just to be on the safe side, please make sure you have a backup copy of the server in case something goes wrong. plesk installer...

Hi, @maennchen1 . Have you previously modified /etc/apt/apt.conf.d/99weakkey-warning? If possible, could you please share its content? Thank you in advance.

Thank you for the confirmation. Yes, please leave it disabled. The repository is not supported by Plesk.

Hi, @ScottGoddard . We have a registered bug identified with ID PPPM-5474 for that behavior. I will consult with our team further on the matter and try to provide an ETA for the fix.

Hi, @Talistech . The case was further analyzed by our software engineers and they did not recognize it as a bug. -apply-to-webmail relates to --hsts option only. It's reflected in the help:[/ICODE] # plesk ext sslit --help | grep apply-to-webmail --hsts -enable|disable -domain <domainName>...

Thank you for the update. Our team found the root cause of the issue to be the Email Security extension. They are actively working on it and a fix will be released as soon as possible. Bug ID EXTPLESK-10084. Thank you for your patience in the meantime.

The issue was fixed in Plesk Email Security 1.5.23. Please update the extension and let us know if you face any further issues.

Hello, @first4it . Do you have anything deployed under stage.mydomain.com, e.g. an existing clone? I am unable to replicate the issue on a test environment. The website is successfully cloned under stage.mydomain.com when I try. Please provide us with more details - what's the document root of...