Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Stash setup on Linux: Can't access http://ip:7990/ from a remote host

momchilov March 28, 2013

I'm doing a Stash 2.3.0 setup for a client and I noticed that I cannot access it through a remote host.

On the local machine, netstat output:

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0       *:7990             *:*                     LISTEN         8940/java

Previously, it listened on tcp6, so I added "-Djava.net.preferIPv4Stack=true" to JVM_REQUIRED_ARGS in setenv.sh. That solved that, but still no joy.

iptables chains are empty, so I don't see why access could be blocked from the outside. Any suggestions are welcome!

I tried also changing the port. Same result.

The same host is running a JIRA setup. No problem with installation there.

One minor detail, the server is actually EC2

10 answers

1 vote
Alan Lindsay May 31, 2013

Actually, I'm back after restarting my EC2 instance and both http and https connections are working. Sorry I can't provide any help, this one solved itself.

0 votes
Yoaquim Cintron March 5, 2014

Total newbie here, and I'm having the same issue. Can't access from outside; it's behind a VPN, and pinging the inner IP works, as well as ssh and ftp: I'm assuming I just can't http/https from the outside.

0 votes
Alan Lindsay May 31, 2013

I'm having the same issue. In my case I can telnet to the box fine, but when I load in the browser it refuses the connection. This is true for both http and https configurations. I have both default open on AWS. Any help is greatly appreciated. Stash is DOA for me so far.

0 votes
momchilov March 28, 2013

it's a firewall. I tried to listen to a port with netcat and see if I could telnet there.

0 votes
Andy Brook [Plugin People]
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.
March 28, 2013

ok, spin another way, can you telnet to the external IP on the server to the port you expect?

0 votes
Alexey_Efimov
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.
March 28, 2013

If telnet failed by timeout it is firewall issues. Cos in other case you should get quick error (if listeneing on wrong interface).

0 votes
momchilov March 28, 2013

I tried changing the port. There's also a JIRA I've installed, currently running. No such problems there.

0 votes
Andy Brook [Plugin People]
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.
March 28, 2013

can you ping the server from the remote client? Is there another service you can check with telnet, eg ssh/http? ie validate connectivity of some kind. Whats the infrastructure between server and client, any proxies or firewalls?

0 votes
Andy Brook [Plugin People]
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.
March 28, 2013

rule out the server, try telnet host:7990, if you get a connect, its your client, probably.

0 votes
momchilov March 28, 2013

tried it. telnet timed out.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events