• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Suddenly all domains unreachable

proton23

Basic Pleskian
Hi there,

I have an nextcloud instance running and tried to upload files to it. I had some trouble so I changed some values in php.ini using plesk. I tried again but it still failed. When I tried to take a look in the log-files, the website was unavailable. So were all domains (2 in total) and all subdomains.

I have no idea what is wrong.
Server is still available via ssh so is plesks control panel.

I'm using Ubuntu 16.04 and tried the following:
Code:
plesk repair all -n
and than
Code:
plesk repair fs -verbose
This fixed some permission problems but sites are still unreachable.

Also tried
Code:
plesk repair web -y -v
same result.

Checked apache and nginx
Code:
nginx.service - Startup script for nginx service
   Loaded: loaded (/lib/systemd/system/nginx.service; enabl
   Active: active (running) since So 2019-07-07 16:47:36 CE
Code:
apache2.service - LSB: Apache2 web server
   Loaded: loaded (/etc/init.d/apache2; bad; vendor preset:
  Drop-In: /lib/systemd/system/apache2.service.d
           └─apache2-systemd.conf
   Active: active (running) since So 2019-07-07 16:48:02 CE
looks like everything is okay
but httpd seems to have some issues
Code:
httpd.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

I don't know if that is the problem and I have no clue how to solve this if it is, so any help is appreciated

Best regards
 
Everything seems to work fine:

Code:
proton23@server:~$ sudo service apache2 stop
proton23@server:~$ sudo service apache2 start
proton23@server:~$ sudo service apache2 restart
proton23@server:~$ sudo /etc/init.d/apache2 restart
[ ok ] Restarting apache2 (via systemctl): apache2.service.
proton23@server:~$
 
httpd.service is not installed on your system. This depends on the OS. Instead it is called apache2 on your system. Apache is running, Nginx is running. So you will need to check in Tools & Settings -> "IP Address Banning (Fail2Ban)" if your server's local IPv4 address is blocked by it.
 
Last edited:
Thanks for your answers.
I'm not sure what to do with this link. I have no account and I cannot register.
What am I supposed to do there?
 
Login to your Plesk with your admin user. Then go to "Tools & Settings", then click "IP Address Banning (Fail2Ban)". Check whether your server's IPv4-address is listed there.
 
Now I get it :D
My local IP was listed there. I unblocked it and now everything works fine.
Thank you very much for your outstanding help! :)
 
Back
Top