view the rest of the comments
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.
-
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.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.
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!
Ok there is a TV and a pi on network 1 and a server on network 2, the pi can connect to the server through SSH or VPN or whatever is needed. The TV would like to connect to the server, however it can't run a VPN or anything like that so exposing the server would be a risk.
The SSH command on the pi is SSH -L 1234:localhost1234 remote_server
The ufw command was run on the pi, with the intention to allow the TV to access the forwarded port on the pi
ssh -L 1234:localhost:1234 remote_serverbinds the RPi'slocalhost:1234to remote_server'slocalhost:1234. You want to bind the port to something on the RPi that the TV can hit, so something likessh -L 192.168.1.5:1234:localhost:1234 remote_server, where192.168.1.5is the RPi's address.I think you also want
-Non thesshcommand.That worked thanks, I didn't know you could put an address like that in the -L command, and the -N is correct here too