You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have made the decision to migrate our entire Atlassian suite of products to CentOS as that seems to be the native / most supported installation environment. I'm not new to linux/unix administration but I am having a heck of a time migrating our installation over.
I have created file system backups of the installation and home directories and transferred them to the same locations, as well as a database dump and restore.
When I start the Crowd server, I get the tomcat response that it is running, but 8095 is inaccessible. This is a vanilla CentOS install explicitly for the purpose of running the atlassian suite of jira, bitbucket, bamboo, and crowd.
I have also tried proxypass/proxypassreverse with apache (which is how I have the current installation working, and it has been for years, but it's also not working. I am on a bit of a time crunch to get this working and still have many other services to migrate. I started with crowd as it seemed to be the easiest but am now worried about the process with the remaining products.
your "problem" is probably firewalld. I can recomend you to use Nginx as reverse proxy. Here you can follow tutorial for installation of Nginx for CentOS.
Next you can look (as example is it Jira, but other apps will be similar) at this.
Let me know if it helps.
I thought firewall might be the problem earlier despite having added the port to it and public zoning. I had already disabled the firewall using systemctl firewalld disable and systemctl firewalld stop
In any case, I got rid of apache went with nginx as per your post. I now get a 502; and in addition to that even using localhost, I can't seem to make it stop going to the setup page onload. If I manually go to /crowd, I can log in, and everything is fine.
I've tried re-doing the process with fresh installs starting at the os level several times now, and simply can't seem to get the damned install to launch, proxy, and stop showing me the setup page. For a moment, I got everything working on the windows install, but it kept looping back to the login page, which I was able to break with a manual /crowd url change, but come on.
I'm at a complete loss and have wasted countless hours at this point trying to get this set up on both a centos as well as windows environment. This install process is absurd. I was able to get it working on FreeBSD which is an unsupported platform in the past in under 30 minutes.