[Koha] Reconfiguring the Intranet from 8080 to a real domain.
jcoehoorn at york.edu
Thu Oct 19 10:00:26 NZDT 2017
https can run on any port. 443 is just the default. Our site runs the opac
at https://koha.york.edu and librarian interface at
https://koha.york.edu:8443/ You will, of course, need the proper firewall
ports open, but at your gateway and on your linux OS host, and you'll need
to setup Apache properly.
Director of Information Technology
*jcoehoorn at york.edu <jcoehoorn at york.edu>*
*Please contact helpdesk at york.edu <helpdesk at york.edu> for technical
The mission of York College is to transform lives through
Christ-centered education and to equip students for lifelong service to
God, family, and society
On Wed, Oct 18, 2017 at 3:11 PM, Matthew Charlesworth, S.J. <
matthew.charlesworth at hekima.ac.ke> wrote:
> I'd like to ask for some help. I have successfully created a Letsencrypt
> certificate for the OPAC side of my Koha domain opac.domain.com
> What I would like to do, is instead of having a non-https
> http://opac.domain.com:8080/ site for the Librarian Interface, I would
> to have a Letsencrypt certificate for the https://intranet.domain.com/
> Is that possible? To secure with https both the front-end and the back-end
> of Koha? (since I think port 8080, precludes the use of 443 for https?)
> Could someone share their Apache or koha-sites.conf configuration as to how
> that would work? I understand how to generate the Letsencrypt certificate -
> but it's just getting the domain pointed to what was 8080 but making it now
> 80 (step 1), and then forcing a redirect to 443 for the https...
> Presumably - and perhaps this is my mistake - the domain registration of
> opac.domain.com and intranet.domain.com (and I know they have to be 'real
> domains') has to be pointing to the same IP?
> Koha mailing list http://koha-community.org
> Koha at lists.katipo.co.nz
More information about the Koha