My system right now gives a routing error trying to connect to port 3000, but connects to port 22 fine. I'm sure this is normal now, but it isn't something I'm used to. Routing errors are usually not given related to ports or processes connected via. $ curl -v [gently-censored-ip]:3000 * Trying 108.26.195.204:3000... * connect to 108.26.195.204 port 3000 failed: No route to host * Failed to connect to 108.26.195.204 port 3000: No route to host * Closing connection 0 curl: (7) Failed to connect to 108.26.195.204 port 3000: No route to host $ ssh user@[gently-censored-ip] Welcome to Ubuntu 20.04.4 LTS (GNU/Linux 5.4.0-109-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support: https://ubuntu.com/advantage System information as of Fri 29 Apr 2022 05:59:42 AM EDT ...