Resolved Error 523 after restart server

[Febryan]

Hi guys,

I'm facing a problem, when i need to restart my server. After i restart my server. I can't connect to my Website/Plesk, it says error 523.

I've tried start psa service, /etc/init.d/psa start, but still error 523 i can't access my web.

Help me
Thankyou

 

[UFHH01]

Hi Febryan,

can you confirm, that your service(s) apache2/httpd ( + nginx? ) are up and running?
can you confirm, that your services "sw-cp-server" and "sw-engine" are up and running?
can you confirm, that no firewall blocks your ports?
can you confirm, that no Fail2Ban - entry blocks your server IP(s)/localhost or/and your home IP ?

 

[Febryan]

Hi Febryan,

can you confirm, that your service(s) apache2/httpd ( + nginx? ) are up and running?
can you confirm, that your services "sw-cp-server" and "sw-engine" are up and running?
can you confirm, that no firewall blocks your ports?
can you confirm, that no Fail2Ban - entry blocks your server IP(s)/localhost or/and your home IP ?

Now i can access my plesk panel.. but the problem i still cant access my websites. All services seems working normal but idk why i still cant access my websites 'firewall/proxy error'

 

[UFHH01]

Hi Febryan,

unfortunately, you don't really confirm the questions, so that your root cause of your issue still remains invisible. Pls. consider to visit:

Plesk for Linux services logs and configuration files ( KB - article: 213403509 )​

... where you are able to find all possible log - file locations and commands to start/stop your essential services. Pls. report back with the output of a depending service - command:

service SERVICE-NAME status
(for example: service apache2 status )
​

You didn't provide any informations about your current operating system and missed as well the informations about your current used Plesk version ( incl. #MU ).


Your issue

but idk why i still cant access my websites 'firewall/proxy error'

could be investigated with the help of domain - specific log - files, where the above mentioned KB - article - link, will point you to the correct location of these log - files. Pls. consider to post these log - files, if you need further help with your investigations.


In order to investigate, if a firewall entry might block your server IP(s)/localhost or your home IP, pls. consider to login as user "root" ( over SSH ), using the command:

iptables -L​

... which will display all current entries. Pls. consider to post them, if you need further help with your investigations.

 

[Febryan]

Hi Febryan,



In order to investigate, if a firewall entry might block your server IP(s)/localhost or your home IP, pls. consider to login as user "root" ( over SSH ), using the command:

iptables -L​

... which will display all current entries. Pls. consider to post them, if you need further help with your investigations.

sorry for late answer,, here is the iptables

target prot opt source destination
ACCEPT all -- anywhere anywhere ctstate RELATED,ES TABLISHED
ACCEPT all -- anywhere anywhere
INPUT_direct all -- anywhere anywhere
INPUT_ZONES_SOURCE all -- anywhere anywhere
INPUT_ZONES all -- anywhere anywhere
DROP all -- anywhere anywhere ctstate INVALID
REJECT all -- anywhere anywhere reject-with icmp-h ost-prohibited

Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere ctstate RELATED,ES TABLISHED
ACCEPT all -- anywhere anywhere
FORWARD_direct all -- anywhere anywhere
FORWARD_IN_ZONES_SOURCE all -- anywhere anywhere
FORWARD_IN_ZONES all -- anywhere anywhere
FORWARD_OUT_ZONES_SOURCE all -- anywhere anywhere
FORWARD_OUT_ZONES all -- anywhere anywhere
DROP all -- anywhere anywhere ctstate INVALID
REJECT all -- anywhere anywhere reject-with icmp-h ost-prohibited

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
OUTPUT_direct all -- anywhere anywhere

Chain FORWARD_IN_ZONES (1 references)
target prot opt source destination
FWDI_public all -- anywhere anywhere [goto]
FWDI_public all -- anywhere anywhere [goto]

Chain FORWARD_IN_ZONES_SOURCE (1 references)
target prot opt source destination

Chain FORWARD_OUT_ZONES (1 references)
target prot opt source destination
FWDO_public all -- anywhere anywhere [goto]
FWDO_public all -- anywhere anywhere [goto]

Chain FORWARD_OUT_ZONES_SOURCE (1 references)
target prot opt source destination

Chain FORWARD_direct (1 references)
target prot opt source destination

Chain FWDI_public (2 references)
target prot opt source destination
FWDI_public_log all -- anywhere anywhere
FWDI_public_deny all -- anywhere anywhere
FWDI_public_allow all -- anywhere anywhere
ACCEPT icmp -- anywhere anywhere

Chain FWDI_public_allow (1 references)
target prot opt source destination

Chain FWDI_public_deny (1 references)
target prot opt source destination

Chain FWDI_public_log (1 references)
target prot opt source destination

Chain FWDO_public (2 references)
target prot opt source destination
FWDO_public_log all -- anywhere anywhere
FWDO_public_deny all -- anywhere anywhere
FWDO_public_allow all -- anywhere anywhere

Chain FWDO_public_allow (1 references)
target prot opt source destination

Chain FWDO_public_deny (1 references)
target prot opt source destination

Chain FWDO_public_log (1 references)
target prot opt source destination

Chain INPUT_ZONES (1 references)
target prot opt source destination
IN_public all -- anywhere anywhere [goto]
IN_public all -- anywhere anywhere [goto]

Chain INPUT_ZONES_SOURCE (1 references)
target prot opt source destination

Chain INPUT_direct (1 references)
target prot opt source destination

Chain IN_public (2 references)
target prot opt source destination
IN_public_log all -- anywhere anywhere
IN_public_deny all -- anywhere anywhere
IN_public_allow all -- anywhere anywhere
ACCEPT icmp -- anywhere anywhere

Chain IN_public_allow (1 references)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere tcp dpt:ssh ctstat e NEW
ACCEPT tcp -- anywhere anywhere tcp dptcsync-htt ps ctstate NEW

Chain IN_public_deny (1 references)
target prot opt source destination

Chain IN_public_log (1 references)
target prot opt source destination

Chain OUTPUT_direct (1 references)
target prot opt source destination

 

[UFHH01]

Hi Febryan,

you decided to use a firewall, without configuring it. Pls. see the Plesk KB - article:

=> Which Ports Need To Be Opened for all Plesk Services to Work with a Firewall?​

 

[24x7cloudservermanagement]

configure the firewall and make sure you have port 80 , 25 , 443 , 110 open

 

[Febryan]

Hi Febryan,

you decided to use a firewall, without configuring it. Pls. see the Plesk KB - article:

=> Which Ports Need To Be Opened for all Plesk Services to Work with a Firewall?​

sorry for late feedback.. excellent! yes it is, i forgot allow some port permanent... thankyou for your help