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

Upgrade to 3.10 causes all access to fail #14645

Closed
nboscia opened this issue Jul 9, 2019 · 1 comment
Closed

Upgrade to 3.10 causes all access to fail #14645

nboscia opened this issue Jul 9, 2019 · 1 comment
Labels
answered For when a question was asked and we referred to forum or answered it.

Comments

@nboscia
Copy link

nboscia commented Jul 9, 2019 •
edited

After upgrading to 3.10.0, both instances of Matomo are failing to log people in. After a dozen attempts and doing "Remember Me", I can sometimes get it to work for a single page. I confirmed directly inside the databases that users are still there with proper permissions and even admin is still set to super-user. I get errors that whomever I login as, does not have "View" permission for whatever page/site I'm loading, regardless of super-admin status or "View" set to access.

My gut is telling me this is a SiteMinder Issue, which we use a CA web agent inside Apache to do authentication for the admin access. I never had to configure proxy stuff inside Matomo before since we're not proxying any data through it, just doing an initial login. Do specific headers need to be passed through login? It seems like a cookie is not getting set. There are a lot of these errors in the Apache logs:

Error in Matomo: Zend_Session is currently marked as read-only.
@tsteur
Copy link
Member

tsteur commented Jul 14, 2019

Seems like a server configuration issue which may be better discussed in the forums: https://forum.matomo.org @nboscia

We don't know your exact server set up here so we can't be much of help unfortunately. Could you maybe post in the forums or check out our support plans https://matomo.org/support-plans/ ?

If you could otherwise investigate a bit more and have some hints for us what is happening, we can maybe work on a fix for it.

@tsteur tsteur closed this as completed Jul 14, 2019
@tsteur tsteur added the answered For when a question was asked and we referred to forum or answered it. label Jul 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
answered For when a question was asked and we referred to forum or answered it.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tsteur @nboscia