Search results

Could have been a temporary routing issue on your Server Network/Datacenter

Seems you cannot reach the autoinstall.plesk.com server. Can you try to run: curl -Iv autoinstall.plesk.com and provide the output?

you would need to check what jailed banned and then the logs of that service

Please do check the domain logs to see if there is some more information available there The error you provided is quite generic

Like with Browsers, etc. extensions/add-ons are often also provided by 3rd parties: Let's see if any other LiteSpeed users have a jail to share, or you would need to contact the LiteSpeed team

LiteSpeed is a 3rd party web server that is not supported by Plesk, but by LiteSpeed itself. Seems that they don't offer a template for a jail, from what I can find here: https://www.litespeedtech.com/support/forum/threads/install-and-configure-fail2ban-in-plesk.16564/ Maybe other members that...

Are you using Plesk Premium Mail extension? If yes, the log would be /var/log/roundcubemail/errors.log

Tech domains are for testing proposes, and to help with initial build of sites, etc. they are not intended to be used productively, so cannot be transferred between servers. Due to this as Peter already said you will need to move it to a new Tech Domain, or to your own domain.

DNS is handled over the top level, so you would still need to add the records under Alfahosting

The same workaround should work using the CLI version over the API: https://docs.plesk.com/en-US/obsidian/cli-linux/using-command-line-utilities/database-databases.75671/ Updated the issue internally with the information that Database creation is also affected.

Please see Software Requirements for Plesk Obsidian For now Plesk only does support up to MariaDB 10.6, anything above would be on your own risk Edit: Missed that Support for 10.11 was already added in Plesk

From what I see, you just have the standard needed ports open that Plesk does use.

Port 25 incoming you can always manage, support is often needed for outgoing only I think I did redact all the IP/Names in the post

They now show as open, you're still missing Port 25 to get mails: Host is up (0.015s latency). PORT STATE SERVICE 25/tcp filtered smtp 110/tcp open pop3 143/tcp open imap 465/tcp open smtps 993/tcp open imaps 995/tcp open pop3s Nmap done: 1 IP address (1 host up)...

You need to open the ports for incoming traffic over AWS: https://lightsail.aws.amazon.com/ls/docs/en_us/articles/understanding-firewall-and-port-mappings-in-amazon-lightsail Just local iptables won't do it

If you want to request it from Plesk, then you can use: https://plesk.uservoice.com/forums/184549-feature-suggestions

Then please contact CL Support first, to get yum working correctly as that is from OS and not Plesk side.

Article was replaced: https://support.plesk.com/hc/en-us/articles/12376920929431, but also already fixed

That depends on lots of factors, you can try over the process list to find it to stop and remove it, but depending on the infection source might not be enough as it may replicate then again. https://www.plesk.com/blog/security-alerts/plesk-server-hacked/

The error comes from your OS, make sure that your CloudLinux license is correctly installed or contact the CloudLinux support for help with it. If you know your key you can try: /usr/sbin/rhnreg_ks --activationkey=YOUR_CLOUDLINUX_KEY or /usr/sbin/rhnreg_ks --activationkey=YOUR_CLOUDLINUX_KEY...