Selfhosted

39435 readers

6 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:

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:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Looking for an alternative to cloudflare tunnel (lemmy.today)

submitted 1 year ago by [email protected] to c/[email protected]

27 comments fedilink hide all child comments

Hi, I moved this year to another city, because my internet provider didn't give me a dedicated ipv4 address I can't use a dyndns like duckdns. Another thing to mention is, that I have a dslite tunnel. So I can't set up dyndns...

So my recent setup is a truenas server sitting under my desk. This is connected via cloudflared to the cloudflare tunnel. There I have my services like seafile or nextcloud configured. They are all pointing to a traefik instance that routes the traffic to the right container.

So to summarize what I have:

Truenas server
- multiple services
dslite tunnel
own domain
Cloudflare tunnel
v-server
- Nginx
- docker

To visualize the route the traffic is going

Internet - cloudflare tunnel - cloudfared docker - traefik docker - service (nextcloud) docker

So I want to setup something on my v-server that routes the traffic to my homeserver (truenas)

Internet - DNS (cloudflare) - v-server - (magic docker service on truenas) - traefik docker - service (nextcloud) docker

Does someone have an idea how to solve this?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 12 points 1 year ago (1 children)

My suggestion would be to setup a VPN service in your publicly available v-server. The most suggested solution is wireguard.

Then you can connect your truenas to that VPN and make it accessible, maybe via nginx.

The traffic flow would be:

nginx on v-server --(wireguard)--> traefik --> Nextcloud

[–] [email protected] 1 points 1 year ago (2 children)

That's a good point. But that's also the point where my tinkering won't help me... Do you have a writeup or a yt video where nginx points to the wireguard VPN? Another question. If I set up the wireguard tunnel, how can I just route the traffic from traefik?

[–] [email protected] 4 points 1 year ago (1 children)

I found this writeup and it looks correct, but I have not tested it.

The author posted a nice graphic that shows the idea:

[–] [email protected] 3 points 1 year ago (1 children)

I'm not sure I understand why they need two Caddy servers. The first one should be a simple port forward, no need for a proxy forward. Unless they want to do something with the connections at application level, but it sounds like they simply forward them as-is.

[–] [email protected] 2 points 1 year ago

You need two caddy servers if there are other websites on the vserver that will use port 80/443. If not, port forwarding (eg. with iptables) will work.

[–] [email protected] 1 points 1 year ago

Basically once you have WG set up, you will have an additional interface with it's own IP in "ifconfig". At that point all the ports are available and you can just point your reverse proxy to them (sorry I'm an NGINX user, I have no idea how Traefik works).

Additionally don't forget to add keep-alive in your WG config so that the service doesn't shut off once traffic stops going between both servers.