Ships consistently experience HTTP connection failures after moving servers

[dr-frmr]

Describe the bug

Started a new server -- no firewall, all ports open. Moved ships to it. No problem accessing them from browser, but on 3 ships, now receiving endless stream of HTTP connection failures. This is causing their eth-watcher to fail and making them unable to produce push notifications for various apps. Sample dojo output:

http: fail (446, 504): connection failure
http: fail (447, 504): connection failure
http: fail (448, 504): connection failure
eth-watcher failed; will retry
%retry-too-many
http: fail (449, 504): connection failure
http: fail (450, 504): connection failure
http: fail (451, 504): connection failure
http: fail (452, 504): connection failure
http: fail (453, 504): connection failure
http: fail (454, 504): connection failure
http: fail (455, 504): connection failure
http: fail (456, 504): connection failure
http: fail (457, 504): connection failure
http: fail (458, 504): connection failure

To Reproduce Steps to reproduce the behaviour:

1. Boot ship on one server
2. Zip up and move to another
3. Turn it on
4. ?

Expected behaviour Ships should at least be able to recover or provide more information on how to resolve this if possible -- it's been several days

Screenshots If applicable, add screenshots to help explain your problem.

System (please supply the following information, if relevant):

• OS: Ubuntu 23.04
• Vere 2.7

  %base
  /sys/kelvin:           [%zuse 413]
  base hash ends in:     9kn52
  %cz hash ends in:      9kn52
  app status:            running
  pending updates:       ~

[dr-frmr]

eth-watcher failed; will retry
%retry-too-many
http: fail (1044, 504): connection failure
http: fail (1045, 504): connection failure
http: fail (1046, 504): connection failure
http: fail (1047, 504): connection failure
http: fail (1048, 504): connection failure
http: fail (1049, 504): connection failure
http: fail (1050, 504): connection failure

still occuring, and beginning to concern me given that this is on a software-distributing ship and newly-keyed ships will not appear in its azimuth state...