[GH-ISSUE #27] Login failed when HTTPS-Only Mode is enabled in Firefox. #17

New issue

Closed

opened 2026-03-23 20:31:43 +00:00 by mirror · 1 comment

mirror commented

2026-03-23 20:31:43 +00:00

Owner

Originally created by @mikaran576 on GitHub (Oct 15, 2023).
Original GitHub issue: https://github.com/tubearchivist/browser-extension/issues/27

Hello!
I encountered a small issue.

In firefox, if the "HTTPS-Only Mode" parameter is set to "Enable HTTPS-Only Mode in all windows", then even when using URL within a manage exceptions (i.e. http://tubearchivist.local:8000).
Authentication will fail with the error "NetworkError when attempting to fetch resource."
If you disable this option, everything is fine.

Addon's console log (version 0.2.1)

ping TA server popup.js:138:11
sync cookies not set popup.js:203:15
Object {  } popup.js:211:13
autostart not set popup.js:213:15
message background.js listener got message Object { type: "verify" } background.js:249:11
GET: http://tubearchivist.local:8000/api/ping/ background.js:29:11
HTTPS-Only Mode: Upgrading insecure request “http://tubearchivist.local:8000/api/ping/” to use “https”. ping
XHROPTIONS https://tubearchivist.local:8000/api/ping/ CORS Failed
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://tubearchivist.local:8000/api/ping/. (Reason: CORS request did not succeed). Status code: (null).
HTTPS-Only Mode: Upgrading insecure request “https://tubearchivist.local:8000/api/ping/” failed. (M14-C1012) ping
XHRGET https://tubearchivist.local:8000/api/ping/
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://tubearchivist.local:8000/api/ping/. (Reason: CORS request did not succeed). Status code: (null).
TypeError: NetworkError when attempting to fetch resource. background.js:290:15
Verify got error: NetworkError when attempting to fetch resource.

thanks in advance

Originally created by @mikaran576 on GitHub (Oct 15, 2023). Original GitHub issue: https://github.com/tubearchivist/browser-extension/issues/27 Hello! I encountered a small issue. In firefox, if the "HTTPS-Only Mode" parameter is set to "Enable HTTPS-Only Mode in all windows", then even when using URL within a manage exceptions (i.e. http://tubearchivist.local:8000). Authentication will fail with the error "NetworkError when attempting to fetch resource." If you disable this option, everything is fine. Addon's console log (version 0.2.1) ``` ping TA server popup.js:138:11 sync cookies not set popup.js:203:15 Object { } popup.js:211:13 autostart not set popup.js:213:15 message background.js listener got message Object { type: "verify" } background.js:249:11 GET: http://tubearchivist.local:8000/api/ping/ background.js:29:11 HTTPS-Only Mode: Upgrading insecure request “http://tubearchivist.local:8000/api/ping/” to use “https”. ping XHROPTIONS https://tubearchivist.local:8000/api/ping/ CORS Failed Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://tubearchivist.local:8000/api/ping/. (Reason: CORS request did not succeed). Status code: (null). HTTPS-Only Mode: Upgrading insecure request “https://tubearchivist.local:8000/api/ping/” failed. (M14-C1012) ping XHRGET https://tubearchivist.local:8000/api/ping/ Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://tubearchivist.local:8000/api/ping/. (Reason: CORS request did not succeed). Status code: (null). TypeError: NetworkError when attempting to fetch resource. background.js:290:15 Verify got error: NetworkError when attempting to fetch resource. ``` thanks in advance

mirror

2026-03-23 20:31:43 +00:00

closed this issue
added the
not an issue
label

mirror commented

2026-03-23 20:31:44 +00:00

Author

Owner

@bbilly1 commented on GitHub (Oct 16, 2023):

That makes sense. You'll probably will have to setup https for TA for this to work. But that sounds like it's working as expected as in you are blocking all http traffic.

@bbilly1 commented on GitHub (Oct 16, 2023): That makes sense. You'll probably will have to setup https for TA for this to work. But that sounds like it's working as expected as in you are blocking all http traffic.