hi everyone,
I was just about to self-host a Ghost blog but then was warned that my ISP might change my external IP address at any time, so I would need to pay for a static IP address.
Is that true?
(I’d not seen much about that in stuff I’ve looked up so far about self hosting)
You must log in or # to comment.
You only need a static address for hosting email or VoIP.
You can do just about everything else with DDNS (dynamic DNS). However with DDNS, you will have downtime until the DDNS update takes effect and propagates to clients. This can be seconds… or hours. Depends on the DDNS service and TTLs that they set and how quickly your script/DDNS client works to push the update out.
You should check how often your address changes and check how quickly your DDNS solution pushed the update out. If it’s 10 seconds every 10 months, you will likely find that perfectly acceptable. If it’s an hour every other sunday… maybe not. But only you will know how much downtime you can tolerate.
I always will take static IP personally. But it’s not technically required and you can work around it if you want to save the 10-15$/month.
Edit: You could also argo tunnel if you’re okay using cloudflare. But I don’t think that answer is particularly in scope of the question. But just in case it’s useful to someone out there I’m adding this edit. Doesn’t fix the PTR requirement for Email and VoIP stuff though.
I run an smtp relay exactly for that kind of stuff with emails. Clients still like wordpress and this is easy to use, many other will accept an smtp relay/service like say gmail (the first one I could think of)
Yeah that’s another option as well… Services like dynu.com or smtp2go.com do exist… but you have to pay for them and there is a risk that the service can open/read your messages.
chance you take with pretty much everything you don’t control. I do use as much as I can to protect emails (not that much really)
Well yes… but if you’re goal to self-host is to control your data, it’s a bit counter productive to use those relays services that inject that problem right back into your setup again.
Edit: I’m not necessarily arguing… just putting the information out there that the services exist, but might not be a good fit.
oh yeah - but I don’t recommend anyone really self host an smtp server… many many issues right there especially as most isps block the ports required and the IP addresses are often blocked as well. Just use a service and don’t spam and all should be well (so don’t get sending newsletter emails all the time)
As others have said, you can use dynamic DNS, but you also might have an IPv6 address that doesn’t change. Or maybe it does, you’ll have to check with your ISP. But that one can be set up as an AAAA record in your DNS.
Most ISPs support IPv6, but some don’t, so you might not be accessible to everyone without also having an A record.
I recommend afraid.org, you get everything that you need for free dynamic dns, and they’re a cool project so someday you may like to do even more with them or send them a little donation.
I started with noip first, and the monthly re-up was so annoying.
Seconded. Used their service for many years.
They are excellent
Whether your ip changes frequently depends on your ISP, but it’s not necessary to have a static ip. My public IP changes about once a year, but I use my router to update my dns and make ally external services rely on DNS and not IP to connect.
You can also do this, look up “dynamic DNS”. You just need to register a DNS name (can be free) and set up the updates to make it accurate.
I selfhost my blog without a static IP. You just need Dynamic DNS.
Keep in mind that your outbound bandwidth might be different from your inbound. I get 300mbps in, but only 5mbps out. It’s not noticeable during normal Internet use, but as you start sharing content publicly, limited bandwidth becomes really noticeable.
Don’t even need dynamic DNS. Just use ddclient to update your DNS record if your IP changes.
That’s called dynamic DNS (it’s the dd in ddclient).
Yes, but there used to be specific dynamic DNS providers or ones that advertised as that but you don’t specify need those now.
It makes things easier, but you have options, such as:
- dynamic dns.
- Public reverse proxy or tunnel.
- Onion routing.
As others have already commented, what you need is a Dynamic DNS service, where you register a subdomain, and setup a small program or script on your computer that pings the DDNS server every few minutes, that way you leave that running on the background, and if the program detects that the IP with the request changes, it will update the subdomain to point to it automatically.
You could access the blog from the subdomain of the DDNS directly or if you get your own domain, you can point it to the DDNS.
If you want a recommendation, I have been using DuckDNS for years, and it has been pretty reliable.
There’s also FreeDNS. Their only ask is that you log into the account once every 6 months so they know you’re still using it.
You can rent a virtual private server (VPS). I used to have a number of these for under $10 / month. I imagine they might cost more now., but chances are you can still find something super affordable.
Wordpress.org will let you have a free site but you don’t get a custom domain. Wordpress.com has a personal plan for $4 / month. Matt Mullenweg (CEO) has revealed himself to be a crazy piece of shit, so maybe look elsewhere. I’m just trying to give you a sense of how accessible this stuff can be.
Running a VPS will require more learning, but it can be super gratifying if you enjoy nerdy computer stuff and solving puzzles just for self-satisfaction. I used to use Rackspace, Linode, and something else that I can’t recall at the moment. All were pretty reasonable. Rackspace had a ton of good setup guides for newbies that were well written. I’d occasionally land on those doing a web search for other hosting stuff and found them reliable.
Edit: DigitalOcean was the one I couldn’t remember.
https://www.hetzner.com/european-cloud Netzner can be a good alternative
I could make this quick: Is your internet access behind a CG-NAT? If yes: you’re gonna need a static IP.
Not necessarily, Cloudflare tunnels, headscale/tailscale will sort that issue out amongst several other ways
I was going to use Cloudflare to sort this, but I’m uncomfortable how big they are getting / lack of competition in that part of the market. So we looked at Pangolin as an alternative, but it’s a faff to self host.
Hence why we’re back at exposing it straight out the back of Nginx Proxy Manager.
I get that… fo me though as I have been using Cloudflare for many years I can’t see any reason to change yet. That of course may change
But how will a tailnet help for a blog? At some point, the https port needs to be open.
tailscale will tunnel through and you can set it to pass through https. Lots of different ways to achieve this, as long as you have control over the dns and are able to set https up it will work. This is why for me I still use cloudflare, you can even setup a subdomain through their tunnels and they act as a cdn. For example, I run a linkstack instance, send instance and much more
Tailscale funnel is made for this.
My router says it has NAT enabled (in the WAN settings section - for the internet connection)
It’s not about your router. But rather if your ISP connects several households with the same IP.
Quick, but sadly incorrect
Care to explain what I got wrong?
Static IP is helpfull but not necessary. Even with NAT and a changeing IP there’s options, such as:
- dynamic dns.
- Public reverse proxy or tunnel.
- Onion routing.
- How do you open the https port behind a nas?
- That public tunnel needs at least a public IP address again.
- Ok, forgot that one. But then you’re only accessible through Tor, isn’t it?
- Port forwarding
- Yes, and there’s services that do that for you
You can’t port-forward if you sit behind a nat.
Port forwarding was invented for exactly that
You don’t need one, but it does make things easier.
What you can use is something like Dynamic DNS to update your DNS record if your IP ever changes.
Thank you for your replies everyone!
I’m looking into DDNS. Before I go with a provider, I notice that my router has this functionality built in. Should I use that?
(It’s an Asus RT-AX86U Pro - so fairly chunky in terms of spec)
For reference, the set up is:
Docker containers for
- Ghost
- Nginx Proxy Manager
(It’s an Asus RT-AX86U Pro - so fairly chunky in terms of spec)
I have your exact router make and model! I self host my own server with a domain on my home network and make use of the built in DDNS feature.
My domain registrar is Cloudflare so I have to use a custom script for DDNS, if you’re in the same boat I can provide the script.
I would suggest looking into Asus WRT Merlin Firmware, the custom firmware enables more functionality to your router.
Docker containers for
- Ghost
- Nginx Proxy Manager
When hosting a reverse proxy like Nginx, Traefik, SWAG, Pangolin, etc keep in mind you 80:80 and 443:443 ports need to be exposed to the host machine then you will forward those ports on your router. This will allow your reverse proxy to communicate with Lets Encrypt generating and verifying your SSL certificates.
Regarding Lets Encrypt your server doesn’t need to be accessible from the internet if you use the DNS-01 challenge. Caddy with the caddy-dns plugin for your provider can do that automatically for you.
That would be a good place to start. Which providers does it support?
Seconding this, it is very convenient if your router supports a good provider. But it is better imo to use a good provider with a helper script on your server than to stick with your router defaults if they’re not that good.
Hope this helps:
Running a service like ddclient may give you more options at the cost of being more complicated.
I would stand up a VPS in a cloud provider
Personally I would look at using a tunnel, something like Cloudflare tunnels (easy to setup, sorts dns out) but many here dislike Cloudflare for a lot of reasons. However the free plan allows you to get started, easily, and then once you are started and serving your blog you can look into other solutions, or failing that stay on Cloudflare. Other tunnels exist but if you have a domain, using cloudflare is the easiest imho to get started
Surprised nobody has mentioned cloudflare ddns. If you registered your domain with cloudflare, you can use the api or qdm12’s (author of gluetun) ddns-updater to keep your A/AAAA records up to date.
Cloudflare Tunnel is a good fit to your use case. You only need a domain name to expose your web server via Cloudflare.
https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/
there is Onionshare…
