crowd redirecting to https

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




all work

however when we setup using a pretty name like in DNS ( and use F5 load balancer pool to redirect to to it does not work properly.


don’t work and seem to redirect to or


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,, etc all reflect http for urls in this instance.

1 answer

Suggest an answer

Log in or Join to answer
Community showcase
Emilee Spencer
Published yesterday in Marketplace Apps

Marketplace Spotlight: DeepAffects

Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...

40 views 0 3
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot