Connecting OK from Linux localhost, not Windows

[Steve Fogel]

Hi, all...I've got the Jira software running on an Amazon EC2 instance of Ubuntu. Using Firefox on the Ubuntu instance, I can connect to the Jira software (http://localhost:8081) just fine and run the software. However, I can't connect from a browser on my Windows laptop. I've done just about everything I can think of with the firewall on both server and client.

Could there be something else I need to configure? (For example, in the Jira admin settings, Base URL is set to http://localhost:8081, but from my Windows browser, I have to go to http://<hostname>:8081.)

By the way, port 8080 was taken, so I had to use 8081. Thanks!

[Nic Brough -Adaptavist-]

Localhost means "this machine"  (it does not necessarily have to, it is a convention rather than an absolute, but the last OS I remember coping correctly with localhost not being itself was OpenVMS)

When you put "localhost" into your laptop/desktop/phone/server/tablet/whatever, what you are saying is "talk to yourself", not "go ask another machine for a connection".

To connect to your Amazon EC2 machine, use the resolvable name of that machine, or even just its IP address.  Once you have a connection, log in and change the base url to match.

[Steve Fogel]

Hi. If I don't change the base URL, will it refuse a connection from that machine? Also, should I use "exact" for the type of base URL? Thx!

[Steve Fogel]

The connection is failing when from a browser on my Windows machine, I go to http://<dns-name-of-EC2-instance>:8081. I'm able to see the default Apache2 web server page when I just go to http://<dns-name-of-EC2-instance>, so communication to port 80 is working. Thx

[Nic Brough -Adaptavist-]

The base url is not critical - it will work with the wrong base url, but some links may wander off to the wrong place, some gadgets won't work, emails will contain duff links and so-on.  You'll be ok to log in and correct it later.

http://<dns-name-of-EC2-instance>:8081 looks right to me, as you know it's running on 8081 from the local localhost experiment.  So I would guess that there's a firewall or something blocking that port on the Amazon side.