Following the installation instruction, JIRA is now available on :
http://example.com:8080/
However I want it to be accessible on http://jira.example.com.
I followed these instruction : https://confluence.atlassian.com/jira/integrating-jira-with-apache-185729645.html
Now http://example:8080/ redirects on http://jira.example.com but nothing gets displayed.
Any ideas on how I could solve it ?
ps : I am restarting the httpd with "service httpd restart" after each changes.
The issue is that jira.example.com cannot be resolved at all. I suspect you may not have DNS entries in place to resolve to your server. For local testing you could try a hosts file override, but you'll need to modify DNS records in order to resolve this further abroad.
Once resolved in DNS you should have JIRA or Apache errors to further investigate/debug, or if you're lucky you'l have a working JIRA server :)
Related
I chose to force https on my server when setting up let's encrypt, not realizing what a NIGHTMARE it would cause for my Node.js WebSocket server. Nothing that I've found online works to get a secure WebSocket connection up and running. (Probably because I'm using Apache for everything aside from WebSockets)
So I've decided to just disable SSL site-wide. I don't have any real use for it as my server is strictly for development anyway.
I've tried the method here But Apache reports that the site is already disabled. So I cleared the cache on my browser and even tried to visit the site incognito to no avail.
I also looked at the instructions here but NONE of my site-available contain the lines that are mentioned.
Then I saw this post but my apache2.conf file did not contain the lines he mentioned either.
I'm puling my hair out.
If anyone else has this issue, here's what I did to solve it.
I saw a configuration file named <sitenam>-le-ssl.conf in /etc/apache2/sites-enabled So I tried a2dissite <sitename>-le-ssl.conf
But Apache said "the file doesn't exist"
So I copied that file to my home directory with cp <sitename>-le-ssl.conf ~(AND YOU SHOULD TOO! just in case...)
Then I deleted that file with sudo rm <sitename>-le-ssl.conf
Then, restart apache with sudo service apache2 restart
Finally, clear the cache on your browser and visit your site. Everything should be back to normal now.
No idea why letsencrypt set up my server in such an odd way. It didn't follow ANY of the standards that others said it should.
Hope this helps someone in the future.
The ACME server was probably unable to reach http://mydomain/.well-known/acme-challenge/LLtRq6EdfBLmxyhzlFEqL
kDXBUFLsQbaea6A5kiJxIo
Check in a browser to see if the answer file is being served correctly.
This could be caused by IIS not being setup to handle extensionless static
files. Here's how to fix that:
1. In IIS manager goto Site/Server->Handler Mappings->View Ordered List
2. Move the StaticFile mapping above the ExtensionlessUrlHandler mappings.
(like this http://i.stack.imgur.com/nkvrL.png)
3. If you need to make changes to your web.config file, update the one
at C:\applications\letsencrypt\web_config.xml
Getting this error
While creatng ssl certifcate using letsencrypt
tried
1) If you can't browse to this configcheck file in your web browser (http://{your site}/.well-known/acme-challenge/configcheck then the Lets Encrypt service can't access the files it needs either.
=> configcheck is not getting created
You can edit the web.config file in this folder to get extensionless files working, then you can re-request your certificate. A mimeMap entry for either "." or ".*" usually works depending on your operating system version.
=> Edited web.config tried both "." or ".*"
No success
Can anyone please suggest steps to follow
i am using aws sever windows 2008 R2
If you have redirected your domain name from http to https
in virtual host of apache http.conf file
This will cause this issue
please comment that redirect and try it
Got solved
I have an Bitnami Redmine installation on my windows. I access my redmine at http://xxx.xxx.xxx.xxx/redmine. this works well.
Now I want to change the port so that I can access http://xxx.xxx.xxx.xxx:8060/redmine
But when I change my httpd.conf file from my Apache I can't find the redmine homepage.
Did I miss something or does somebody has a solution for this issue?
Are you running under bitnami? if so, there's an extra step of updating this file:
apache2\conf\bitnami\bitnami.conf
maybe this will help you (see item 8) http://www.redmine.org/projects/redmine/wiki/HowTo_Install_Redmine_in_a_sub-URI_on_Windows_with_Apache
...
8. Assuming that we will be hosting Redmine under http://localhost/redmine
Edit C:\webserver\Redmine\config\environment.rb file to configure Redmine to work as a sub-URI (Apache configuration is also required and is listed later on in this document).
add the following line at the bottom of the file:
Redmine::Utils::relative_url_root = "/redmine"
I am running a huge php-application on an ubuntu server, using apache2, php5, mysql.
Sometimes (approx. once a month) the page ist not reachable from the internet ("it's down").
The weird thing is, that service apache2 status says that apache is running.
The solution is always to restart apache using service apache2 restart and everything works fine again.
The server load is at a minimum and can't be part of the problem (I guess).
I know, this description is not as detailed as it should be, but I do not have more information.
Any suggestions about what could cause this problem are appreciated!
Disable Firewall or Antivirus and try again.
Change /etc/apache2/apache2.conf => change all AllowOverride all,
and make sure that /etc/apache2/sites-available/000.default.conf => verify the path of the Directory that you access.
assign the necessary permissions of the webroot directory for the domain.
chmod -R 755 /var/www/html/
I'm setting up a cluster of servers for the company I work at, and I'm using Monit to monitor that all server processes are running and working as they should.
For Apache monitoring, I wanna use the mod_status feature which is explained here. However, this has turned out quite difficult. As no matter how I configure both Monit and Apache, Monit just keeps reporting a connection failure error (connection failed to 127.0.0.1:80 [APACHESTATUS via TCP]).
I followed the instructions on the Monit Wiki without much luck. The Apache status page (http://127.0.0.1/server-status?auto) page works in any browser I test it with. I've also tried changing host the from 127.0.0.1 to localhost without any luck.
I've tested this setup with Monit versions 4.8.x, 4.10x, and 5.0-beta6, all with the same result. Also, there's not much useful info on Google to help either, as most results are about more trivial and simple problems.
Am I missing something? Or am I just plain stupid maybe?
Try to change the authorization in Apache:
Order allow,deny
Allow from all
Check Apache access.log and error.log files - which kind of error is reported ?