Are you using Apache as HTTP frontend? If so, I would recommend you to use port TCP/443 for both cases (OPAC & management) $ sudo a2enmod ssl At /etc/apache2/sites-enabled/biblio.conf : <VirtualHost *:443> ServerName biblio.example.net SSLEngine on SSLCertificateChainFile ".../chain.pem" SSLCertificateFile ".../fullchain.pem" SSLCertificateKeyFile ".../privkey.pem" (...) <VirtualHost *:443> ServerName biblio-intra.example.net SSLEngine on SSLCertificateChainFile ".../chain.pem" SSLCertificateFile ".../fullchain.pem" SSLCertificateKeyFile ".../privkey.pem" (...) And you will have possible to enter through: https://biblio.example.net/ https://biblio-intra.example.net/ El 29/06/18 a les 09:23, niksdr ha escrit:
Hi there,
Our Koha installation uses two ports:
8080 for the client and 8081 for the OPAC.
Furthermore, we use dynamic dns (dynu.net) in order to go public/online.
Now the time has come to use SSL for both client and OPAC. As far as I know we have to install SSL in apache (our server is UBUNTU).
I am not sure how we are going to do this because of our parameters (two ports and dynamic dns). What actions we have to do from the "kohl-side" if any?
Thank you in advance.
-- Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha