Here are the steps we have taken from upgrading to 3.17.0
3.16.0 Upgraded from 3.13.0 we took each gen leap 13-14-15 Upgraded to 3.17.0 Users try to log in by putting the workspace URL as the domain. Nothing seems to load but we get requests via a log service with the correct user agent.
Since upgrading to 3.17.0 once the user has typed the workspace URL it is like they cannot see the prompts to log in, we can see the rocket chat logo like open.rocket.chat.
Server Setup Information:
Version of Rocket.Chat Server: 3.17.0 Operating System: Ubuntu Deployment Method: Docker Number of Running Instances: 1 DB Replicaset Oplog: NodeJS Version: v12.22.1 MongoDB Version: 4.0.23 Proxy: NGINX Firewall: ModSec
We can see the the request come through to our logging system and all connections make through the proxy but it is just like they are not being offered the login buttons.