Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,417
Community Members
 
Community Events
177
Community Groups

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

http://10.243.2.193:8097

and

http://10.243.3.11:8097

and

http://corp-jiraweb:8097

all work

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.

http://10.243.3.33

and

http://crowd2.onlifehealth.com

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

respectively.

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.

1 answer

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events