I run Jira-Software on a dedicated server in a docker container. I dont want my users to use the IP address of this server to access jira. Instead I want them to use a subdomain lets call it jira.abc.com But for that I have to forward the subdomain to the server IP. For that I us an .htaccess file with the proxy flag, which works perfectly.
So a user types in the browser https://www.jira.abc.com and the .htaccess proxy forwards the user to the IP, while in the browser the url is still displayed. Everything fine so far.
--- .htaccess ---
RewriteRule (.*)$ http://SERVER_IP:9990/$1 [P]
For some reason jira is very slow, but besides of that everything seems to work fine.
One problem I have is that jira logs this exception, which so far I now means something like it cannot reach itself over the url.
HealthCheck:thread-3 ERROR [c.a.t.j.healthcheck.support.GadgetFeedUrlHealthCheck] An error occurred when performing the Gadget feed URL healthcheck java.net.SocketTimeoutException: Read timed out
In the /opt/atlassian/jira/server.xml I edited the Connector and added the following:
The questions I have are the following:
- Can I use a .htaccess file as proxy?
- Could the exception above be the reason why jira is so slow?
in that case, please, use mod_proxy module
That article will help you
I have written a short tutorial for people who want to learn the basics of Apache URL rewriting. You can read the tutorial to improve your URL rewriting skills.
Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their Jira Cloud instance. ...
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