I'm evaluating Jira. After installing I tried to access Jira from a web browser and it's not responding.
It responds to http://localhost:8080 and loads normally.
However, when I try to access it from a browser on another machine, http://<ip>:8080, I get no response.
I've also tried http://<machinename>:8080 and I get nothing.
If anyone has a suggestion it would be greatly appreciated.
If you are trying to access JIRA from an external (global) IP address, instead of your local host, you might not have port forwarding setup on your router to access it outside of your local area.
To access it locally from any computer on your network
192.168.0.XXX:PORT where XXX is the local IP to that machine (eg http://192.168.0.101:8080) - This would be the first thing to check out to make sure you can access it from other computers on your network. To find the local ip of the machine you need to do an ipconfig (eg windows start -> run -> ipconfig -- look @ IP Address there). If you can't access it locally from another machine on the network, you might want to check the firewall settings on the computer you are running JIRA on to make sure it's allowed.
To access it globally, you'll need your real external IP (whatsmyip.net can give this to you - eg http://188.8.131.52:8080 --- random IP address i just typed FYI) If you can't access it that way, then you need to setup port forwarding on your router. You need to forward all port request (in this case 8080 for JIRA) to your local IP address. Linksys routers have a "Forwarding" area that's pretty explanitory. You enter the local IP address you want it to go to, the port number ranger (in this case both would be 8080), UDP/TCP/Both (use 'Both' if you aren't sure)
Each router is different. But it sounds like your porblem is port forwarding.
That's a networking question really - something on the server, or in your network is stopping access.
Start by checking the firewall settings on the Jira server and all machines between it (proxies and routers). A lot of installations block most ports by default and need adjusting to allow services to be accessed.
No, it should have connected on port 8080, not 23 (23 is default for telnet)
If your Jira is running and not firewalled by your network, it should respond to telnet on 8080 (it'll look rubbish, but that's fine, we're just interested in a response that returns data, or the error message explaining why not)
I looked at the firewall and don't now what any of this means does any of this look out of place.
[root@localhost ~]# iptables --list-rules
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -j INPUT_direct
-A INPUT -j INPUT_ZONES_SOURCE
-A INPUT -j INPUT_ZONES
-A INPUT -p icmp -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -i lo -j ACCEPT
-A FORWARD -j FORWARD_direct
-A FORWARD -j FORWARD_IN_ZONES_SOURCE
-A FORWARD -j FORWARD_IN_ZONES
-A FORWARD -j FORWARD_OUT_ZONES_SOURCE
-A FORWARD -j FORWARD_OUT_ZONES
-A FORWARD -p icmp -j ACCEPT
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
-A OUTPUT -j OUTPUT_direct
-A FORWARD_IN_ZONES -i enp7s0 -g FWDI_public
-A FORWARD_IN_ZONES -g FWDI_public
-A FORWARD_OUT_ZONES -o enp7s0 -g FWDO_public
-A FORWARD_OUT_ZONES -g FWDO_public
-A FWDI_public -j FWDI_public_log
-A FWDI_public -j FWDI_public_deny
-A FWDI_public -j FWDI_public_allow
-A FWDO_public -j FWDO_public_log
-A FWDO_public -j FWDO_public_deny
-A FWDO_public -j FWDO_public_allow
-A INPUT_ZONES -i enp7s0 -g IN_public
-A INPUT_ZONES -g IN_public
-A IN_public -j IN_public_log
-A IN_public -j IN_public_deny
-A IN_public -j IN_public_allow
-A IN_public_allow -p tcp -m tcp --dport 22 -m conntrack --ctstate NEW -j ACCEPT
No, the problem is your network, not Jira. The fact that you can get to it on localhost:8080 tells you that Jira is running, accepting incoming connections and responding to them correctly. I suspect your "open source product" is running on another port, one that your network is not blocking automatically.
So you need to fix your network.
It's officially Tuesday, which means it's officially time for another tip to help you better navigate this space we call the Atlassian Community. 😄 I got a great question from community member, Sa...
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!
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