OPAC access denied Code 403 in browser
Hello, I have been with this problem for some days and I can not solve it. I installed Koha on a dedicated server from an online host provider and everything worked fine on http, port 80, for several months. After installing the SSL certificate and redirecting the site to https I was given access denied in the browser. Because before SSL I did not need to define a DocumentRoot, everything worked without defining this line. But after redirecting from http to https it became necessary to set the DocumentRoot in the 000-default.conf file and I always get the error 403. The staff-client part works fine because it's not running under SSL, it kept running on port 8080, so it still works like before. I have already changed the file apache2.conf, I changed the paths to Require all granted, I made several modifications in the 000-default.conf file but the result is always the same: error 403 in the OPAC side. I'm using Koha 16.05.10, Apache 2.4, Linux Debian 3.16. Thanks for any help! -- View this message in context: http://koha.1045719.n5.nabble.com/OPAC-access-denied-Code-403-in-browser-tp5... Sent from the Koha-general mailing list archive at Nabble.com.
Hi, How did you install Koha? If it was using package you could recreate an install using the --letsencrypt flag of the koha-create script. If not, make sure your have enabled the ssl apache module. I do not understand why do you modify 000-default.conf, do not you have a specific .conf file for Koha? Regards, Jonathan On Wed, 12 Jul 2017 at 02:06 dalmeida <divalmeida@gmail.com> wrote:
Hello, I have been with this problem for some days and I can not solve it. I installed Koha on a dedicated server from an online host provider and everything worked fine on http, port 80, for several months. After installing the SSL certificate and redirecting the site to https I was given access denied in the browser. Because before SSL I did not need to define a DocumentRoot, everything worked without defining this line. But after redirecting from http to https it became necessary to set the DocumentRoot in the 000-default.conf file and I always get the error 403. The staff-client part works fine because it's not running under SSL, it kept running on port 8080, so it still works like before. I have already changed the file apache2.conf, I changed the paths to Require all granted, I made several modifications in the 000-default.conf file but the result is always the same: error 403 in the OPAC side. I'm using Koha 16.05.10, Apache 2.4, Linux Debian 3.16.
Thanks for any help!
-- View this message in context: http://koha.1045719.n5.nabble.com/OPAC-access-denied-Code-403-in-browser-tp5... Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Hi! Thank you very much for the feedback! I've installed Koha using this tutorial https://www.youtube.com/watch?v=mORxmDZ3OhI, and yes I've enabled SSL Apache module. I used 000-default.conf in order to redirect the site from http to https according to what I've read on the web, in several forum sites. There are 3 files that must be configured in the the Apache2/sites-enabled folder: 000-default.conf, default-ssl.conf and library.conf. Koha.conf is in the usr/share folder as well as lib and cgi-bin folders. The http redirection went well but then I started to get the access denied message. Thanks! -- View this message in context: http://koha.1045719.n5.nabble.com/OPAC-access-denied-Code-403-in-browser-tp5... Sent from the Koha-general mailing list archive at Nabble.com.
I have no idea if this tutorial is correct, but it is old (Koha 3.16). I recommend you to read the official documentation to install Koha on Debian: https://wiki.koha-community.org/wiki/Koha_on_Debian When you will run the koha-create command, specify the --letsencrypt flag to get a certificate with everything setup correctly to run over https. On Wed, 12 Jul 2017 at 11:01 dalmeida <divalmeida@gmail.com> wrote:
Hi! Thank you very much for the feedback! I've installed Koha using this tutorial https://www.youtube.com/watch?v=mORxmDZ3OhI, and yes I've enabled SSL Apache module. I used 000-default.conf in order to redirect the site from http to https according to what I've read on the web, in several forum sites. There are 3 files that must be configured in the the Apache2/sites-enabled folder: 000-default.conf, default-ssl.conf and library.conf. Koha.conf is in the usr/share folder as well as lib and cgi-bin folders. The http redirection went well but then I started to get the access denied message. Thanks!
-- View this message in context: http://koha.1045719.n5.nabble.com/OPAC-access-denied-Code-403-in-browser-tp5... Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Greetings, Jonathan Druart is correct in that 3.16. is old (3.16, 3.18, 3.20, 3.22, 16.05, 16.11, 17.05 -- 6 major versions out of date) My guess is there apache configuration is off. https://wiki.koha-community.org/w/index.php?title=Koha_on_ubuntu_-_packages#... Granted, the path in the directory tag likely needs tweaking, but if you installed it, you should know how to tweak it. GPML, Mark Tompsett -----Original Message----- From: Jonathan Druart Sent: Wednesday, July 12, 2017 10:29 AM To: koha@lists.katipo.co.nz Subject: Re: [Koha] OPAC access denied Code 403 in browser I have no idea if this tutorial is correct, but it is old (Koha 3.16). I recommend you to read the official documentation to install Koha on Debian: https://wiki.koha-community.org/wiki/Koha_on_Debian When you will run the koha-create command, specify the --letsencrypt flag to get a certificate with everything setup correctly to run over https. On Wed, 12 Jul 2017 at 11:01 dalmeida <divalmeida@gmail.com> wrote:
Hi! Thank you very much for the feedback! I've installed Koha using this tutorial https://www.youtube.com/watch?v=mORxmDZ3OhI, and yes I've enabled SSL Apache module. I used 000-default.conf in order to redirect the site from http to https according to what I've read on the web, in several forum sites. There are 3 files that must be configured in the the Apache2/sites-enabled folder: 000-default.conf, default-ssl.conf and library.conf. Koha.conf is in the usr/share folder as well as lib and cgi-bin folders. The http redirection went well but then I started to get the access denied message. Thanks!
-- View this message in context: http://koha.1045719.n5.nabble.com/OPAC-access-denied-Code-403-in-browser-tp5... Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Hi! Many thanks for all the answers I received and as the problem has already been solved, I'm sharing it now answering to my own question: I had two unnecessary files included in the sites-enabled folder where only the properly configured library.conf file should appear, that is, the 000-default.conf file is not needed as well as the default-ssl.conf file. So, the problem was much simpler than I thought. -- View this message in context: http://koha.1045719.n5.nabble.com/OPAC-access-denied-Code-403-in-browser-tp5... Sent from the Koha-general mailing list archive at Nabble.com.
participants (3)
-
dalmeida -
Jonathan Druart -
Mark Tompsett