I can work around that, ( I don’t need to water my lawn from the office) but you should expect this to be a problem. I would be proactive and put that in a FAQ, and note that your app doesn’t work on many corporate networks.
I’m trying to make sure I have a robust firewall rule and have done a wireshark capture on the connection. I’m seeing that the only IP that tcp 444 connects to is 52.89.82.249. Doing an IP lookup it looks like you’re hosting the service on AWS.
I created a firewall rule that allowed tcp 444 out and everything worked but I’m not wanting to simply open 444 to the internet (and would assume that corporate environments wouldn’t either) so is this the only IP that communication over tcp 444 will happen on or will this change over time, e.g. is it possible that in the future the service would be hosted directly by you or another cloud provider?
Great. I figured SNPP was pretty embedded and 444 was going to stay for a while. Getting everything on 443 is a great option and I appreciate the work toward that goal