Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Localhost Jira won't allow me to log in

KO89 May 14, 2019

Hello!!

I'm having an issue after upgrading from Jira Server 7.6.1 to Jira Server 8.1. After the upgrade I replaced the server.xml file with the one I used in 7.6.1 in order to retain my proxy server settings. This worked and users are now able to login on the HTTPs portion of it but when I as an admin attempt to login on the backend HTTP localhost site the screen flashes once and goes back to the login page. The credentials arent wrong because when I purposefully type in the wrong password it tells me that my username/password are incorrect. This issue doesn't tell me anything but redirect me to the login page. I've uploaded a screenshot of what the logs say after this occurs. 

Back-end Jira error.png

Hope this helps. Any assistance would be appreciated; Cheers.

1 answer

1 vote
Jakub Sławiński
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 14, 2019

Hi @KO89 ,

 

can you attach the full stacktrace?

KO89 May 14, 2019

Sure, I've attached it via this message.

Jira Atlassian Log

Didn't want to jam this message with logs so I uploaded the file into my Azure storage. let me know if you have issues opening it.

Jakub Sławiński
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 14, 2019

Yes, I can open it and see the following issue:

 

2019-05-14 09:55:36,739 http-nio-8080-exec-18 ERROR anonymous 595x9876x1 - 10.10.1.7 /plugins/servlet/gadgets/dashboard-diagnostics [c.a.g.d.internal.diagnostics.DiagnosticsServlet] DIAGNOSTICS: FAILED
com.atlassian.gadgets.dashboard.internal.diagnostics.UrlSchemeMismatchException: Detected URL scheme, 'https', does not match expected scheme 'http'

 

so you should fix your configuration regarding https/http.

KO89 May 14, 2019

Roger that, the issue probably exists somewhere in my server.xml file. I'd have to dig to find it

Suggest an answer

Log in or Sign up to answer