after the port was changed from 8090 to 80, it stopped working.
Asked by Burlakov Eduard:

Hello,

I edited server.xml files

It was

```

<Server port="8000" shutdown="SHUTDOWN" debug="0">
??? <Service name="Tomcat-Standalone">
??????? <!--
???????? ==============================================================================================================
???????? DEFAULT - Direct connector with no proxy, for unproxied HTTP access to Confluence.

???????? If using a http/https proxy, comment out this connector.
???????? ==============================================================================================================
??????? -->
??????? <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"/>


```

has become

```

<Server port="8000" shutdown="SHUTDOWN" debug="0">
??? <Service name="Tomcat-Standalone">
??????? <!--
???????? ==============================================================================================================
???????? DEFAULT - Direct connector with no proxy, for unproxied HTTP access to Confluence.

???????? If using a http/https proxy, comment out this connector.
???????? ==============================================================================================================
??????? -->
??????? <Connector port="80" connectionTimeout="20000" redirectPort="8443"
?????????????????? maxThreads="48" minSpareThreads="10"
?????????????????? enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
?????????????????? protocol="org.apache.coyote.http11.Http11NioProtocol"/>
```

after that the server stopped working.

If I return everything as it was, then everything will start working.

In logs

```
2018-11-21 01:44:37,257 WARN [synchrony-interop-executor:thread-3] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:80/synchrony-proxy/healthcheck]: Connect to 127.0.0.1:80 [/127.0.0.1] failed: Connection refused (Connection refused)
2018-11-21 01:45:07,258 WARN [synchrony-interop-executor:thread-3] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:80/synchrony-proxy/healthcheck]: Connect to 127.0.0.1:80 [/127.0.0.1] failed: Connection refused (Connection refused)
2018-11-21 01:45:37,259 WARN [synchrony-interop-executor:thread-3] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:80/synchrony-proxy/healthcheck]: Connect to 127.0.0.1:80 [/127.0.0.1] failed: Connection refused (Connection refused)
2018-11-21 01:46:07,261 WARN [synchrony-interop-executor:thread-3] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:80/synchrony-proxy/healthcheck]: Connect to 127.0.0.1:80 [/127.0.0.1] failed: Connection refused (Connection refused)
2018-11-21 01:46:37,262 WARN [synchrony-interop-executor:thread-3] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:80/synchrony-proxy/healthcheck]: Connect to 127.0.0.1:80 [/127.0.0.1] failed: Connection refused (Connection refused)
2018-11-21 01:47:07,264 WARN [synchrony-interop-executor:thread-3] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:80/synchrony-proxy/healthcheck]: Connect to 127.0.0.1:80 [/127.0.0.1] failed: Connection refused (Connection refused)
2018-11-21 01:47:37,265 WARN [synchrony-interop-executor:thread-3] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:80/synchrony-proxy/healthcheck]: Connect to 127.0.0.1:80 [/127.0.0.1] failed: Connection refused (Connection refused)
2018-11-21 01:48:07,266 WARN [synchrony-interop-executor:thread-3] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:80/synchrony-proxy/healthcheck]: Connect to 127.0.0.1:80 [/127.0.0.1] failed: Connection refused (Connection refused)
2018-11-21 01:48:37,268 WARN [synchrony-interop-executor:thread-3] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:80/synchrony-proxy/healthcheck]: Connect to 127.0.0.1:80 [/127.0.0.1] failed: Connection refused (Connection refused)
2018-11-21 01:48:47,008 WARN [Caesium-1-2] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
2018-11-21 01:49:07,269 WARN [synchrony-interop-executor:thread-3] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:80/synchrony-proxy/healthcheck]: Connect to 127.0.0.1:80 [/127.0.0.1] failed: Connection refused (Connection refused)
2018-11-21 01:49:37,270 WARN [synchrony-interop-executor:thread-3] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:80/synchrony-proxy/healthcheck]: Connect to 127.0.0.1:80 [/127.0.0.1] failed: Connection refused (Connection refused)
```


Answers:
author: Burlakov Eduard
body: So, I create confluence user as root and I turn off the synchrony module. These errors ceased to appear.

But the confluence is not work.

The situation, as soon as I changed the port from 8090 to 80 in the confluence, this confluence stops working


author: Daniel Eads
body: Hi Burlakov,

I see from your previous posts on Community that you're probably running on Server 2012. In this case I'd actually recommend not using the server.xml file to change to port 80, but instead set up IIS as a reverse proxy. IIS would serve port 80 (or 443 if you set up HTTPS) and on the backend, IIS would connect to Confluence over port 8990.

We have a document with [all the details you need to set this up with IIS 8.0](https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-microsoft-internet-information-services-iis-833931378.html) on Windows Server.

If you can go through those instructions and let me know if you run into any issues with the setup, I am happy to help.

Cheers,  
Daniel

comments: author: Burlakov Eduard
body: No,

I use CentOS 7.4 server.


author: Daniel Eads
body: Ah, in that case this should be easier! You can [proxy with nginx instead following this document](https://confluence.atlassian.com/confkb/how-to-use-nginx-to-proxy-requests-for-confluence-313459790.html).

I would not recommend running Confluence as a root user.

The nginx guide will be similar - Confluence will serve over 8090 on the localhost but nginx will proxy the ports so that you can access it over port 80. nginx will do all the communication on the backend with Confluence over the higher ports.

Cheers,  
Daniel


author: Alexey Matveev
body: Hello,

You would need to grant the root permissions to the Confluence user. But it is a bad practice.

Kindly read this thread:

<https://community.atlassian.com/t5/Confluence-questions/How-to-Configure-Confluence-server-IP-port-from-8090-to-80/qaq-p/47325>