this post was submitted on 25 Apr 2026
39 points (93.3% liked)

Selfhosted

60542 readers
861 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. 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. Tags [CBH] or [AIP] are required, see the link in Rule 8 for details.

  8. 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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
39
Looking for information on setting up a VPS to forward traffic (piefed.zeromedia.vip)
submitted 2 months ago by guynamedzero@piefed.zeromedia.vip to c/selfhosted@lemmy.world
28 comments fedilink hide all child comments
 

Context:

Over the past few months, Xfinity has just been causing me so many problems with self-hosting. Not having a static ip isn't actually that much of a problem for me, I was able to set up a little docker container that automatically changes my dns records when my ip changes. However, pretty frequently, they'll reset my router/gateway's firewall configuration, which blocks basically all ipv6 traffic by default, and the other day, they even removed my port forwards while I was away, and hid my server from the port forwarding screen so I couldn't add them back until I got physical access to the server.

So, I've come to the realization that I should probably set up a VPS, since that should solve basically all of my issues. All I want is something that can forward/proxy gigabit traffic to my server, probably over something like wireguard.

To be clear, I still want all of my services to run on my server, I just want the VPS to route the traffic.

And, said VPS preferably has ipv6 in addition to ipv4 access, and gigabit download, though none of those are strict requirements.

Questions:

Are there any issues or limits with this setup that I'm not considering?

Is there a better solution?

Assuming the previous Q's are fine:

What's a good VPS provider for this?

What software should I use to actually do the forwarding/proxying?

you are viewing a single comment's thread
view the rest of the comments
[–] Onomatopoeia@lemmy.cafe 2 points 2 months ago (2 children)

How would this work if the router doesn't have a port forwarded to an internal address?

[–] hendrik@palaver.p3x.de 1 points 2 months ago

I'd let the home server connect to the VPN on the VPS so there's a direct tunnel between the VPS and the home server. And the router is pretty much irrelevant. You can of course choose to terminate it on the router as well, bus as you said, that requires either a second forwarding. Or the entire home network to be bridged or routed.

[–] frongt@lemmy.zip 0 points 2 months ago

The VPN tunnel is initiated from inside the home network.