97
submitted 4 months ago by kionite231@lemmy.ca to c/selfhosted@lemmy.world

Greetings,

my current ISP refuses to provide me a static IP and they also blocks incoming connection to my ipv6 so I can't host services on just ipv6 too. I will be changing my ISP when the plan expires.

without public IP I can host my own IRC bouncer but I would like to know what else can I self host? Thanks in advance!

top 50 comments
sorted by: hot top controversial new old
[-] just_another_person@lemmy.world 59 points 4 months ago

Anything. You don't need any services to be public unless you choose for them to be.

[-] kionite231@lemmy.ca 9 points 4 months ago

actually I was thinking about hosting my own fediverse service to own my data but I can't do that without a static public IP and domain name.

[-] rtxn@lemmy.world 37 points 4 months ago* (last edited 4 months ago)

As long as you're not behind CGNAT, you can use a dynamic DNS provider (like duckdns.org) and its web API to keep a record pointed at your IP. If you're behind CGNAT, Tailscale also has a service (Tailscale Funnel) that can expose an internal service to the internet.

You could also pay for a small VPS with a static IP, and set up a Wireguard tunnel to your home server and an HTTPS proxy to forward traffic through the tunnel.

Also, just in general, use Tailscale. It's serious black magic fuckery on the firewall.

[-] kionite231@lemmy.ca 6 points 4 months ago

Yeah I am behind CGNAT so I guess I have to use either Tailscale or wireguard as other users also suggested.

Thank you for the reply!

load more comments (1 replies)
load more comments (3 replies)
[-] sk@hub.utsukta.org 5 points 4 months ago

@whoareu cloudflare tunnel can easily help you do that. the only limitation is your domain will need to be from cloudflare. It works well, I am hosting an instance without any public IP and without exposing any ports.

[-] lordnikon@lemmy.world 5 points 4 months ago

Your domain need to be tied to cloudflare you don't need to buy one from them. I just moved mine to them didn't pay them a dime

[-] superglue@lemmy.dbzer0.com 2 points 4 months ago

You actually want a cloudfare tunnel if youre going to do that. It protects your real IP. Hosting a fediverse instance will draw attention to your real IP eventually otherwise.

[-] MangoPenguin 28 points 4 months ago

Basically everything. Self hosting doesn't rely on public access.

[-] StaticFlow@feddit.uk 21 points 4 months ago

Self host all your stuff and use tailscale if you just want to provide private services to yourself

[-] Shimitar@downonthestreet.eu 15 points 4 months ago

Rent a VPN, setup a wire guard tunnel and fuck your ISP!

Anyway having a real public IP on a residential block is basically impossible anywhere but in the USA, I guess.

[-] Darkassassin07@lemmy.ca 4 points 4 months ago

Public IPV4 here. It's not static, but very rarely rotates. DDNS ftw.

Telus Residential in Canada.

[-] aeternum 3 points 4 months ago

Straya. I have a static ip. Costs like 5$ a month

load more comments (5 replies)
load more comments (1 replies)
[-] ikidd@lemmy.world 13 points 4 months ago* (last edited 4 months ago)

Put everything behind Tailscale or another VPN and use it that way from outside devices. There should be very little need to have a public IP, and if there's something that has to be exposed, use ngrok, cloudflared or Tailscale Funnel.

[-] Voroxpete@sh.itjust.works 12 points 4 months ago

I just use a DDNS updater. That's honestly good enough for most purposes.

Alternatively, you could use a service like Zerotier, Tailscale or Netbird to create a virtual private LAN connection to a free Oracle VPS, then route the traffic from the VPN to your home network.

[-] fiddlesticks@lemmy.dbzer0.com 11 points 4 months ago

As someone in a similar situation I'd recommend using a free tier oracle vps with a wireguard tunnel to connect to you services. Effectively just using the vps as a proxy for your own network. Here's a guide that should work for your purposes https://github.com/mochman/Bypass_CGNAT

load more comments (1 replies)
[-] SexualPolytope@lemmy.sdf.org 11 points 4 months ago* (last edited 4 months ago)

The best way would be to use a VPS to proxy your traffic to you. You can achieve this for pretty cheap, just set up an wireguard tunnel to a cheap VPS. That's exactly how I access all my services from outside my home. As long as the VPS has a publicly accessible IP (most of them do), you being behind CGNAT should not be an issue.

[-] kernelle@0d.gs 3 points 4 months ago

This is the way OP

[-] Petter1@lemm.ee 11 points 4 months ago

You can self host anything like this, all you need is buying a domain and set something up like DynDNS which updates the entry of the domain with your new IPv4 as soon as it changes.

I would recommend to not open your services to public, but set up a wireguard (or other VPN) endpoint in your home, which you then use to access all your services.

I think, an alternative to that would be some servicees from tailscale or cloudflare, I suppose

[-] hendrik@palaver.p3x.de 11 points 4 months ago* (last edited 4 months ago)

I mean you can host anything. It's just not reachable from the outside. And Fediverse or anything that gets data pushed in, won't work. The common method to handle all of this is to use some tunnelling solution.

[-] billwashere@lemmy.world 10 points 4 months ago

Tailscale or Cloudflare will solve your problems.

[-] qaz@lemmy.world 10 points 4 months ago* (last edited 4 months ago)

You can use Tailscale, you can access your personal services with it but also expose public services with their Funnels system.

Keep in mind that while the clients are open source, their servers are running proprietary software.

[-] lorentz@feddit.it 8 points 4 months ago

I started using headscale (the opensource reimplementation of tailscale server) on a private vps. It is incredibly better compared to plain wireguard. I regret waiting so much before switching.

Something that really made my life easier: wireguard is poor at roaming: switching to and from my wifi created issues because the server wasn't reachable anymore from its public ip and wireguard didn't bother to query the DNS again to check the new IP. Also, configuration is dead simple because it takes care of iptables for you (especially good when you enables forwarding to a node).

Since the server just sends small messages for the control plane and all the traffic is p2p between the devices, the smallest vps with the smaller connectivity is more than enough to handle it.

[-] Xanza@lemm.ee 9 points 4 months ago

my current ISP refuses to provide me a static IP

So then use dynamic dns? HurricaneElectric offers DynDNS now and it's great. You can update it right over curl if you want. I have it mapped to a cli function;

~\downloads
❯ ddns
HTTP/1.1 200 OK
Cache-Control: no-cache, must-revalidate
Content-Length: 18
Content-Type: text/html
Date: Tue, 25 Feb 2025 09:24:18 GMT
Email: DNS Administrator <dnsadmin@he.net>
Expires: Wed, 25 Feb 2026 09:24:18 GMT
Server: dns.he.net v0.0.1

nochg {ip}
[-] kionite231@lemmy.ca 2 points 4 months ago

It's not only not static It's firewalled too! I can't ping it from outside the network

[-] Xanza@lemm.ee 2 points 4 months ago

Oh, damn. Not much you can do then. You may be eventually be able to get something outrageously complicated to work, but honestly it's just plain not worth it. Just get a cheap VPS.

Best you could do is a forward server with tailscale and a reverse_proxy, but I've never had any real luck getting that type of setup to work reliably.

[-] mbirth@lemmy.ml 2 points 4 months ago

Did you configure NAT to the service(s) and/or DMZ to your internal server in your ISP’s router?

Not allowing even ping seems like it is against any sane networking configuration.

load more comments (1 replies)
[-] sirico@feddit.uk 9 points 4 months ago

If this is just for personal use, I'd see if you can put their router in modem mode and go get a better router, then I'd just use tail-scale or WireGuard.

[-] kionite231@lemmy.ca 4 points 4 months ago

tailscale is looking good I might try that

load more comments (1 replies)
[-] Greg@lemmy.ca 7 points 4 months ago

Use Cloudflare's free tier tunnel

[-] Krik@lemmy.dbzer0.com 2 points 4 months ago

They'll shut it down if you send more than a few megabytes down that tunnel. It's ok if you just need a connection (for ssh and stuff) but anything that generates a lot of traffic will be blocked.

load more comments (1 replies)
[-] bdonvr@thelemmy.club 6 points 4 months ago

I just have a script that checks my IP every few minutes and changes the DNS record as necessary

[-] possiblylinux127@lemmy.zip 5 points 4 months ago

Why do you need to expose a service publicly?

[-] Shimitar@downonthestreet.eu 8 points 4 months ago

Why do you need to make a question questioning OP needs, when he is looking for a solution to a problem?

[-] vithigar@lemmy.ca 7 points 4 months ago

Because of the XY problem. The problem OP is stating may not actually be the source of the issues OP is experiencing.

Finding out what OP is trying to do will better inform a solution and may make the stated problem irrelevant.

[-] Shimitar@downonthestreet.eu 2 points 4 months ago

Good point, but did it solve anything?

[-] vithigar@lemmy.ca 3 points 4 months ago

OP doesn't seem to have responded, so no, but that's not the fault of the question.

load more comments (1 replies)
[-] bluGill@fedia.io 3 points 4 months ago

Because too often people are asking for a solution to the wrong problem. I can tell how to setup a car to drive from the Hawaii to Iceland, but odds are that is not your actual goal. (most often the correct answer is fly to iceland and rent a car, or perhaps just public transit in iceland. You can also put your car on a ship. It is possible to modify a car to drive on the ocean if that is really what you want to do)

[-] Shimitar@downonthestreet.eu 2 points 4 months ago

Darn, i really wanted to drive to Iceland, now, you are downplaying my needs. I feel offended! /s

load more comments (1 replies)
load more comments (1 replies)
[-] webghost0101@sopuli.xyz 4 points 4 months ago* (last edited 4 months ago)

I believe duckdns has a tool that checks your public ip on a schedule to update your subdomain. (Which they provide for free last I checked)

[-] Valmond@lemmy.world 3 points 4 months ago

That would solve not having a static IP, not solving having no port forward right?

load more comments (2 replies)
[-] nitrolife@rekabu.ru 4 points 4 months ago* (last edited 4 months ago)

Look:

  1. you can buy any VPS server or use free VM in Amazon cloud
  2. then connect your home PC to this VPS with VPN tunnel After that you have public IP address (on VPS) linked with you home server.
  3. configure VPS for pass through incoming ports to you home server After that you can host anything for anyone in v4 or v6 internet.
load more comments (1 replies)
[-] irotsoma 3 points 4 months ago* (last edited 4 months ago)

Use VPN or DDNS connected to your domain registrar. Of course DDNS might not update immediately, especially if your domain host is not the same as your DNS provider, so you might have outages for short periods when your IP changes. So, depends on if you're OK with that or what kind of connection you have and whether it changes your IP a lot.

Also, might be able to get an IPv6 address for free depending on your ISP or at least you can set up your router to request that your address block is retained for you. I know Comcast does this. Unfortunately, my ISP does not.

[-] sugar_in_your_tea@sh.itjust.works 2 points 4 months ago* (last edited 4 months ago)

I use a cheap VPS and connect all my relevant devices to it via a VPN (aldo self hosted w/ wireguard). It's $5/month and does the job.

load more comments
view more: next ›
this post was submitted on 25 Feb 2025
97 points (100.0% liked)

Selfhosted

46672 readers
695 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS