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.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 30 days old, your post is exempt from this rule as long as you continue to engage in comments.
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
Your 142.x.x.x will be your public IP address. All devices on your network share that public IP. They all have a unique private IP address too, accessible only on your network. It probably starts with 192.168.x.x, but it could be 10.x.x.x or even less likely 172.16–31.x.x.
If you want to operate a web server that users can go to by typing https://youdomain.com/, you'll need to forward from ports 80 and 443 through to the internal IP address of your server, using the "port forwarding" settings on your router. What port on the internal IP you route to depends on how your server is configured. But a basic default configuration is fairly likely to be 80 and 443, too.
Since you have a reverse proxy, all traffic from your router should go to that. Then you use that to send the appropriate traffic to the appropriate server based on whatever rules you want to apply. (e.g. siteone.mydomain.com goes to server 1, sitetwo.mydomain.com goes to server 2, or mydomain.com/siteone goes to server 1, etc.).
It depends on how you want to do it; how your reverse proxy server is setup. I use Pangolin running on a VPS as my proxy server. It uses a tunnel ("Newt") between web servers running on my home network and the VPS, so I don't need any open/forwarded ports on my home router.