Application Links remainigs after migrating Confluence and Jira
Asked by Dimitri Sedich:

We had a server named jira.weisagd.local, where Jira and Confluence (actually also Bitbucket) were running.

After migrating to the other server (with different IP) we removed the App Link and created it new pointing to IP of the new server (the white list was also updated) . The LDAP synchronization works fine. But login in Confluence fails.

We tried then to update the admin password from Confluence. And there was an error containing those old server name in message:

```
java.net.UnknownHostException: jira.weisagd.local: Name or service not known


Caused by: java.net.UnknownHostException: jira.weisagd.local: Name or service not known	at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)	at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:929)	at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324)	at java.net.InetAddress.getAllByName0(InetAddress.java:1277)	at java.net.InetAddress.getAllByName(InetAddress.java:1193)	at java.net.InetAddress.getAllByName(InetAddress.java:1127)	at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45)	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:112)	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381)	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)	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:185)	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)	at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.executeCrowdServiceMethod(RestExecutor.java:487)	at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andCheckResponse(RestExecutor.java:453)	at com.atlassian.crowd.integration.rest.service.RestCrowdClient.updateUserCredential(RestCrowdClient.java:238)	at com.atlassian.crowd.directory.RemoteCrowdDirectory.updateUserCredential(RemoteCrowdDirectory.java:257)	at com.atlassian.crowd.directory.DbCachingRemoteDirectory.updateUserCredential(DbCachingRemoteDirectory.java:545)	at com.atlassian.crowd.manager.directory.DirectoryManagerGeneric.updateUserCredential(DirectoryManagerGeneric.java:424)	at com.atlassian.crowd.manager.application.ApplicationServiceGeneric.updateUserCredential(ApplicationServiceGeneric.java:626)	at com.atlassian.crowd.embedded.core.CrowdServiceImpl.updateUserCredential(CrowdServiceImpl.java:310)
```

```
I suppouse there is a remainig from old server there, but I don't know where to look for it.

```


Answers:
author: Fabian Lim
body: Hi [@Dimitri Sedich](/t5/user/viewprofilepage/user-id/3340899)

I recommend you go through the troubleshooting guide here: <https://confluence.atlassian.com/kb/application-links-troubleshooting-guide-718668765.html>

If you still have issues, contact atlassian support.

Regards


Tags: confluence-server

server