Selfhosted
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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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!
view the rest of the comments
~~I don't think simply forwarding the port actually works with free Plex anymore. I think if the server has a different public IP from the client it asks you to pay, even if you're connecting to the server over LAN.~~
Edit: That doesn't appear to be true. I'm not entirely sure how Plex is checking whether you're trying to stream remotely. In my case at least it works if I connect to my server using the LAN IP, but not if I use DNS (even though it resolves to the same IP). Maybe I'm missing something to allow it to work using the hostname.
Interesting, maybe they check whether it's a domain/remote IP on the client side to prevent usage of a reverse proxy.
I checked the logs and it said it was assuming a remote connection because there was an unknown hostname in the headers (I forget the exact wording). It was because the hostname I was using didn't match the hostname configured in the server's OS (one I set up on my local DNS server).