this post was submitted on 29 Jan 2026
44 points (100.0% liked)
Selfhosted
60366 readers
701 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There are far better, more secure ways to do this. You could use a reverse proxy. You could use tailscale. You could use wireguard.
The last thing you should do is open Frigate's port to the net.
Just answering the question you asked.
I know, but it seemed like there was confusion about my intended point, which is that you should never expose it to the open internet. It wasn't a question I really intended to be answered since I know that was their intention. My confusion is why do that when there are secure alternatives, some of which are easier than opening a port.
Inexperience or lack of effort. I don't know any method easier than just opening the port.