The remote authentication server is not available.

[IT@tarus.com]

We changed our jira port from 8080 to 80. Now bitbucket gives the error:

The remote authentication server is not available. 

I did the local user 'recovery_admin' solution by putting

JVM_SUPPORT_RECOMMENDED_ARGS=-Datlassian.recovery.password=somepassword

into the _start-webapp.sh file but it still gives that same error.

[IT@tarus.com]

Thanks for the suggestions Bastian. I'm not sure if that would solve the issue of the development team being unable to resolve their credentials or if being able to finally log on to bitbucket (at least locally) would allow me to successfully repair the link to the jira server again but I had just come up with a workaround. It doesn't resolve the issue but it does make it moot. I was able to set Jira back to 8080 and remove the split dns so lan traffic to the server now hits our firewall. Not the most efficient routing of network traffic but certainly not a problem. That allowed me to create a firewall rule that mapped the lan traffic to port 8080. So we can just leave our jira installation running on 8080 now. I will note your suggestion for possible future needs.

[Bastian Stehmann]

If you can login when changing back the port, just do that and create a admin user in the Bitbucket local directory, you should be able to use that one even when you change back the port to 80.

[Bastian Stehmann]

Hi IT@tarus.com ,

You will have to recreate the Application Links for Jira-Bitbucket.

You should be able to do that from Jira, afterwards authentication should work again as usual. 

[IT@tarus.com]

The links in Jira to Bitbucket are good.

I can't log in to Bitbucket to fix the link from Bitbucket to Jira.

If I change the port back to 8080 in jira I can log in to bitbucket. I can edit the link to Jira from within Bitbucket and change it to 80. But when I put Jira back to port 80 I cannot log in to bitbucket any more. I wanted to use the local account because presumably it doesn't need Jira to authenticate and perhaps changing the link to Jira to use port 80 while Jira is using that port might make a difference. But the local recovery_admin user says invalid username or password

[IT@tarus.com]

recreate the links rather than edit the existing link? Maybe that will fix it but I have no idea what the three keys are that it's prompting for in the create link wizard