Closed
Bug 1275429
Opened 10 years ago
Closed 10 years ago
SEC_ERROR_UNKNOWN_ISSUER connecting to api.accounts.firefox.com
Categories
(Firefox :: Sync, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: jeremc343, Unassigned)
Details
Attachments
(1 file)
|
39.93 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0
Build ID: 20160523113146
Steps to reproduce:
Tried to sync my Firefox account.
Both from the hamburger menu and from the options sync menu
Actual results:
I get the message "unexpected error".
Uninstalled Firefox completely and reinstalled
Deleted all the Mozilla folders under users/me/appdata (windows 10)
Tried different Firefox accounts (all of which work on other devices, as long as they aren't on my WiFi)
My android phone which is also connected to this account can sync fine as long as it isn't on my WiFi.
I tried to hit https://api.accounts.firefox.com from my desktop and I get the attached screenshot.
When I try it on my android phone while connected to my WiFi, the page never returns. However if I disconnect from my WiFi it returns a JSON result.
I haven't been able to sync for at least a couple of weeks, not really sure how long.
Expected results:
Should have gotten a valid certificate back from api.accounts.firefox.com
Updated•10 years ago
|
Component: Untriaged → Sync
Comment 1•10 years ago
|
||
(In reply to jeremc343 from comment #0)
> Tried different Firefox accounts (all of which work on other devices, as
> long as they aren't on my WiFi)
It sounds like your wifi connection might be using a proxy - do you know if that is the case? What ISP are you using?
Flags: needinfo?(jeremc343)
Summary: Firefox Sync Unexpected Error → SEC_ERROR_UNKNOWN_ISSUER connecting to api.accounts.firefox.com
Comment 2•10 years ago
|
||
No word from the reporter - please reopen if you have more information.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(jeremc343)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•