MariaDB Access Denied & WordPress Installations Failing (Internal CyberPanel Issue

Support and Discussion General Discussion
1

Dear CyberPanel Members,

I urgently need your assistance with a critical problem on my CyberPanel server (IP: 213.239.217.121). This issue is preventing correct WordPress installations and database management, and I have gathered key evidence.

1. Original Problem with gästefotos.com (404 persists even after DNS correction): My main website (gästefotos.com) initially showed a 404 error. Upon investigating wp-config.php and checking the CyberPanel interface for this domain, I found that both the Database Name (DB_JNFMhVgmkfVUlZ) and Database User (DB_JNFMhVgmkfVUlZ) are incorrectly set to a string resembling my MariaDB Root Password. This panel-generated configuration error renders the website inoperable.

Crucially, I have now corrected the DNS A-records for gästefotos.com at GoDaddy to point directly to my server’s IP (213.239.217.121). However, gästefotos.com still displays a 404 error, confirming that the issue lies with CyberPanel’s handling of the domain on the server, not external DNS.

  1. CRITICAL FINDING: MariaDB “Access Denied” Error in Logs: While troubleshooting, I found a highly relevant warning in the system logs (journalctl), which strongly indicates the root cause of the database configuration issues. At Jun 20 19:59:04, MariaDB reported: Jun 20 19:59:04 localhost mariadbd[2000]: 2025-06-20 19:59:04 709 [Warning] Access denied for user 'root'@'localhost' (using password: YES) This suggests that MariaDB is denying access to the root user, which is likely preventing CyberPanel from correctly creating or managing databases and users during provisioning.

  2. Failed Test with a New WordPress Installation (linkyway.club): To confirm the issue was systemic, I attempted a fresh WordPress installation on a separate domain (linkyway.club) using CyberPanel’s “Application Installer.”

  • DNS for linkyway.club was correctly pointed to my server (A-record to 213.239.217.121).
  • linkyway.club initially displayed the default “CyberPanel Installed” page, confirming basic server/DNS functionality.
  • However, the WordPress installation failed with an internal CyberPanel error , likely due to the underlying MariaDB access issue: Installation failed. Error message: ['cannot unpack non-iterable int object [404]']
  • Following this failure, linkyway.club also displays a 404 error.
  1. Troubleshooting Steps Already Taken (External Factors Ruled Out):
  • ModSecurity/WAF: Confirmed not active or causing issues.
  • Hetzner Cloud Firewall: Confirmed to be already deactivated.
  • Manual DNS Entries: DNS settings for both gästefotos.com and linkyway.club (A-records, MX, SPF, DKIM, DMARC) have been correctly set up and are propagating.
  • Extensive Log Search: We have checked common CyberPanel, OpenLiteSpeed, and general system log locations (/var/log/cyberpanel/, /usr/local/lsws/logs/error.log, journalctl -u cyberpanel) and found no specific log entries for the “cannot unpack…” error, which suggests a logging issue within CyberPanel itself. However, the critical MariaDB “Access denied” warning was found in journalctl.

Summary: The persistent 404 for gästefotos.com despite correct DNS, combined with the MariaDB Access denied warning for the root user, the incorrect database configuration for gästefotos.com, and the failed WordPress installations on linkyway.club, strongly indicates a fundamental issue with CyberPanel’s ability to integrate with and manage MariaDB on this server. This appears to be a core software bug within CyberPanel itself.

As external factors have been ruled out and the issue is deep within the panel’s functionality, I kindly request your immediate assistance in diagnosing and resolving this critical flaw.

Thank you for your prompt attention to this matter.

Sincerely,

Ucakca

2

@usmannasir Sorry for the highlight, I’m looking for a solution and I’m already at my limit. I hope you have an idea.