I just tried the discourse.diy system on my own hardware and it didn’t work. Did I do something wrong?
What hardware? Your desktop PC under a residential ISP? A VPS in a data center? AWS EC2?
It’s an enterprise-grade server (PowerEdge R630) being colocated in my friend’s rack at his home at the moment. There is no firewall rule that I know of in the router that would block it but I have access so I can check stuff there if required
Looks like his ISP, like most, block connection to ports 443 and 80, which are required by Discourse.
You can follow Install Discourse on a residential internet with Cloudflare Tunnel for a workaround.
I had a whole reply typed up about how the IP wasn’t the issue and I had the realization that 80/443 on that IP are actually taken by a nginx container in a separate Proxmox cluster which is currently offline due to a botched firmware update (no quorate). This is why I’m a sysadmin and not a netadmin 
Presumably there is nothing I can do about this unless I change the IP it runs off? There are multiple IPs available (5) but the vlan that this specific server is on always runs off the 213 IP
