Search results

If the syntax error with the webmail is still present, simply remove the webmail conf file for now. Disable the missing aclr module using a2dismod aclr

This was the other approach. You get > ERROR: You are trying to run Plesk Installer on an unsupported OS. Because of the HTTP 404 earlier in the script output. Ubuntu 24.04 is properly detected. That appears to be an old plesk-inataller. Download the ubuntu 24.04 package from this page ...

Please try the other approach, not the one-click-installer. Data should still be on the server. Just some Plesk components were removed during apt actions.

Try to install Plesk again How to Install Plesk On Linux? Installing Plesk via CLI Download Plesk installer: wget https://autoinstall.plesk.com/plesk-installer Add proper permissions to Plesk installer: chmod +x plesk-installer Run Plesk installer via command line and follow...

Solution to problem 1 is to enable the firewall from Plesk. For problem 2, is plesk atually installed and running? systemctl status sw-cp-server sw-engine Can you access the database service? plesk db

You have no actual rules in the INPUT chaind and the policy is DROP. Change the policy and enable the firewall from Plesk iptables -P INPUT ACCEPT

That is good. You have a default gateway, obtained via DHCP. Next let's check the firewall. iptables -S INPUT And iptables -S OUTPUT Also try setting a nameserver in /etc/resolve.conf. try at the begining of the file: nameserver 1.1.1.1

Please share the output of ip ro sh

Why do you want SMB? I find it very resource intensive and you don't have any preinstalled panel for it. SSHFS might be a better fit and you can access and mount it in Windows. From the Plesk side you need only SFTP access with /bin/bash shell or /bin/bash (chrooted). For Windows SSHFS please...

Certainly. Just move the subdomain1.domain.tld and subdomain2.domain.tld to the domain.tld subscription. It's still added as a domain, but you can now rename it and add it back as a subdomain with the document root in the same folder. Afterwards, remove the renamed subdomain.

cloudassociates.io has only ns3 and ns4 at the registrar: $ whois cloudassociates.io Domain Name: cloudassociates.io Registry Domain ID: ae84d461e5994d1d89847b46233faa15-DONUTS Registrar WHOIS Server: whois.godaddy.com/ Registrar URL: http://www.godaddy.com/domains/search.aspx?ci=8990 Updated...

Ns3 and ns4 were for skcomm.in For www.cloudassociates.io, you need to add a www CNAME record with the value cloudassociates.io in the Plesk hosted DND zone.

For www.cloudassociates.io, you don't have a DNS record for www. cloudassociates.io resolves to 46.165.217.228. When you access it, you get redirected to ww. $ curl -IL cloudassociates.io HTTP/1.1 301 Moved Permanently Date: Thu, 02 Jan 2025 07:58:46 GMT Server: Apache Location...

The Plesk DNS service looks fine to me: $ dig skcomm.in @46.165.217.228 ; <<>> DiG 9.11.36-RedHat-9.11.36-16.el8_10.2 <<>> skcomm.in @46.165.217.228 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22049 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1...

Match any of the following rules. I would move them to the Spam folder. That way the system can learn from the received emails. You will have to empty the Spam folder from time to time ( one or two times per year, depending on the received mail volume).

Simply do it in the mail filter. Show us the entire filter panel for the rule you shared earlier.

That is sieve filtering performed server side. It will march those domain names and will perform the set action. You also have Spam settings when editing the email address in Plesk. That is what I was referring to. Spam setting can also be set via CLI. > So I want to blacklist that whole...

The blacklist in Tools & Settings > Mail Server Settings doesn't allow the use of wildcards. Only specific domain names can be set. You can set per mailbox rules when Spamassassin is used or globally when Plesk Email Security is used.

Step 5 from https://support.plesk.com/hc/en-us/articles/12377851489943-How-to-restore-a-Plesk-server-on-a-new-Linux-server-from-file-system appears to have information on how to revert to the previous install installation key. Do you have that file from the old server?

The passwords are encrypted with the Plesk installation id. Plesk Backup restore will set the same passwords only on the install from where it was created. To restore the passwords to a new Plesk install you need to set a password on the backup on the original Plesk install.