The learning part not working on Ubuntu linus Chromu
See original GitHub issueLooking forward for reporting a security issue:
Please report security issues by sending an email to security@freecodecamp.org
instead of raising a GitHub issue.
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
- Go to ‘…’
- Click on ‘…’
- Scroll down to ‘…’
- See error
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
Smartphone (please complete the following information):
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
Additional context Add any other context about the problem here. the Learning part is not working on Linus chromium browser, it keeps on saying "something is not quite right, a report have been generated and the freCodeCamp team have been notified. althought is working perfectly on windows chrome.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top GitHub Comments
Finally checked this myself and, yep, you can’t sign in on Chromium. Trying to sign in leaves you on https://api.freecodecamp.org/signin with the 502 error @SagirGarba showed above. Some sort of routing issue, I guess, but I have no idea why it’s only Chromium.
I’ve checked Chrome, Brave and Firefox and none of them have the problem.
cc: @raisedadead
Edit: there’s no information in the dev console.
Thank you for bringing this to our attention @SagirGarba, and for looking more into this @ojeytonwilliams.
Turns out this was a problem with the way NGINX handles really long SSO URLs with some browsers like Chromium. @ahmadabdolsaheb and I pushed a fix using the settings mentioned here: https://stackoverflow.com/questions/3704626/nginx-502-bad-gateway-error-only-in-firefox/3710649
@SagirGarba, could you try signing in again and let us know if you’re still having issues? Please don’t hesitate to reopen this issue if you’re still seeing those 502 errors.