Search results

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...

So probably: https://support.plesk.com/hc/en-us/articles/12376926550679-Domain-is-not-accessible-from-some-locations-after-switching-to-Plesk-nameservers-due-to-DNSSEC-misconfiguration You may need to re setup DNSSEC for the domain to propagate correctly with it enabled.

Not enough information to help. Does the registrar point to the correct NS? Do the other domains work? Is the domain active at the registrar level? Is the DNS populated inside Plesk? If you do "dig example.com @server_ip" do you get something?

Seems that the PSA database got corrupted, either due to removed data, or due to a system issue with the InnoDB. You can try to restore it over the daily dumps that plesk makes: https://support.plesk.com/hc/en-us/articles/12377774462231-Unable-to-access-Plesk-Table-psa-table-name-doesn-t-exist...

This plan is hidden by default and created when restricted mode or web admin license is used by the 1st time Yes, the same issue may reappear, you can then run the repair for PHP handlers again to update it again when the time comes

It will ask what handler to use: https://support.plesk.com/hc/en-us/articles/12387711784471 The admin simple plan is not visible in GUI as it is for the Restricted Admin Mode: https://docs.plesk.com/en-US/obsidian/deployment-guide/reference/plesk-in-restricted-mode.80000/

You would need to run it for each PHP versions (7.4, 8.0, etc.) not each sub handler

It will install it for all handlers on the same version as they share the modules, but you can find the exact names with: plesk bin php_handler --list

You can normally install it on your own for the PHP handler you need: https://docs.plesk.com/en-US/obsidian/cli-linux/using-command-line-utilities/php_handler-php-handlers.72490/ As an example, for PHP 8.1: plesk bin php_handler --extension-install ssh2 -id plesk-php81-fpm Or manually...

It is expected as the domain does not point directly to the Plesk server, that is why you see the message, since DNS, etc. is handled at Cloudflare for your domain, you can ignore the message More information can be found here: https://support.plesk.com/hc/en-us/articles/12387546184727

Yes it is normal, Plesk does not manage certain system updates as they can have risks, like Kernel, etc.

I would suggest then to contact the technical support to check this further

Please do check: https://support.plesk.com/hc/en-us/articles/12377464405527-Unable-to-open-Updates-and-Upgrades-menu-on-Plesk-for-Linux-server-Can-t-connect-to-backend-No-such-file-or-directory