• 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!
  • 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 Sporadically unreachable websites

Eirik Sikveland

New Pleskian
Hello!

I'm fairly new to Plesk but not to the overall game. I have a few websites running on Plesk Dedicated Server. And everything is working like a charm.

But once in a while, sporadically, maybe twice a month or so all the hosted websites is unreachable except the Plesk panel, the panel works fine every time.

The downtime for the websites vary for each time, from a few minutes up to 30minutes. If I reboot the server, its works fine again.

Have anyone encountered this issue before?
Or do anyone know how to find and eliminate the issue?

Thanks for you time!
 
We've seen this issue when the system has too many open files, although you might not be hosting many domains. What is happening is that a configuration change by a user or an update requires a restart or reload of a system service. This reload fails because further open files are disallowed. This situation does not happen frequently, but it can happen from time to time if your open file handle limits are too low. I suggest following https://kb.plesk.com/en/115139 and https://kb.plesk.com/en/121268. You may also need to modify etc/sysctl.conf (add/modify fs.file-max) and /etc/security/limits.conf (add/modify hard and soft max values or nginx, root, psaadm, mysql), then # systemctl --system daemon-reload.
 
Thanks for your reply. I will try to get this sorted out.

A small update: Happened again today, checked the apache status and is was not running. It was stopped somehow. Don't know if it's because it fails to start again, but once I clicked the Start Service button in the plesk panel, it started without any issues.
 
Back
Top