Forums

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

Can't log in after using proxy

Jeffry Parks
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 4, 2018

I had the system admin create a proxy so that I can go to jira.company.com and have it land on JIRA.

After they made the proxy, I can't seem to log in. I can only log in if I go to the IP address instead of the new URL.

When I put in the username and password and click 'log in', it just takes me back to the login page (effectively refreshing the page). When I type in the wrong password, it will have the box that says 'wrong password'.

I looked at the network tab in chrome and it looks like the login cookie is not being set. Maybe that has nothing to do with it

 

Any advice?

2 answers

1 vote
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 8, 2018

When you setup a proxy in front of Jira, there are steps you need to take both to Jira's configuration and the proxy's configuration in order to make sure that this connection works as expected. 

As a general outline, I'd recommend trying to walk through the guide Proxying Atlassian server applications with Apache HTTP Server (mod_proxy_http)

It's a generalize guide you can use to proxy most Atlassian applications with an Apache HTTP server.  I am not sure what proxy type your environment is using, but there are also other more specific guides for nginx, iis, etc.

I suspect that the proxy might have been setup to redirect to the correct address, but that Jira's own $JIRAINSTALL/conf/server.xml file has not yet been updated to make sure that the connector that proxy is redirecting traffic to is aware of this redirection.   Try checking the <Connector> tags to see if you have more than one connector, note what port they use, and also see if they have the proxyName, proxyPort, scheme parameters listed and what values these have.   By default Jira won't use these parameters in the connector if you are not using a proxy (ie just using Jira's own tomcat to serve up content).

If you have to make changes to this file to match up with that guide above, you will need to save that file and restart Jira for these changes to take effect.

0 votes
Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 5, 2018

Hi Jeffry,

Could you confirm if this is indeed for Cloud? I saw your atlassian-cloud tag so I wanted to be sure.

If so, setting a custom domain is not possible using the Cloud environment in that manner.

There's a feature request for it below:

If it's for Jira Server, can you tell us your server version? 

Regards,

Shannon

Jeffry Parks
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 5, 2018

I’m sorry, no this is for JIRA server. Not sure why that tag is there

Suggest an answer

Log in or Sign up to answer