Hi, We have a second instance of crowd setup that we are doing some testing with. Its setup on the same web server as the previous crowd but listening at a different port (8097 instead of 8095).
If I go to the straight ip addresses it works and does not redirect to https
however when we setup using a pretty name like crowd2.onlifehealth.com in DNS (10.243.3.33) and use F5 load balancer pool to redirect to crowd2.onlifehealth.com to http://10.243.2.193:8097 it does not work properly.
don’t work and seem to redirect to https://10.243.3.33/crowd/console/login.action or https://crowd2.onlifehealth.com/crowd/console/login.action
Of course the https does not work.
Any ideas on what is happening here? Our network guys swear up and down that there is no redirect happening in the F5 and a fiddler trace verifies this.
We did create this second crowd instance from our working crowd instance (backup and restore from xml) however all of the crowd.properties, build.properties, etc all reflect http for urls in this instance.
Have you setup the trusted proxy server settings?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Do you own more than one Server or Data Center product? Do you have challenges provisioning users across your Atlassian products? Are you spending a lot of time integrating each Atlassian product wit...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs