Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira isn't accessible, but other services are

Patrice Vignola
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 14, 2016

Hi. I just installed JIRA on port 8080, and I can access it locally just well (192.168.100.xxx:8080). But as soon as I try to access it with my real ip, it's impossible.

I know what port forwarding is and I tried everything I could think of. If I try to run another application (like Jenkins) on port 8080 instead, it works just fine everywhere, but only JIRA doesn't seem to be working. I can't figure out why.

1 answer

0 votes
Nic Brough -Adaptavist-
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.
July 14, 2016

If other applications work and JIRA does not, that's very odd.  It implies routing and so-on is working, but that JIRA won't listen externally.  Off-the-shelf, JIRA simply doesn't do that, it just listens.  You'd actually have to fiddle with the Tomcat settings in order to deliberately block off the access, and I doubt you've done that.

Could you tell us the exact symptoms of "doesn't seem to be working"?

Compare what happens when you are running JIRA on port 8080 and you use a browser to go to

http://localhost:8080  (with a browser on the machine running JIRA)

http://actual-ip-address:8080 (with a browser on the machine running JIRA)

http://actual-ip-address:8080 (with a browser on another machine in the network)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events