Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
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

Cannot access crowd console from another host browser on LAN

I'm not able to access the crowd console via http://<IP Address>:8095/crowd

I can only access it via localhost

I've tried adding entries in Applications > Crowd > Remote Addresses

but nothing works.

 

1 answer

1 accepted

0 votes
Answer accepted
Bruno Vincent
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 16, 2018 • edited

Hi @N B

If you can't even see Crowd's console login form, then that's probably a network issue. Make sure that port 8095 is open for inbound HTTP connections on your Crowd server.

If you do see Crowd's console login form, but cannot login, then that's probably a configuration issue in Crowd itself. In that case (I assume that you're running Crowd v3.x), in the console go to Settings > General options and change the Base URL. I strongly suggest that you use a resolvable FQDN (e.g. myserver.mydomain) instead of an IP address. Still in Settings > Single Sign-On cookie settings, make sure that SSO domain is either blank or equals your actual domain (e.g. .mydomain). Once you've changed those settings, you might need to restart your browser or clear your cookies to login again.

Hope this helps.

Thanks for the quick response. It turned out to be a Windows Firewall issue where I had to add port 8095. After that it worked. Out of practice with Windows as I've been using only Linux for years. 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events