• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Phpmyadmin is running on nginx but nginx not installed

Ahmad12

Basic Pleskian
Hello,

i've uninstalled nginx and php-fm from plesk panel.

but phpmyadmin info still showing it is running on nginx 1.6 and while uploading sql file i'm getting 503 gateway error.

any advice please
 
As stated in the other thread ( you might consider only using ONE thread for the same issue, to avoid double, trible... posts ), phpmyadmin runs via the sw-cp-server ( a very own Plesk-nginx-webserver ), which is a part of Plesk. The installed webserver components apache2 and/or nginx have nothing to do with it.

Please investigate any issues with phpmyadmin over the sw-cp-server - logfiles and/or configurations files.

 
ok.. i've checked the error log and found this:
2015/01/03 11:18:17 [error] 29740#0: *539 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: xxxx, server: , request: "POST /domains/databases/phpMyAdmin/import.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: xxxx:8443", referrer: "https://xxxx:8443/domains/databases/phpMyAdmin/index.php"
 
Hi Ahmad12,

such issue mostly indicate, that the FastCGI - process for the sw-cp-server isn't working properly or could be stuck for some reason, or isn't running at all for some reasons. Please consider restarting the sw-engine-fpm and maybe as well the sw-cp-server to solve your issue.

Please use ...

/etc/init.d/sw-engine restart && /etc/init.d/sw-cp-server restart
to restart sw-engine-fpm and sw-cp-server, or check the status with the commands "/etc/init.d/sw-engine status && /etc/init.d/sw-cp-server status"


If you experience such an issue quite regulary, please consider tweaking your depending configuration files for the Control Panel ( please see the link above to inform yourself about the paths ) or switch to a debug - log mode, to investigate the cause.
 
Back
Top