No go there unfortunately. Same error when the new UI is in place. Protocols are all set to https. I wonder if the problem stems from using the AWS load balancer to do the SSL certs. - this means all comms from load balancer to client are 443 with cert, and all internal is port 80. we don’t have the option for lets encrypt, however i do have the required certificate/key in pem format, so could use that if there is a way to make it work and then just use 443 all the way through the loadbalancer and the ineternal server setup.
Have you had anyone else setup this way with a loadbalancer in front of the product?