Plesk for Windows
Plesk for Linux
kb: technical
ABT: Group B
Applicable to:
- Plesk for Linux
- Plesk for Windows
Symptoms
-
A website or a website preview does not work. One of the following error messages is shown in the browser:
CONFIG_TEXT: Connection time out
CONFIG_TEXT: This site can’t be reached The connection was reset.
-
The following warning is shown for IP address assigned for the website in Tools & Settings > IP Addresses :
PLESK_INFO: This IP address is not configured properly. Repair.
Cause
IP address misconfiguration.
Resolution
-
Go to Tools & Settings > IP Addresses and click Repair link in warning:
Note: If there is no Repair button click on broken IP 203.0.113.2 > and then OK.
Comments
5 comments
Just in case - I have suddenly started getting this against one IP on my server - several times a day it seems (site works fine for a while, then times out and I find this error). Started yesterday (24th Sept 2019) as far as I can tell. Never seen it before.
So not sure a recent update has broken something. The IP is only used for one website, as I got it for a dedicated SSL ip address. the other IP on my server which is shared over many websites works fine and hasn't seen this error. Get stuff together to report it but I thought I'd leave this year in case others search and fine with the same issue.
hello,
Running the fix sorts the time-out problem - but only for a number of hours - it then breaks again, and requires the same fix. I wonder if a Plesk update has made something unstable?
@Zayoud Ayoub
Plesk does not manage networking, so it is unlikely caused by a product. Recently there was similar problem report caused by the fact one of the IP addresses was issued by DHCP and was not properly renewed. If it is your case - you may want to get in touch with hosting provider and adjust that. If not I'd recommend to create a ticket to check the issue.
Over the last year many of our servers have suddenly lost the IP addresses after routine automated plesk updates. Often in batches of 100 at a time. The only fix is to login to each.. repair IP.. then run repair web. This really is not ideal!
Hi, andy bird
This is definitely not an expected behavior; We'd be more than interested in investigating this issue should you have one server/case as an example. Please submit a request to us at https://support.plesk.com/hc/en-us Thanks!
Please sign in to leave a comment.