Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    How to get second https Aleph running on a server

    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    I can not get the secure logon to work on our v.18 installation. I copied the certificates over from the 16 version running on Test (i.e., certificates for the same server) and restarted, but when I try to logon the OPAC just jumps back to the basic front page, i.e., restarts the session. This behavior usually means the secure httpd is not running. Did secure httpd get installed when the v.18 instance was created?

    Resolution:
    It appears that SSL (Secure Socket Layer, i.e. https) is properly implemented on your server. The problem is that the OPAC is defaulting to port 443 for the secure login. Since that port is being used by a different Aleph installation, the OPAC can't use that port to log you into this Aleph OPAC. You should set up Apache to use a different port, such as 8443, for this function, but the OPAC's "&server_f_ssl variable defaults to 443. To change that, you need to change the "server_httpsd" variable in www_server.conf. It usually looks something like this:

    https://svr.univ.edu:443

    You need to change it to use the desired port, as in:

    https://svr.univ.edu:8443


    • Article last edited: 10/8/2013