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?
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:
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
[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
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.
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.
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.
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.
Hi Atlassian community, My name is Max and I work on the product integration team at Atlassian. I am pleased to announce the early access program for the Jira Cloud add-in for Outlook. This add-in...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events