Confluence does not start
Asked by Suresh Ramasuppu:

Our Confluence instance used our Jira user database for authentication. After chaning IP address for the Jira server Confluence refuses to start. How do we change Jira's IP in Confluence via command line? NOTE: Jira is up and running.


Answers:
author: Shannon S
body: Hi Suresh,

It may not be the IP change that is causing Confluence to start but you can begin by attempting to recover admin rights via your Internal Directory in Confluence:

* [Confluence 6.5.0 and earlier](https://confluence.atlassian.com/conf64/restore-passwords-to-recover-admin-user-rights-936511358.html)
* [Most recent version](https://confluence.atlassian.com/doc/restore-passwords-to-recover-admin-user-rights-158390.html)

Once you are logged in with that user, you can go to your User Directory settings and update the connection with Jira to use the correct IP address.

Kind regards,

Shannon

comments: author: Suresh Ramasuppu
body: Hi Shannon,

Thx for the reply. We tried to follow your instructions and Confluence starts but the recovery password does not work. It seems it still tries to use Jira to authenticate. Please find the logs below:

Caused by: org.apache.http.conn.HttpHostConnectException: Connect to 10.46.10.49:8080 \[/10.46.10.49\] failed: Network is unreachable (connect failed)

at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)

at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)

at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)

at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)

at org.apache.http.impl.client.cache.CachingExec.callBackend(CachingExec.java:592)

at org.apache.http.impl.client.cache.CachingExec.execute(CachingExec.java:269)

at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)

at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)

at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)

at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)

at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)

at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.executeCrowdServiceMethod(RestExecutor.java:574)

at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:413)

at com.atlassian.crowd.integration.rest.service.RestCrowdClient.authenticateUser(RestCrowdClient.java:162)

at com.atlassian.crowd.directory.RemoteCrowdDirectory.authenticate(RemoteCrowdDirectory.java:194)

at com.atlassian.crowd.directory.DbCachingRemoteDirectory.authenticateAndUpdateInternalUser(DbCachingRemoteDirectory.java:272)

at com.atlassian.crowd.directory.DbCachingRemoteDirectory.authenticate(DbCachingRemoteDirectory.java:183)

at com.atlassian.crowd.manager.directory.DirectoryManagerGeneric.authenticateUser(DirectoryManagerGeneric.java:311)

at com.atlassian.crowd.manager.application.ApplicationServiceGeneric.authenticateUser(ApplicationServiceGeneric.java:198)

at com.atlassian.crowd.embedded.core.CrowdServiceImpl.authenticate(CrowdServiceImpl.java:75)

... 188 more

Caused by: java.net.ConnectException: Network is unreachable (connect failed)

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)

at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)

at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)

at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

at java.net.Socket.connect(Socket.java:589)

at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:74)

at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)

... 207 more


author: Nic Brough -Adaptavist-
body: The first line of the log tells you that the network can't be reached. That's a problem with your network, not Confluence or Jira. You'll need to get the routing and/or network fixed on that machine.


author: Shannon S
body: Hi Suresh,

In addition to what Nic said, the article I sent you earlier in Step 3 asks you to [set the Internal Directory to First position](https://confluence.atlassian.com/conf64/restore-passwords-to-recover-admin-user-rights-936511358.html#RestorePasswordsToRecoverAdminUserRights-Step3.PuttheInternalDirectoryinFirstPosition), so it shouldn't still be trying with Jira. In addition, I would recommend setting Jira to inactive, so:

```
update cwd_directory set active = 'F' where id = <Jira Directory id>;
```

Please give that a try and let us know how it goes.