Upgrade 2.0 -> 2.1.1 not working about teampass HOT 15 CLOSED

It seems that you didn't entered a username. Can you please confirm?

Note: This problem of "no error message" has been corrected in next 2.2.

from teampass.

No, I did enter all fields.

from teampass.

Well perhaps is it not that you haven't entered a field.
The error indicates that the access is not allowed for the expected user.

Check your database credentials ... take the ones from your previous settings.php file.

from teampass.

No, I am absolutely 100% sure all fields were entered with the proper details.

from teampass.

On top of that, all information came from the previous settings.php.

from teampass.

Hum strange ... this error is a mysql error.

Can you check if your credentials are ok via phpmyadmin for example.

Perhaps have you any "special" characters in your pass, login? can you tell me so that I can test with those?

from teampass.

from teampass.

Hum I've done a lot of tests and I can't reproduce this issue.
I've tested all those special characters and others without success.

If it was a variable problem, every one should have it. I'm pretty sure it is server related.
Maybe can you let me an access to your server so that I can check with you?

from teampass.

That won't be possible as its internal :)
I've tried it again today with the latest git code, and it was still the same problem.

Please note that this was not a problem at all when going from cPassman (1.8) to TeamPass 2.0.
The server it is running on is a normal nginx + php-fpm setup, but that should not be the reason.

from teampass.

Can you do a simple test?
Launch "install.php" instead of "upgrade.php".
Go to step of credentials testing and tell me if it succed

from teampass.

It says "Impossible to get connected to server" yet the original installation is more than capable of doing so..
If I use a different user (with a password with only a-z 0-9) it works fine.

I've just created a new MySQL user (+same grants) with the same type of password (no special chars) and it works as well.
I think we can safely conclude that TP ironically does not like strong passwords for database connections. :)

from teampass.

Can you give me the kind of password you have set?

change the "normal" letters by others so that I can have the same "complexity" level

Indeed I've done tests with special characters but perhaps not enough

from teampass.

Here you go:

jFDm3xj#=fvGHbn55}\$

This apparently contains a few more characters than I initially thought.

from teampass.

I've just changed my DB account pw with this password and do the test.

And it is ok ... "Connection is successfull"

Very strange ... I've tested on pre-release 2.1.2 but not changed this part of the code

from teampass.

Still an issue with strong passwords but fine with normal ones.

from teampass.