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:
- 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
Thanks, sounds like Squid will be perfect. I’ll just need to figure out some way to connect. I wish I could just open a port, but it hasn’t been working since I enabled IPv6 on my router. Do you think I could make it accessible through cloudflare tunnels?
Probably not, look into wireguard or tailscale.
Cloudflare tunnels won't work as Cloudflare won't tunnel HTTP proxy traffic, at least as far as I know.
What you can do however is have your home server VPN into your remote server, then your remote server will have no problem connecting to Squid over the VPN link. WireGuard is very simple to configure like that, probably 5-10 lines of config on each end. You don't need any routing or forwarding or anything, just a plain VPN with 2 peers that can ping eachother, so no ip_forward or
iptables -j MASQUERADEneeded or anything that most guides would include. You can also use something like Tailscale, anything that will let the two machines talk to eachother.Depending on the performance and reliability needs, you could even just forward a port with SSH. Connect to your remote server from the home server with something like
ssh -N -R localhost:8088:localhost:8080 $remoteServerand port 8088 on the remote will forward to port 8080 on the home server as long as that SSH connection is up.-Nsimply makes SSH not open a shell on the remote, dedicating the SSH session to the forwarding. Nice and easy, especially for prototyping.That seems overcomplicated for me honestly, but now I just thought that I actually can host the scraper on the home server, as the scraper itself only scrapes simple data, and the downloads are by a separate program.
The downloader talks to the scraper through HTTP, which I can publish through CF Tunnels, so it’s perfect.