I have a tech illiterate mother in law who I switched to Zorin OS (an Ubuntu fork).

I installed a wireguard VPN client on her laptop and did drills over the course of 3 days to make sure that she understood how to connect. Anytime she needs help, I can tunnel through my wireguard server and log on with my own account - Heck, as long as she doesn’t change her password, I can log on as her as well.

That has made remote troubleshooting significantly easier as she is located about a a 23-hour drive away.

Okay, then I’m thinking your router/NAT maybe causing the problem. Typically, your ISP won’t block subdomains for dns, they may outright block Source NAT (SNAT), but if you could get through via the IP, you should be good to go.

An easy way to check is to visit a site like this and check for port 443: https://www.yougetsignal.com/tools/open-ports/. You don’t need to be on the server that’s hosting your portfolio, just any thing that’s on the same network as your portfolio (something behind your external router)

Just to make sure.

1. When on your home network, doing nslookup (or similar), your fqdn resolves to your public IP
2. When on a hotspot, if you go to https://fqdn/ it does not connect (probably with the ERR_CONNECTION_TIMED_OUT that you mentioned below)
3. When on hotspot, if you to telnet to port 443 on 206.x.x.x, it connects

What happens if you, on the hotspot, try browsing to https://206.x.x.x? When you are on the same network as the portfolio, can you reach https://[internal ip]?

What I’m leaning towards is a router/firewall that may be causing some issues. To help with troubleshooting, does your website server have any local firewalls (for ubuntu that would typically be ufw, but it could be iptables or firewalld)?

Try this command from a terminal on the system from which you’re attempting to connect:

nslookup <yourfqdn>

It should come back with something like this:

~ ❯ nslookup stronk.bond
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   stronk.bond
Address: 172.67.174.80

If it says something like “can’t find” that means that your dns isn’t configured appropriately. Does your IP address start with 192.168, 10., or 172.? That would be a private IP address (something which isn’t accessible from the internet.

Oh! And where is everything - is your workstation/laptop on the same network as your portfolio? Is the portfolio on a different network? That could effect things as well.

What does your nginx config look like for ssl? It should specify a certificate and key file - that certificate subject needs to match your fully qualified domain name (fqdn). Certificate can have subject alternative names (SAN) for other names and even IP addresses.

For instance, you could have a single certificate for foo.bar with a SAN for just foo and an IP SAN for 192.168.1.30.

Certificates also need to be signed by a certificate authority (CA), and in order for your browser to visit https://foo.bar/ without a warning your browser must trust that CA.

If you did a self signed cert, this is most likely the problem you’re running into.

It’s important to know that your communication is still encrypted because of SSL, but since your browser doesn’t trust the CA (or the subject doesn’t match the FQDN) the browser will say it’s not secure.

I’m confused - what was here before the domain expired? The only thing I’m finding for AZA is the association of Zoos and Aquariums.

Sometimes when I sneeze, my arm hurts.

I’m fairly certain it’s not a heart attack.

Heck, African American! That’s all you had to say!

Hooooboy. Their comment gets worse the further you read.

IIRC, he was the designated driver too.

They’re also no picnic for people who want kids but can’t have them despite years of trying.

I’m not sure if buildings have feelings, but I bet that would feel so good to remove that foliage.

Oh there’s definitely some elder gods involved with programming when I do it.