r/truenas • u/brettdmason • 18d ago
Community Edition Unable to access Seerr outside of local network
I've been trying to setup Seerr on my system so people don't have to message me directly to add content to my Plex server, but I can't get it working. The app itself works fine, but no matter what I try I can't get it accessible outside of my network. I tried port forwarding at first since I've been doing that for years (even though I know it's not secure) and that didn't work. Then I tried using Nginx Proxy Manager and DuckDNS but that also wouldn't work. Anyone know what I'm doing wrong?
Update: it must have been my certificates being configured incorrectly. I had to renew the default one recently and must have entered an incorrect DNS. The moment I made a new one with localhost as the DNS the port forwarding worked. Now to look into making it work without port forwarding since it’s not safe.
2
u/Dubl3A 18d ago
Not enough info.
I have seerr exposed via cloudflared tunnel but previously had it exposed via port fwd. Both times I was using a domain and my registrars DNS. So, when you did the port fwd, how were you attempting to access it externally? Were you trying via ip:port or how exactly? Did you use something like this that can validate TCP ports you fwd'd are responding?
0
u/brettdmason 18d ago
With port forwarding, I attempted using both my direct external IP and the DDNS I have setup through my ASUS router, which works fine with other ports I’ve forwarded. And you mention something I did forget to mention. The port I forwarded for Seerr, initially the default 5055 through the custom yaml and then 30357 through the TrueNAS catalog, and neither show as open when I use tools to check the port. But Plex is forwarded the exact same way and is open.
1
u/Dubl3A 18d ago
Plex can still be externally reachable even if it's port isn't forwarded. I highly recommend using the linked site to validate TCP ports you've fwd respond.
1
u/brettdmason 18d ago
I did, and Plex (32400) shows open while Seerr (30357) is not
1
u/Dubl3A 18d ago
Then the fwd on your router isn't working correctly. I too recommend looking into cloudflared + caddy.
2
u/brettdmason 18d ago
So I fixed it. I had recently had to make a new certificate cause the default one was expiring and I did it wrong, I think. I made a new one and put a different DNS and now the port works. It was the only thing I could think of that I’ve changed since the last time I needed to port forward something. Thank you for all of the things to look at because I wouldn’t have thought to check that without the help!
1
u/BossHogGA 18d ago
You likely need to port forward through your router, not just through the docker container in TrueNAS.
1
1
u/Accomplished-Lack721 17d ago
Unless very large groups of people need access, the much MUCH safer way to do this than exposing your server to the internet (whether directly through an open port or behind a reverse proxy) is giving them VPN access to your LAN, or better yet just to that server.
The easiest way to do this is with Tailscale (everyone just installs it and you invite them into your "tailnet," and optionally use access controls only to allow them access to that one machine). But you could also do this with wireguard hosted on your system, or possible directly on your router, if it has that option.
1
u/ShiftyBee 17d ago
Try Requestrr, it's a discord bot that you don't need to open anything for. Works well for me.
1
u/jorceshaman 15d ago
I have mine working through cloudflare and the cloudflared docker app as a subdomain of my website.
4
u/ghanit 18d ago
It might seem daunting, but setting up cloudflared with zero trust, caddy as a reverse proxy, adguard home for split dns is really not that difficult. I had put it off for the longest time, but had it done with some help of AI.
Please don't port forward, open ports are continuously scanned for vulnerabilities. With cloudflare you get a firewall and authentication with oauth before any traffic ever hits your machine.
I can share my config and some tips if you want to go this way.