The remote authentication server is not available. Please try again later.

I'm getting this error when trying to log into stash. Stash is configured to use the Jira Directory. The only thing that changed since it last worked is the IP for the VM both Stash and Jira are running on.

It seems to be a cache issue and everything I find online says to remove and recreate the directory. My problem is that I have absolutely no access to stash (I'm logged out). I get the same error when logging into the account on the local stash directory ( id : 32769 )

Does anyone know how I could proceed?

Here's the stash-atlassian tail logs:

2014-07-08 17:42:23,424 ERROR [scheduler_Worker-1] c.a.c.d.DbCachingDirectoryPoller Error occurred while refreshing the cache for directory [ 229377 ].

com.atlassian.crowd.exception.OperationFailedException: Connection reset

at$MethodExecutor.andReceive( ~[crowd-integration-client-rest-2.7.2-rc2.jar:na]

at ~[crowd-integration-client-rest-2.7.2-rc2.jar:na]

at ~[crowd-remote-2.7.2-rc2.jar:na]

at ~[crowd-ldap-2.7.2-rc2.jar:na]

at ~[crowd-core-2.7.2-rc2.jar:na]

at ~[crowd-core-2.7.2-rc2.jar:na]

at com.sun.proxy.$Proxy121.synchronise(Unknown Source) ~[na:na]

at ~[crowd-core-2.7.2-rc2.jar:na]

at [crowd-core-2.7.2-rc2.jar:na]

at org.springframework.scheduling.quartz.QuartzJobBean.execute( [spring-context-support-4.0.0.RELEASE.jar:4.0.0.RELEASE]

at [quartz-1.8.6.jar:na]

at org.quartz.simpl.SimpleThreadPool$ [quartz-1.8.6.jar:na]

... 11 frames trimmed

Caused by: Connection reset

at ~[na:1.7.0_51]

at ~[na:1.7.0_51]

at ~[na:1.7.0_51]

at ~[na:1.7.0_51]

at org.apache.commons.httpclient.HttpParser.readRawLine( ~[commons-httpclient-3.1.jar:na]

at org.apache.commons.httpclient.HttpParser.readLine( ~[commons-httpclient-3.1.jar:na]

at org.apache.commons.httpclient.HttpConnection.readLine( ~[commons-httpclient-3.1.jar:na]

at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine( ~[commons-httpclient-3.1.jar:na]

at org.apache.commons.httpclient.HttpMethodBase.readStatusLine( ~[commons-httpclient-3.1.jar:na]

at org.apache.commons.httpclient.HttpMethodBase.readResponse( ~[commons-httpclient-3.1.jar:na]

at org.apache.commons.httpclient.HttpMethodBase.execute( ~[commons-httpclient-3.1.jar:na]

at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry( ~[commons-httpclient-3.1.jar:na]

at org.apache.commons.httpclient.HttpMethodDirector.executeMethod( ~[commons-httpclient-3.1.jar:na]

at org.apache.commons.httpclient.HttpClient.executeMethod( ~[commons-httpclient-3.1.jar:na]

at org.apache.commons.httpclient.HttpClient.executeMethod( ~[commons-httpclient-3.1.jar:na]

at$MethodExecutor.executeCrowdServiceMethod( ~[crowd-integration-client-rest-2.7.2-rc2.jar:na]

at$MethodExecutor.andReceive( ~[crowd-integration-client-rest-2.7.2-rc2.jar:na]

... 12 common frames omitted

1 answer

1 accepted

This was related to a dns issue. Had it resolved once the server could properly resolve domains

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

682 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot