i can’t access Adminer at http://localhost:10005. There is error displayed like in a title. I try this on Pop OS (Ubuntu 20.04 based distro). Is there anything blocking this port? How to find out what the problem is?
PS: Sites work just fine with domain names (for example: domain.local) and with SSL, and also Mailhog works at http://localhost:10000 without an issue.
seems the problem is not resolved yet. Adminer seems to be working fine on PHP7.3 but not working on PHP7.4 on linux systems i tried it on latest popOS and mintOS.
Thanks everyone for being persistent and working with me to reproduce this. I’ve finally been able to replicate on my Ubuntu machine. It looks like, for some reason, Local thinks that an existing FPM instance was already on the socket:
I’ve created a bug report for the team to take a closer look and see what can be done!
I’ve also moved this forum topic under the “Bugs” category so that it can be voted on, so to help me show how important this feature is to you, be sure to up-vote!
We’re facing this same issue on Ubuntu on both Chrome and Firefox. We’ve tested this on both v6 and v6.1. Our port number 10010. The issue actually happens on all sites and they have different ports for Adminer - 10015, 10016 and so on.
This is impacting our workflow a lot so it would be really helpful if this can be solved soon. Or if there’s a temporary workaround to access database, do share that. We tried TablePlus extension but the button for that shows disabled. Thanks.
I have the same experience using elementary OS (Ubuntu based distro), Adminer works on PHP 7.3, fails on 7.4 & 8. Disappointing as WordPress recommends PHP 7.4 or greater and I’m sure we’d all prefer for our local dev environment to mirror production.
I am able to access Adminer running PHP 7.4.1 using the next sequential port number (for example if Adminer opens http://localhost:10006/ I am able to access Adminer using port http://localhost:10007/)
Yesterday we put out a stable release for Local 6.2.0 which includes a fix for Adminer on Linux. Check it out and let us know if you’re still experiencing issues.