• 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 Error 500 Plesk\Exception\Database (DB query failed: SQLSTATE[HY000] [2002] Connection refused)

jaumealcantarago

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
Plesk Obsidian Version 18.0.56 Update #3
Hello everyone, the problem I'm having is the following: I have a Linux VPS managed by Plesk. There are different users on this server since it's dedicated to my company.
The error occurs when one of my employees accesses the server through Plesk or when they access a WordPress project on the server, but it only happens to them. We thought it was related to their public IP and found the temporary solution of using WARP, but the same thing still happens. After reviewing logs, etc., we can't find out why only this person from their home accesses the VPS and the database server crashes. I've attached an image of the error here.

Once we restart the entire server or the MariaDB server, it starts working again and can operate without problems.


Error Plesk MySQL .png
 
Hi,

The error in the screenshot indicates Plesk can't connect to the database service. Check the status of MariaDB. Did it restart recently?

Do you have enough RAM on the VPS? OOM (Out Of Memory) events can kill the database service process and can even damage the InnoDB storage in the process. OOM events occur when the processes on the VPS try to allocate more than the available RAM and generally kill processes with the most used RAM.
 
Hi,

The error in the screenshot indicates Plesk can't connect to the database service. Check the status of MariaDB. Did it restart recently?

Do you have enough RAM on the VPS? OOM (Out Of Memory) events can kill the database service process and can even damage the InnoDB storage in the process. OOM events occur when the processes on the VPS try to allocate more than the available RAM and generally kill processes with the most used RAM.
The problem is that in this case it should always happen and this only happens when a colleague accesses from a complete IP, for example there are 3 more people who access to perform different tasks and MariaDB never goes down
 
The first step is to verify that the MariaDB service is working correctly. If it restarts when the 4th Plesk user connects then you need to find out why. MariaDB can support up to 200 concurrent connections at any given time with the default configuration.

If you have the time stamp when it last happened, check if MariaDB was restarted around that time.
 
El primer paso es verificar que el servicio MariaDB funcione correctamente. Si se reinicia al conectar el cuarto usuario de Plesk, deberá averiguar el motivo. MariaDB admite hasta 200 conexiones simultáneas con la configuración predeterminada.

Si tiene la marca de tiempo de cuándo ocurrió por última vez, verifique si MariaDB se reinició aproximadamente en ese momento.
No se reinicia solo, simplemente lo reiniciamos nosotros mismos y todo vuelve a la normalidad.
 
Interesting.
When it happens, connect to the database service and check the number of active processes:
Code:
plesk db "show full processlist;"  | cat

In the meantime, check if you don't have a small connection limit:
Code:
plesk db "select @@max_connections; select @@max_user_connections;"
 
Back
Top