Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unable to login in some instances upgraded to beta3 #13260

Closed
mattab opened this issue Aug 7, 2018 · 3 comments
Closed

Unable to login in some instances upgraded to beta3 #13260

mattab opened this issue Aug 7, 2018 · 3 comments
Assignees
@diosmosis
Labels
not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org. Regression Indicates a feature used to work in a certain way but it no longer does even though it should.
Milestone
3.6.0

Comments

@mattab
Copy link
Member

mattab commented Aug 7, 2018

After upgrading demo and demo2 to the beta3 (this update applied both beta2 and beta3 SQL upgrades), logging in does not work anymore: although there is no error and it appears to work, I'm still logged out after logging in.

However it seems to work fine on the localhost running beta3 also upgraded from beta1. It will be great to investigate this on demo/demo2 so we can address the root cause.
@mattab mattab added not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org. Regression Indicates a feature used to work in a certain way but it no longer does even though it should. labels Aug 7, 2018
@mattab mattab added this to the 3.6.0 milestone Aug 7, 2018
@diosmosis diosmosis mentioned this issue Aug 7, 2018
Merged
@diosmosis diosmosis self-assigned this Aug 8, 2018
@GreenReaper GreenReaper mentioned this issue Aug 8, 2018
Closed
@GreenReaper
Copy link

GreenReaper commented Aug 8, 2018 •
edited

The commit suggests that this is due to a discrepancy between SQL time and PHP which might cause passwords to maybe look like they're expired. Is there a way to resolve this for those who hit it, perhaps through SQL? I'm not sure how to autoupdate once -b4 is out because I can't login...

@Findus23
Copy link
Member

Findus23 commented Aug 8, 2018

The easiest way to fix this is apply the changes from #13261 manually.

So either make the changes you can see in https://github.com/matomo-org/matomo/pull/13261/files
or download https://patch-diff.githubusercontent.com/raw/matomo-org/matomo/pull/13261.patch and apply it with patch -p1 <13261.patch

But maybe wait a minute until @diosmosis finished the changes.

@GreenReaper
Copy link

OK. I hackily just logged in to mysql and set
update piwik_user set ts_password_modified = '2018-08-08 18:52:56';
and it let me login. FWIW my system time zone is CEST and time_zone in MySQL is SYSTEM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@diosmosis diosmosis

Labels
not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org. Regression Indicates a feature used to work in a certain way but it no longer does even though it should.
Projects
None yet
Milestone
3.6.0
Development

No branches or pull requests
4 participants
@diosmosis @GreenReaper @mattab @Findus23