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
Can't login in Chrome #14210
Comments
Please check if the cookies get correctly forwarded to the user. |
Hi, thanks for your reply. Any tips on how I would do that? Also why does it work in Firefox etc if it's an issue with the cookies? Thanks! |
Browsers du handle cookies differently. You should be able to get this information from the browsers dev tools. |
could you upgrade to the latest Matomo version? see https://matomo.org/docs/update/ if you still experience this issue afterwards, could you maybe create a phpinfo.php file with the content Hope we can troubleshoot this issue and find the root cause! |
Check if you use http vs https maybe in another browser? |
I am forcing https. |
I have the same problem, how to solve it |
hi ,i can login in chrome finally by adding the port after X-Forwarded-Host |
Awesome thanks |
Hi, I have two installations of 3.8.1, one a "manual" installation and the other with Docker (I'm migrating the first one's db to the second one). I can't login on either of them if using Google Chrome, while I have no problems with Firefox or Safari. I have tried uninstalling Chrome completely and even on another Mac I have the same issue. Whenever I enter my credentials I get the following error:
By doing a lot of searching, I have tried so many things but nothing has worked so far. I have tried several combinations of settings in config.ini.php concerning proxy but I wonder why in other browsers it just works. At the moment the settings in the config.ini.php are as follows:
Matomo is behind Nginx in both installations and the proxy settings are as follows (e.g. for the Docker installation):
What can I do to be able to log in with Chrome?
Thanks in advance!
The text was updated successfully, but these errors were encountered: