-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Unable to connect to Overseer (Firefox extension) #47
Comments
I'm having the same issue. |
I wasn't able to get it to work with my home network IP address, either. It did, however, work when using the domain name I set up for online availability. Might be an SSL issue, or something of the sort. To be honest, I simply accepted that my workaround functions and stopped investigating further. |
Still no success for me. I tried setting it up from outside, same issue. I can access Overseer (http://xxx.synology.me:5055), but when I enter the same info in the extension, same error message. |
Can confirm: works in Chrome, doesn't work in Firefox. |
Same issue here. Having a CORS error followed by NS_ERROR_DOM_BAD_URI in Firefox's Network Inspect tool. |
@RemiRigal are you aware of this ? |
I am still unable to connect in Firefox |
same issue in Firefox 😞 |
Same thing for me. It works in Chrome, but not Firefox, for the exact same, copy-pasted configuration. |
Same here. Overseerr is on my Docker host and is accessible via other apps/browsers but the Firefox add-on will not connect. The Chrome add-on will. |
same issue here. was stoked to find this extension existed, but no luck |
Hi,
My Overseer is installed on my Synology NAS through Docker. I can access it locally without any issues at http://192.168.2.10:5055/
However when I try to use the extension and login for the first I get the "unable to connect to Overseer" error.
Not sure what I'm doing wrong: I use the IP and the port from above, server's path is empty and I just copy the API key from Overseer. Any clues?
Thanks
The text was updated successfully, but these errors were encountered: