This is a solution to a problem I had while trying to access phpMyadmin as a Nginx user, not Apache.

As any developer using Bitnami Instance / Aws knows, the Instance they provide does not recommend direct access to phpMyadmin. Aws/Bitnami recommend to create a key pipe in the Ssh terminal and connect to the user's local address/port.

However, while I could use phpMyadmin without problems in Apache, I could not use it in Nginx. No matter what I tried, I couldn't use it.

There are some guide about this issue. This page (or troubleshoot page) provides a solution.

Manual recommend that it only need to change 80 to 443 in the command line:

'ssh -N -L 8888:127.0.0.1:80 -i KEYFILE bitnami@SERVER-IP'

-> 'ssh -N -L 8888:127.0.0.1:443 -i KEYFILE bitnami@SERVER-IP'

However, when I changed port 80 to 443, a 400 error (Bad Request) occurred. I tried to improve it for a long time, but it didn't work. I don't know if this is common. If you are facing this same problem, there are more things to consider. Enter something like this directly in the URL:

https: // 127.0.0.1:8888/phpmyadmin/,

not http: // 127.0.0.1:8888/phpmyadmin/

Keep in mind that it's https, not http.

That way, you won't get a 400 error. You must click on the 'ADVANCED' link on this screen and go inside/next page to finally see the phpMyadmin main screen.

Note: Http only throws a Bad Request 400 error on Bitnami instance, so the user thinks he himself made a mistake in the settings and keeps repeating the same thing. As you know, browsers hide http or https, so users overlook them.

You must accurately enter 'https://127.0.0.1:8888/phpmyadmin/' or 'https://localhost:8888/phpmyadmin/' to see the screen below.

I don't know if this problem is common among Nginx users, but there is a lack of information about it. The solution was very easy, but I'm writing down the answer so you don't waste a lot of time like I did. Happy New Year!