evilstevie @evilstevie@mastod1.ddns.net

@hypnogoria fingers crossed

@eclectech that is an awesome marble :)

@anon_opin * apart from the bulls. I don't think they volunteer.

@35millimetre @levitte from inside your network it's going to need either a host entry on your router (if it lets you) pointing the URL to your inside server address. if the router lets you...
if not that, you're going to have to put a host entry on each device using the server for it to work, or use the local IP address internally instead I guess :)

and with that I'm done, good luck and shout up if you need any help bodging it further.

@35millimetre @levitte be warned that this makes your certificate Bad and Wrong to anyone using the Awesome URL, as the name it's tied to is the duckdns one.
Plan ahead for this before you start - leave the letsencrypt stage until now, and set it up for the Awesome URL instead - means testing via the IP or duckdns name will get certificate errors, but using the AwesomeURL will work fine.

@35millimetre @levitte at that point, you're basically good to go, although with potentially a not-so-great URL (duckdns have been better than dyndns for me - they just let you have a domain name and leave you to it. others tend to want to keep prompting you for "still active?" and "want to go premium?" every month or three).
if you have an Awesome URL and control it via some form of DNS control panel you can point your Awesome URL towards your duckdns name using a CNAME entry

@35millimetre @levitte to use https correctly as a server, you need to get a server certificate.
two options: money and pain, or just pain.
for just pain, visit
letsencrypt.org
while holding your server's nice shiny duckdns name you made earlier.
follow the instructions to create yourself a certificate and prove you own that name, and you're good for the next 90 days of being a server, yay.
to keep it going beyond that, add in certbot
certbot.eff.org/instructions
and let that take the strain.

@35millimetre @levitte this "publishes" your current IP address (which is not static, though with Virgin tends to change on each router reboot) every 5 mins / hour / day / whatever you choose - it does this to keep the name you chose pointing to the right place - your Virgin router. your router then sees the traffic pointing at that name as inbound traffic to the web ports which it forwards on to your server.
so far, so good. works for http nicely.
https needs another thing, because why not...