I opened the ports for Overseerr to be accessible outside my network but when I have a user try to access it they can't see the page
#Issues getting seerr to be accessible to other users outside my network
pale sail
twilit latch
Could you be a bit more specific about your setup please ?
First, how is seerr deployed ?
pale sail
using Docker for Windows i have it deployed using the default port of 5055, and with that port forwarded
but every time I try to access the external IP with the port i get a "sent an invalid response." error
twilit latch
using Docker for Windows i have it deployed using the default port of 5055, and ...
How is the port forwarded ? ISP router ?
pale sail
yeah, I have a UniFi Dream Machine SE with the ports forwarded
sorry im very new to the whole docker thing
twilit latch
Can you reach seerr from you pc ?
twilit latch
sorry im very new to the whole docker thing
No worries
pale sail
yes using a local IP but not the external
twilit latch
And are you sure your router can reach seerr ?
twilit latch
I'm a magician 🤓
pale sail
i wonder if i was just being inpatient with it?
pale sail
an ip, but i know the IP is accessible as its the same one i use to host game servers on
muted acorn
Just a heads up, you may want to consider setting up a reverse proxy instead of simply forwarding ports. Forwarding ports is the most simple way to get external access, but it’s also very insecure. With a reverse proxy, you could use a proper URL instead of your IP address, and it would allow you to use https with automatically generated security certificates, instead of using regular insecure http requests.
muted acorn
an ip, but i know the IP is accessible as its the same one i use to host game se...
Especially if you’re hosting multiple things, like game servers. Having a URL to give to your friends is much easier on their end, instead of just giving out a WAN IP that your ISP can change whenever they want.
pale sail
i actually did invest in a dns host
muted acorn
i actually did invest in a dns host
Nice. Did you get the reverse proxy set up? That will allow you to avoid opening ports for every single service you host. You’d only need to open two ports for your reverse proxy, (80 for http and 443 for https traffic).
The reverse proxy would take the incoming requests on 80/443 and verify that they are valid, then redirect them to your various services as needed.
So like you’d tell your DNS provider to forward {service 1}.example.com to your WAN IP on port 443 for https. You’d probably want to configure it to upgrade http requests to https while you’re at it. Then you’d tell your reverse proxy to take incoming requests for {service 1}.example.comand forward them to{LAN IP address}:{Service 1’s port number}``.
Then repeat for service 2, 3, 4, etc… You don’t need to open more ports for each service, because your reverse proxy is taking care of that on 80 (for http) and 443 (preferably, for https). The reverse proxy will also be able to automatically obtain and renew https certificates, so the https requests will be valid and your traffic will be safely encrypted. And you get a nice pretty URL to give to your friends.
Like if you didn’t set up a reverse proxy, you probably just have your DNS provider sending http requests directly to your service’s port number. And any attempts at using https will show security errors, because they’ll be self-signed certificates that are generated directly by the service.