JIRA is unable to resolve the URL but is working on localhost

Question

Hi,

I am migrating my JIRA application from one server to another. I have followed the process of migration and the JIRA is now running on new server - when i run through localhost, however when i use the proxy-name, the application does not open and gives me unable to connect error.

I think the URL is not getting resolved.

Require your kind help on this.

Regards

Sanket

rrudnicki · Answer

Hi Sanket,

You've mentioned when you put a proxy name this doesn't work. Can you check if both proxy and JIRA server can answer for the same hostname. I mean, on JIRA you configured the hostname like "jira.yourcompany.local" and the same thing on your proxy?

Lastly, can you confirm that your JIRA Base URL is pointing to the correct hostname instead of localhost? This option appears on the System --> General Configuration --> Base URL

Regards,

Renato Rudnicki

Jaime S · Answer

Hi, Sanket.

As Nic said, you have to isolate the problem.

Apart from his suggestion, I also suggest that you try to ping the Server from the Client (using IP preferably):

ping <ip address>

If that works, see if access using the name or IP works. If the IP works, then you probably have a DNS problem. You can check that using nslookup:

nslookup my.jira.com

If your able to ping the server and access it using the IP, but not it's domain name, you have to check DNS configuration. If you can't access using IP, check network access, port access, proxy and firewall configuration.

I hope it was helpful.

Kind regards,

Jaime Kirch da Silveira

Atlassian Cloud Support

Nic Brough -Adaptavist- · Answer

Sounds like your network is not set up correctly.

To start to isolate where, lets assume you're successfully running JIRA on http://localhost/jira

Now try http://your.ip.address/jira  (e.g. http://192.168.1.42/jira), from the server, and then try it from a remote machine. That will tell you if it's reachable or not.  If those fail, it's probably a firewall, if they work, then it's probably your network's DNS setup.