-
Notifications
You must be signed in to change notification settings - Fork 147
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
401 with Firefox 83.0 #263
Comments
Just want to let you know, those prefs will eventually be removed from Firefox, so we can't count on them for a long-term solution here. When you have a chance, please try setting those prefs back to False, reproducing the |
Well, I set them back to true, but no 401 in logs for now.. |
Those settings do not exists in Firefox for Android since last august. Probably reason, why I cannot get sync to work even with https. |
@virgoparna For Android version I'm using https://URL/token/ without changing any settings and it is working fine |
Got Android version to sync by new install. Old sync server was probably too old. |
So you did this with the current server which source is available here? w/o adding any SSL certs or whatsoever? You even did not change the URI to https://URL/token/1.0/sync/1.5 with or without trailing slash? |
I'm using 3 months old version with Lets Encrypt SSL. It is just https://URL/token/ without any /1.0/sync etc. |
Hello,
I just deployed my docker container, and with some research I was able to sync with my Android phone ( https://example.com/token/ ), however I'm unable to sync with my firefox desktop (83.0).
Docker logs says:
INFO:mozsvc.metrics:{"code": 401, "request_time": 0.00031304359436035156, "remoteAddressChain": ["1.2.3.4", "172.17.0.1"], "agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0", "path": "https://example.com/token/1.0/sync/1.5", "method": "GET"}
Also, there was crash or something inside, here is the log:
sync_logs.txt - I removed some ip's and url's
I tried with
http://example.com/token/1.0/sync/1.5
http://example.com/token/token/1.0/sync/1.5
http://example.com/token/
After setting these two to false and few relogins I was finally able to sync...

The text was updated successfully, but these errors were encountered: