Unable to connect to Overseer (Firefox extension)

[Gwouigwoui]

trafficstars

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

[jgwallace3]

I'm having the same issue.

[CaphalorAlb]

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.

[Gwouigwoui]

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.

[levifig]

Can confirm: works in Chrome, doesn't work in Firefox.

[sebcourant]

Same issue here.

Having a CORS error followed by NS_ERROR_DOM_BAD_URI in Firefox's Network Inspect tool.

[Fogest]

I am still unable to connect in Firefox

[GSKang94]

same issue in Firefox 😞

[morianhawke]

Same thing for me. It works in Chrome, but not Firefox, for the exact same, copy-pasted configuration.

[NetixQc]

Works in Chrome but getting this error in Firefox too.

[ZiIlaGit104]

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.

[jiznon]

same issue here. was stoked to find this extension existed, but no luck

[haggis444]

Yup, just found out about it and gave it a shot, same issue.

[soredake]

Same problem.

[Gwouigwoui]

Ok, got it working by creating a reverse HTTPS proxy on my Synology (don't forget to add the Websocket)! DDNS with Synology (xyz.synology.me), wildcart certificate with Let's Encrypt (*.xyz.synology.me), jellyseer using HTTP on port 5055, create a reverse proxy with jellyseer.xyz.synology.me port 443 (HTTPS) as input and localhost port 5055 (HTTP), add the Websocket bit, and voilà !

[bookish1303]

Any news on this one yet? Is there a possibility of bypassing it using something like Greasemonkey? Chrome works fine, but really hoping for a Firefox fix (anyways no updates for a year seems like this project may be dead?)