@thechildofroth @rds its claiming its a private ip?
that makes it sound like its one of 192.168... or 10... or 172.16...
@thechildofroth @rds its claiming its a private ip?
that makes it sound like its one of 192.168... or 10... or 172.16...
@thechildofroth @rds does the ip actually fall into one of those ranges in the wikipedia article?
@xandris @rds Ahh, yes. It's in the range described as:
Shared address space for communications between a service provider and its subscribers when using a carrier-grade NAT
Hmm, is there a way around that (I knew didn't have a fixed IP but I was going to use my domain providers DNS API to dynamically update the IP as required.
@thechildofroth @rds i haven't looked into dynamic dns solutions (aka dyndns) in a while. you may be able to buy a static ip for a little extra fee from your isp. last time i checked your router might be able to interface with your registrar's dyndns feature. asuswrt has such a feature. server side i found:
- ddclient (perl daemon)
- ez-ipupdate
- inadyn
- updatedd
or roll your own with just curl if your registrar gives you a url:
https://gist.github.com/gbraad/e167a509a902263ed67264f346937aae
@thechildofroth @rds oh wait hold up
you have cg-nat which means you don't have a unique external address at all from what i understand. if you go to ip.me or similar, the address it shows you is shared with other customers. the gateway would have no way to know which customer an incoming connection should go to
all that to say...more research needed on how to receive connections when behind cg-nat. i think cloudflare offers something for this for free...
@thechildofroth @xandris @rds @beasts
If you're having trouble getting regular certbot certificates (because that requires certbot service to talk to the computer trying to get the certificates), you can try using the certbot DNS verification for certificates (because that only needs you to prove that you control the domain name, and doesn't really talk to your servers)
https://eff-certbot.readthedocs.io/en/stable/using.html#dns-plugins
@double_a_runi @xandris @rds @beasts I used a very helpful guide from here: https://www.digitalocean.com/community/tutorials/how-to-acquire-a-let-s-encrypt-certificate-using-dns-validation-with-acme-dns-certbot-on-ubuntu-18-04 and it appears to have worked (for the certificates at least) so now on to learning a bit more #Nginx to get my #Jellyfin server line.
Many thanks again for the very helpful nudge in the right direction!
@double_a_runi @xandris @rds @beasts I've continued to chase this around today and it does appear that there's no simple way around the CGNAT address issued by my ISP. I've reached out to them to find out what options they have to circumvent it.
@thechildofroth @double_a_runi @xandris @rds @beasts Worth checking if your ISP uses CGNAT for both IPv4 and IPv6 addresses. If you have a real IPv6 address, that might be the way to go.
@mdonkin @double_a_runi @xandris @rds @beasts There's no IPV6 address in the router control panel, although there is this article (from 2023) saying the ISP are ready and rolling it out to customers: https://www.ispreview.co.uk/index.php/2023/08/uk-broadband-isp-octaplus-confirms-ipv6-readiness.html
I wonder if there's something that I can do from my end to get upgraded?