Forums

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

Disable https

Aleks
Contributor
January 4, 2019

Hi Folks

I tried to run Jira over https. But this didn't work, so I going back to http. 

I changed the httpd.conf (Apache Proxy) and the server.xml back and restarted apache and jira. But I'am still getting redirected to https://jira.<someting>.com:8443/jira$

Did I forgot someting?

1 answer

0 votes
Nic Brough -Adaptavist-
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.
January 4, 2019

You might be better off trying to fix "run over https, but this didn't work", as https is strongly recommended for any system on a network nowadays.

But, what you might be missing are:

  • Whatever in Apache might be redirecting http to https (you might not have done this, so there might be nothing to check)
  • The base url in Jira
  • The connector settings in the server.xml (have you removed all three things that enable https?)
  • The urls in the reverse proxy settings in apache
Aleks
Contributor
January 4, 2019

Thank you for your fast reply!

I have to fix jira first. Afterwards I will give another try for https. At the moment I can't connect to jira neither over https nor http.

In the server.xml connector string port, proxyport and scheme is set as described.

the urls in the httpd.conf are also set to http

Nic Brough -Adaptavist-
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.
January 4, 2019

Ok, so what are the errors in the logs, and/or the errors you get when you try to reach it?

Aleks
Contributor
January 4, 2019

Browser: ERR_CONNECTION_TIMED_OUT

Apache:

[Fri Jan 04 14:51:46.786917 2019] [proxy:error] [pid 1812:tid 1064] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957: HTTP: attempt to connect to <IP-Addrss>:8080 (<jira-name>) failed
[Fri Jan 04 14:51:46.786917 2019] [proxy_http:error] [pid 1812:tid 1064] [client <ip-address>:46392] AH01114: HTTP: failed to make connection to backend: <jira-name>

 

no errors in jira

Aleks
Contributor
January 4, 2019

how can I change the base url in jira - i cannot connect to jira

Nic Brough -Adaptavist-
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.
January 4, 2019

Don't worry about the base url yet - it could be taking you back to https, but it won't stop you connecting to Jira.  You need to get that working before you can change the base url.

The error you have there is that Jira is not responding to the proxy.   The usual reason for that error is that Jira is not running.

You'll need to read the Jira application logs to find out why it's not running.

Aleks
Contributor
January 4, 2019

I checked the database, the base url should be right.

The jira-service is running - I am sure because I am receiving notification emails from jira e.g. Service desk new issue created.

Nic Brough -Adaptavist-
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.
January 4, 2019

Ok, so it's running, but not serving - again, you'll need to read the logs to find out why, and check where it is supposed to be listening to you.

Aleks
Contributor
January 4, 2019

any recommendations in wich logs I should start searching?

Nic Brough -Adaptavist-
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.
January 4, 2019

You should find out if Jira is failing by reading through <jira home>/log/atlassian-jira.log.If there's no smoking gun in there, try <jira install>/log/catalina.out  for the Tomcat log - this should catch cases where Tomcat starts ok and looks like Jira is running, but it can't get Jira to start internally.

Suggest an answer

Log in or Sign up to answer