The requested URL /secure/MyJiraHome.jspa was not found on this server. I keep getting this error after configuring apache with Jira's instructions.
That's not what the documentation says.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So, you're saying that following the documentation worked then?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
All of the documentation worked when I uncommented the SSL port in the server.xml file. With the SSL port commented out the configuration did not work. I also added "*:443" as the virtual host compared to just "*" the way the documentation has it listed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The documentation you've said you've been reading doesn't mention the SSL ports at all.
So, I assume you did something undocumented, and then when you un-did it, it worked? Or you've not pointed us at what you actually followed? (Such as the doc which tells us how to uncomment the ssl connection)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would like to point out that I followed the directions, to a t @ https://confluence.atlassian.com/adminjiraserver070/integrating-jira-with-apache-using-ssl-749383660.html AND https://confluence.atlassian.com/doc/using-apache-with-mod_proxy-173669.html Got the same error as the OP. No where in that documentation does it say to edit the tomcat server.xml file to uncomment out the https connector (it is defaulted to being commented out).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That implies you've got the config wrong somewhere - which documentation did you follow, and what did you do differently, or what's the non-standard setup of your server?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm afraid we're kind of stuck then.
If you've followed those instructions, Jira and Apache work - I did this last Thursday, so I know it works.
First question is what you've done to debug this - you're saying a single URL doesn't work - what about the others you've tried? Is Jira actually running at all? Is it serving up some pages and not others? Probably ost useful - what do your log files say?
Next question is to try to establish exactly where the issue might be. What are you running this on (rough outline of the hardware and OS), what versions of Java, Jira and Apache?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am in same situation. I am on a deadline. I am filling for my web admin who is on extended leave. Now I need to deploy JIRA to production soon. I am having tough time with jira running on https. Here is what I have 1. I have a server which is already configured for apache and tomcat and ssl 2. my java apps work fine that uses https 3. I installed jira with port 8090 and it works fine 4. Now I needed to use https 5. I added a context path /jira to server.xml 6. i changed my tomcat_proxies.conf file to reflect RewriteCond %{REMOTE_ADDR} !127.0.0.1 RewriteCond %{REMOTE_ADDR} !205.156.38.16 RewriteCond %{REMOTE_ADDR} !205.156.38.59 RewriteCond %{REQUEST_URI} ^/jira($|/.*) RewriteCond %{SERVER_PORT} ^80$ RewriteRule .* https://server url [R,L] 7. i get this error 'jira/secure/MyJiraHome.jspa'. How do i resolve this? What am I doing wrong? Please help. We are under the impression that by buying jira, we get technical support for 1st year. I need help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Step 6 - that's not right. You absolutely should never rewrite 127.0.0.1 in any case, and the documentation makes no mention of rewrites, it uses proxies. Could you try it with the proxies as documented instead?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.