Can't connect to new installation

[Darrel De Freitas]

I followed the instructions on the site and got the app installed on an AWS EC2 instance.

The command line instructed me to go to http://localhost:8080.

I visited the public IP at port 8080 and I get an ERR_CONNECTION_REFUSED in Google Chrome.

I've checked my security group to ensure that port 8080 is allowed for TCP access from anywhere.

Any ideas why this isn't working?

EDIT: I've also tried changing the default port in /opt/atlassian/jira/conf/server.xml

[Grigory Salnikov]

What happens if you try to 

wget http://localhost:8080

 directly on the instance?

[Darrel De Freitas]

--2018-05-23 19:19:12--  http://localhost:8005/

Resolving localhost (localhost)... 127.0.0.1

Connecting to localhost (localhost)|127.0.0.1|:8005... connected.

HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.

Retrying.

[Grigory Salnikov]

I think it's worth trying to look through atlassian-jira.log. There may be some useful information.

[Nic Brough -Adaptavist-]

I notice you tried port 8005 there, not 8080.  What does 8080 give?

[Grigory Salnikov]

Ok, the port may be blocked by the firewall or something. Which OS you use?

[Darrel De Freitas]

Amazon Linux AMI 2018.03.

I checked the security group and and the port is set to allow access. I even temporarily allowed access on all ports for all services in the security group.

[Grigory Salnikov]

Ok. If you list all the connections on your host

netstat -tulpn

does it show that the there's a process listening to that port? 

[Darrel De Freitas]

I ran that but I don't see anything running for that port.

Also tried doing :

sudo service jira start

which ends saying that Tomcat started

EDIT: Changed the port number again, did a full system reboot and then stopped and started the jira service and now netstat shows me something running on my port (8005)

Opened up the port on the AWS security group, but I still can't access it :/

[Grigory Salnikov]

Hi!

If you run (from any remote host)

telnet <public ip> 8080

is your connection successfull? 

[Darrel De Freitas]

Well I tried port 10247 since that's what I had changed it to in my config and I got this back:

telnet: connect to address xx.xx.xx.xx: Operation timed out

I also tried 8080 (in case I didn't make the config change right) and it immediately  comes back with a connection refused error.