• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue plesk not reachable for ip4 visitors, only ip6

S

szpleskroast

New Pleskian
This morning my server's disk space became too full, making our website unavailable. I immediately added disk space to it.
After that I was only able to reach the Plesk frontend through the:8443, but not through the normal URL.
Also when I visit our website on the server, it shows a 504 gateway timeout.

Then i found out, someone else (on a ipv6 internet connection) was able to perfectly reach the website and server.
So basically this is what I know now:
Someone with an IP4 is not able to reach the server (except through the :8443 port). IP6 visitors are connecting to the server just fine.

In the plesk log i see an error for this site after i watched it: upstream timed out (1100 connection timed out) while connecting to upstream

Hope anyone has an idea or is able to help out on this one.
 
Does anything listen to that port on v4? Check with netstat -tupln. Did you restart apache2?
 
You must log in or register to reply here.

Similar threads

Z
Issue Prestashop 8 : very slow and error "504 Gateway Time-out - Nginx"
Replies
1
Views
2K
1nghi
1
Nextgen-Networks
Resolved Plesk 18.0.65 Update -> Error 504
Replies
4
Views
1K
Nextgen-Networks
Nextgen-Networks
B
Issue 704710#0: *18394 upstream timed out (110: Connection timed out) while SSL handshaking to upstream
Replies
1
Views
2K
sans
S
R
Resolved upstream timed out (110: Connection timed out) while connecting to upstream
2
Replies
24
Views
23K
rhand
R
B
Issue High latency, unreliable performance & 522 errors on a Plesk server that ran fine for 6+ months
Replies
8
Views
2K
HHawk
HHawk
Back
Top