There are two new features in the latest Nomad Server versions, introduced to Nomad Server without big notice.
I just got the question from a partner why Nomad Server now binds port 9080 in addition to port 9443 and the internal communication port (only loop back).
The port might be used by other applications like the IBM Spectrum Protect (TDP) -- which was the problem in this customer case.
It turns out the TDP Java based restore GUI and does not work in combination without changing or disabling the port.
This is a companion discussion topic for the original entry at https://blog.nashcom.de/nashcomblog.nsf/dx/new-nomad-server-features-acme-http-01-challenge-support-http-redirects-via-port-9080.htm