This sounds really simple, and I thought it would be, but I'm wondering if I'm missing some simple configuration.
We have Jira installed on a Cent OS virtual machine, configured in a DMZ. I need to move it to a different subnet which I did by changing the IP/Mask/DNS in the OS, and then making the appropriate network changes on our side. However, when I start the VM up, all I get is a 503 service unavailable error. I can ping it fine, WinSCP it fine, but the web interface never comes up. Is there some sort of binding or other config I need to change as far as adjusting the IP? It worked fine when I reverted it to it's original IP.
@GrizzlyOne95 Are you running any proxy Server (like nginx or Apache) in front of JIRA Sever. If yes, you will need to change the Proxy settings in Virtual Host Configuration file for JIRA Server, to change IP address (if used) in Proxy directives.
I did not set up the Jira server so I am not sure, but that is certainly possible. Would those settings be the ones set up in server.xml under the "conf" folder? I will look into this more, thanks for the suggestion.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@GrizzlyOne95 Yes, the settings in server.xml file as well as settings in Virtual Host Configuration file that contains the proxy settings for JIRA application (Virtual Host) served by the proxy server.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok thank you. I checked both those files and it is using a DNS name, not an IP. So why would changing the IP for the machine break the web interface, if I updated our DNS entries? I'm sorry if I'm not understanding something simple, if you have a guide or something for this that'd be helpful. I haven't been able to find a solution for this seemingly simple task.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, I feel really dumb. I didn't update the hosts file in CentOS, even though I had updated the info everywhere else. The hosts file still had the old IP pointing to the hostname. So, thanks for your help and sorry for wasting your time :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.