ID 511084 - [B] Panels don't load anywhere in the Client when using port 443 (TLS enabled) or port 80 (no TLS)

Problem summary
Starting the Flix Server with TLS enabled, and having the Client connect via port 443 causes download issues on the Client.
The same issue occurs when using regular HTTP and connecting via port 80. Using HTTP on port 443 or HTTPS (TLS) on port 80 works correctly.

Customer reported version
Flix 6.4.0

Steps to reproduce

1) Set up a Flix 6.4 server with TLS

2) Set the http_port to 443 (this is the default https port)

3) Login to Flix

4) Try and open a sequence revision with some panels (which are not cached by the client)

OR

1) Set the http_port to 80 in the config.yml

2) Login to Flix

3) Try and open a sequence revision with some panels (which are not cached by the client)

Expected behaviour
All panels should show in Flix.

Actual behaviour
None of the panels show in the Flix client. The server shows warnings like this:

WARN[0049]auth.HeaderSignedAuthenticator.validateSignedRequest: signatures do not match                      

WARN[0049]auth.HeaderSignedAuthenticator.signedAuth: signature invalid                             Key="AccessKey{User{admin Admin user} #CmcT5zxXgfNjq5oadL2t Expires 2022-06-09 01:45:36 +0000 UTC}"

WARN[0049]auth.HeaderSignedAuthenticator.Authenticate: Auth failed                                  

WARN[0049]base.authenticator.signedAuthHandler.func1: could not authenticate request                Warning="invalid authentication header"

DEBU[0049]base.responder.JSONErrorResponse: sending HTTP error response                   error="jsonError{0: 401 - Authentication failed}"

The Flix server works properly on port 443 without TLS and with TLS on different ports.

The Flix server works properly on any port but 80 without TLS.

Workaround
Use any port other than 443 when TLS is enabled, and any port other than 80 when TLS is disabled.

Reproduced by support

This bug has been reproduced in:
Flix 6.4.0

Unable to reproduce bug in:
Flix 6.3.7

Earliest version tested
Flix 6.3.7 - This issue doesn't appear in this version and has regressed