Login Network Error after migration
Asked by arturs:

Hi, I am in the process of migrating a Confluence 5.9.6 installation from Windows to Linux in a test environment before the actual migration. I have so far succefully completed it for the JIRA side but having some issues with Confluence.

The XML restore went as expected however it is not allowing me to login with this error:

```
The following error(s) occurred:Sorry, a network error occurred trying to log you in. Please try again, and contact your administrator if the problem persists.
```

I installed confluence using the default ports (8090) but looking at the logs it is trying to authenticate using the old custom port numbers from the JIRA install (7080).

```
Caused by: org.apache.http.conn.HttpHostConnectException: Connect to localhost:7080 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused
```

I have checked the server.xml file and all the settings are correct.

By the looks of it Confluence was set up to use JIRA authentication. Any way I can manually point it to the new JIRA location on8080?

After completing all the suggestions made by Jonathan I started seeing new log entries:

```
2016-06-19 18:07:31,670 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache INCREMENTAL synchronisation for directory [ 131073 ] starting2016-06-19 18:07:31,672 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache Attempting INCREMENTAL synchronisation for directory [ 131073 ]2016-06-19 18:07:31,672 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache Incremental synchronisation for directory [ 131073 ] was not completed, falling back to a full synchronisation2016-06-19 18:07:31,672 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache INCREMENTAL synchronisation for directory [ 131073 ] was not successful, attempting FULL2016-06-19 18:07:31,679 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache failed synchronisation complete for directory [ 131073 ] in [ 9ms ]2016-06-19 18:07:31,696 ERROR [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingDirectoryPoller] pollChanges Error occurred while refreshing the cache for directory [ 131073 ].com.atlassian.crowd.exception.OperationFailedException: org.apache.http.conn.HttpHostConnectException: Connect to localhost:7080 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused        at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:493)        at com.atlassian.crowd.integration.rest.service.RestCrowdClient.searchUsers(RestCrowdClient.java:557)        at com.atlassian.crowd.directory.RemoteCrowdDirectory.searchUsers(RemoteCrowdDirectory.java:371)        at com.atlassian.crowd.directory.ldap.cache.RemoteDirectoryCacheRefresher.findAllRemoteUsers(RemoteDirectoryCacheRefresher.java:55)        at com.atlassian.crowd.directory.ldap.cache.RemoteDirectoryCacheRefresher.synchroniseAllUsers(RemoteDirectoryCacheRefresher.java:90)        at com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseAll(AbstractCacheRefresher.java:89)        at com.atlassian.crowd.directory.ldap.cache.EventTokenChangedCacheRefresher.synchroniseAll(EventTokenChangedCacheRefresher.java:67)        at com.atlassian.crowd.directory.DbCachingRemoteDirectory.synchroniseCache(DbCachingRemoteDirectory.java:1122)        at com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:76)        at com.atlassian.crowd.directory.DbCachingDirectoryPoller.pollChanges(DbCachingDirectoryPoller.java:50)        at com.atlassian.crowd.manager.directory.monitor.poller.DirectoryPollerJobRunner.runJob(DirectoryPollerJobRunner.java:93)        at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153)        at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118)        at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97)        at com.atlassian.scheduler.quartz1.Quartz1Job.execute(Quartz1Job.java:32)        at org.quartz.core.JobRunShell.run(JobRunShell.java:223)        at com.atlassian.confluence.schedule.quartz.ConfluenceQuartzThreadPool.lambda$runInThread$0(ConfluenceQuartzThreadPool.java:16)        at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)Caused by: org.apache.http.conn.HttpHostConnectException: Connect to localhost:7080 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused        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 org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)        at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.executeCrowdServiceMethod(RestExecutor.java:598)        at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:481)        ... 17 moreCaused by: java.net.ConnectException: Connection refused        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)        ... 30 more
```

Thanks

A


Answers:
author: Jonathan Soo
body: Hi Arturs,

Are you logging in to Confluence as a user from JIRA ? If yes, since the base url has changed, I'm afraid the following could be one of the reasons why :

1. JIRA does not include Confluence server IP address in [JIRA User Server](https://confluence.atlassian.com/display/JIRA/Allowing+Other+Applications+to+Connect+to+JIRA+for+User+Management) settings
2. JIRA has not [whitelisted](https://confluence.atlassian.com/display/JIRA/Configuring+the+Whitelist) Confluence server or IP address, despite both of them located within same server.
3. There is a proxy or firewall that blocks such access from Confluence to JIRA

The base url was stored in Confluence database : `BANDANA` table, column name `BANDANAVALUE` with a BANDANAKEY = `atlassian.confluence.settings`.

Would you it be possible for you to use the default for now, login as you in your old server, change the server base url ?

OR

Resolve one(or more) of those 3 issue above in JIRA.

<br />

Hope this helps.

Regards,

Jonathan

comments: author: arturs
body: Thanks Jonathan,

1. JIRA User Server setting is as follows:  
   Confluence - localhost - 44e469c7-c519-3e67-ad36-caf14836aedc 127.0.0.1
2. I have added the confluence application to the whitelist, in fact it realized the the path was wrong and offered to find it, it found it automatically and added it to the whitelist
3. I have stopped the firewalld service in centos to test this and the result was the same
4. I changed the base url via the database to point to [http://IP:PORT](http://IPPORT) of the test setup

All of the above has resulted in the same. Network error but I cant see the logs being updated this time, the last entry is still from my first attempt.


author: Cool Baba
body: 1. JIRA User Server setting is as follows:  
   Confluence - localhost - 44e469c7-c519-3e67-ad36-caf14836aedc 127.0.0.1
2. I have added the confluence application to the whitelist, in fact it realized the the path was wrong and offered to find it, it found it automatically and added it to the whitelist
3. I have stopped the firewalld service in centos to test this and the result was the same
4. I changed the base url via the database to point to [http://IP:PORT](http://ipport/)of the test setup

All of the above has resulted in the same. Network error but I cant see the logs being updated this time, the last entry is still from my first attempt.


Tags: confluence-administration