It's not like you can learn from it (even if the topic is something you'll never use like a 2 hour dissertation on heat pumps or a multi-video series on how an old pinball machine uses only relays to calculate scores).
Why yes, I am subscribed to Technology Connections, how could you tell?
The first paragraph says that she pulled a huge Karen, getting out her phone to look up the law and even called the governor's office so that they would give her the shot.
And it's surprise to absolutely fucking no one, she is still a huge pro-lifer.
I would get multiple drives and do RAID. Here's a helpful calculator to figure out drive quantity, size, and configuration. The reason to do RAID is redundancy. Hard drives will fail (even NAS branded drives). You do not want your photos, media, etc to be lost in that case. I personally do not go with anything below RAID5 (and for super sensitive things, I'll even go RAID6 - despite the hit on overall capacity. If the optiplex has drive capacity for multiple drives, I strongly recommend you go this route.
Hey, while we're spending time rehashing presidencies - how about we have a full blown Senate investigation into Ronnie's cognitive decline? Surely we can find some evidence there.
I thought final destination had death chase folks who had a vision of an impending accident and they used that foreknowledge to avoid their fate? To be fair, I haven't seen any other than the first one, and that was through my fingers. (I am not a brave man)
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)
When on your home network, doing nslookup (or similar), your fqdn resolves to your public IP
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)
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)?
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.
Is there something on your wishlist that's on discount?