the last working version is 4.6.2. Since 4.6.3 it is not possbile to login anymore.
I'm aware of this https://www.adminer.org/en/password/ , but all of the mysql users do have passwords.
This is the error report of adminer which is wrong
Access denied for user 'root'@'localhost' (using password: NO)
login at the terminal is working fine (with password).
Any hints why it fails?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't think so, I use the single adminer-mysql variants, but even the full adminer does not work. I tried also different language specific files. No plugins at all.
I double checked the user and their passwords. All password fields are filled with a hash.
MariaDB [(none)]> SELECT host, user, password FROM mysql.user;
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a fresh installation [4.7.0] on my server and not able to login either, only login window available. Same result with MySQL and sqlite3. I tried also login-password-less plugin but without success. Documentation should cover also installation on web server, hard to be sure about data asked on the login fields, e.g. server name and login credentials.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My case is solved with person that works with PHP language.
Solution was to use provided code .
My challenge was to understand what to do because missing instructions - now I know that server name is not required and login password is set in provided sqlite.php file which need to be renamed as index.php. If you are having additional plugins or adminer in subdirectory, those modifications need to be made similar as instructed with original index.php file. Below is my index.php file.
Hi guys- I am having problems with 4.7.3, although I think the change happened in 4.7.2 but I skipped that version. I was using the following to automatically login:
same here. I love/hate this project. I've been fighting this for years. Why not build in an auto login feature? I'm spending a whole day doing something that should be 3 lines of code.
Whats ironic is that the login/auth stuff is so convoluted that you have to implement integrations in a very insecure way to make it work.
Nobody should have an app like this on the internet without firewall protection. Every possible exploit protection shouldn't be in the code. There's simply no scenario where the app address shouldn't be whitelisted.
👍
1
Last edit: Danial 2019-12-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I see that after using login form which is in iframe it will broken my own session. When I log again into my platform a go to first time to adminer url then its logged and i see adminer interface but after reload page adminer will broke my session again.
When i opening iframe with adminer at bottom of my php file is my own session_start().
But adminer wants do it the same.
I see this error message:
Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at adminer.php:2035) in adminer.php on line 71
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Not sure if it is applicable in your cases, but try login via HTTPS - even on localhost/same machine. If you try to login on HTTP protocol, you may get 403 (forbidden) and thus would not login.
It may not address your case - but it is worth trying.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Same here, 4.7.5 is working fine to login a mysql user ('user_wp'@'localhost'), whereas in newer versions auth is broken, including in 4.8.1. Looks like there is no true solution to that...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
the last working version is 4.6.2. Since 4.6.3 it is not possbile to login anymore.
I'm aware of this https://www.adminer.org/en/password/ , but all of the mysql users do have passwords.
This is the error report of adminer which is wrong
login at the terminal is working fine (with password).
Any hints why it fails?
Is it possible that you override the
Adminer
class, either by a plugin or a customization? If not then Adminer just passes the password to the driver.I don't think so, I use the single adminer-mysql variants, but even the full adminer does not work. I tried also different language specific files. No plugins at all.
I double checked the user and their passwords. All password fields are filled with a hash.
I have a fresh installation [4.7.0] on my server and not able to login either, only login window available. Same result with MySQL and sqlite3. I tried also login-password-less plugin but without success. Documentation should cover also installation on web server, hard to be sure about data asked on the login fields, e.g. server name and login credentials.
My case is solved with person that works with PHP language.
Solution was to use provided code .
My challenge was to understand what to do because missing instructions - now I know that server name is not required and login password is set in provided sqlite.php file which need to be renamed as index.php. If you are having additional plugins or adminer in subdirectory, those modifications need to be made similar as instructed with original index.php file. Below is my index.php file.
Last edit: Rampe 2018-12-26
Yeah, any other solution to fix that?
seems to be fixed with 4.7.2
Hi guys- I am having problems with 4.7.3, although I think the change happened in 4.7.2 but I skipped that version. I was using the following to automatically login:
but this no longer works. Is this an intentional change, or a bug? Is there some other way to automatically login with the new version?
Thank you.
Last edit: adrianbj 2019-09-12
Hi ! I have this issue with Firefox 71 .... dont know why (maybe cookie related) ...
Not work for me too.
same here. I love/hate this project. I've been fighting this for years. Why not build in an auto login feature? I'm spending a whole day doing something that should be 3 lines of code.
Whats ironic is that the login/auth stuff is so convoluted that you have to implement integrations in a very insecure way to make it work.
Nobody should have an app like this on the internet without firewall protection. Every possible exploit protection shouldn't be in the code. There's simply no scenario where the app address shouldn't be whitelisted.
Last edit: Danial 2019-12-08
Same here! 4.7.4 worked perfectly fine, with 4.7.5 it's not possible to login anymore. Going back to 4.7.4 instantly fixes the issue.
Still no reaction from Adminer developer? OMG. See how many views is on this post and others.
Last edit: stan 2020-01-21
Yeah :/ This project is horribly broken and seems to be abandoned by the developer(s). Maybe we should fork this to GitHub and fix it ?
I couldn't reproduce the issues. Perhaps the simplest solution for you is to set up the password for the database server.
I see that after using login form which is in iframe it will broken my own session. When I log again into my platform a go to first time to adminer url then its logged and i see adminer interface but after reload page adminer will broke my session again.
When i opening iframe with adminer at bottom of my php file is my own session_start().
But adminer wants do it the same.
I see this error message:
Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at adminer.php:2035) in adminer.php on line 71
Do you have any solution?
Not sure if it is applicable in your cases, but try login via HTTPS - even on localhost/same machine. If you try to login on HTTP protocol, you may get 403 (forbidden) and thus would not login.
It may not address your case - but it is worth trying.
Same here, 4.7.5 is working fine to login a mysql user ('user_wp'@'localhost'), whereas in newer versions auth is broken, including in 4.8.1. Looks like there is no true solution to that...
Solution for me - login with HTTPS instead of HTTP works.
After alot of try/fail I found the solution to this: