Jira isn't accessible, but other services are

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

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
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

214 views 6 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you