After discussion with Network IT staff from my institute, we understood that it was a limitation from the reverse-proxy that triggered the error, not the ningx container!
After discussion with Network IT staff from my institute, we understood that it was a limitation from the reverse-proxy that triggered the error, not the ningx container!