Facebook
Twitter-
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.
Not microupdated PLESK 12.5.30
- Thread starter emperor
- Start date
@emperor,
Your server does not connect to the Plesk repositories, leaving you with an update cycle in which the connection is being reset.
In essence, the issue is that the connection on the Plesk server is being closed before the content is being downloaded.
The behaviour, resulting in a connection shutdown, can be present on the Plesk server OR the remote server.
In general, we can exclude the possibility that the remote server is causing the connection shutdown: after all, the Plesk repositories are and should be "open".
Many causes for this behavior can exist, I will discuss some of them:
a) Firewall: make sure that your server does not block any traffic. To test this: just open the firewall completely once and if the problem persists, it is not the firewall.
b) MTU (Maximum Transmission Unit): the MTU size of packets can be changed, causing any problems. This often happens when having a VPN. Check the MTU size, it should be around 1500 bytes (if I am not mistaken). Also check the presence of a VPN. If the MTU size is ok and a VPN is absent, than the MTU is not the root cause of the problem.
c) Bugs: a well-known Linux kernel bug is related to window_scaling. The solution is to add the line "net.ipv4.tcp_window_scaling = 0" to /etc/sysctl.conf.
I sincerely hope that one of the above resolves your issues.
In general, you should contact your hosting provider, since the issue is very likely to be related to the configuration by the hosting provider.
In short, the fastest way to resolve this issue is to contact your hosting provider.
Hope the above helps!
Regards....
Your server does not connect to the Plesk repositories, leaving you with an update cycle in which the connection is being reset.
In essence, the issue is that the connection on the Plesk server is being closed before the content is being downloaded.
The behaviour, resulting in a connection shutdown, can be present on the Plesk server OR the remote server.
In general, we can exclude the possibility that the remote server is causing the connection shutdown: after all, the Plesk repositories are and should be "open".
Many causes for this behavior can exist, I will discuss some of them:
a) Firewall: make sure that your server does not block any traffic. To test this: just open the firewall completely once and if the problem persists, it is not the firewall.
b) MTU (Maximum Transmission Unit): the MTU size of packets can be changed, causing any problems. This often happens when having a VPN. Check the MTU size, it should be around 1500 bytes (if I am not mistaken). Also check the presence of a VPN. If the MTU size is ok and a VPN is absent, than the MTU is not the root cause of the problem.
c) Bugs: a well-known Linux kernel bug is related to window_scaling. The solution is to add the line "net.ipv4.tcp_window_scaling = 0" to /etc/sysctl.conf.
I sincerely hope that one of the above resolves your issues.
In general, you should contact your hosting provider, since the issue is very likely to be related to the configuration by the hosting provider.
In short, the fastest way to resolve this issue is to contact your hosting provider.
Hope the above helps!
Regards....
Glad to be of some assistance, thanks for the like! That like is much appreciated.
