Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

error 502, service running but port 8090 not open

Steve Boydon
Contributor
May 11, 2019

Hi

More problems with my Confluence setup.

Currently running on EC2 instance t2.small

On trying to connect I am getting connection refused 502 bad gateway via Nginx

I've installed 'links' on my Confluence box and run it from the command line and get the connection refused error. On doing a netstat -plnt I get the following output

 

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name     
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      620/systemd-resolve  
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      899/sshd             
tcp6       0      0 :::22                   :::*                    LISTEN      899/sshd

 



And for some reason port 8090 is not open. I have another server and it shows

 

 

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      -                
tcp        0      0 0.0.0.0:5432            0.0.0.0:*               LISTEN      -                
tcp6       0      0 :::46809                :::*                    LISTEN      -                
tcp6       0      0 :::8090                 :::*                    LISTEN      -                
tcp6       0      0 :::443                  :::*                    LISTEN      -                
tcp6       0      0 127.0.0.1:8000          :::*                    LISTEN      -                
tcp6       0      0 :::8009                 :::*                    LISTEN      -                
tcp6       0      0 :::80                   :::*                    LISTEN      -                
tcp6       0      0 :::22                   :::*                    LISTEN      -                
tcp6       0      0 :::5432                 :::*                    LISTEN      -

 

My server.xml is as below.

 

<Server port="8000" shutdown="SHUTDOWN" debug="0">
   <Service name="Tomcat-Standalone">

<Connector port="8090" connectionTimeout="20000" redirectPort="8443"
                  maxThreads="48" minSpareThreads="10"
                  enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
                  protocol="org.apache.coyote.http11.Http11NioProtocol"

               scheme="https" secure="true" proxyName="<subdomain>.<domain>.com" proxyPort="443"/>


<Engine name="Standalone" defaultHost="localhost" debug="0">
           <Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="false" startStopThreads="4">
               <Context path="" docBase="../confluence" debug="0" reloadable="false" useHttpOnly="true">
                   <!-- Logging configuration for Confluence is specified in confluence/WEB-INF/classes/log4j.properties -->
                   <Manager pathname=""/>
                   <Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60"/>
               </Context>

               <Context path="${confluence.context.path}/synchrony-proxy" docBase="../synchrony-proxy" debug="0"
                        reloadable="false" useHttpOnly="true">
                   <Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60"/>
               </Context>
           </Host>
       </Engine>
   </Service>
</Server>

 

Is there any reason why from a default install Confluence wont start

 

using 6.15.4

 

Regards

 

Steve

 

2 answers

2 accepted

0 votes
Answer accepted
Jakub Irzyński
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 11, 2019
Steve Boydon
Contributor
May 11, 2019

So is this a bug in the release

0 votes
Answer accepted
Steve Boydon
Contributor
May 11, 2019

Hi

I installed 6.13.4 on another instance and it seems to work.

Although another error as arisen.

Will start a new thread as a different error

 

rgds

Steve

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events