Hello Scott, Katrin is likely right about it being a configuration issue with Apache. A command like the following, customized to suit the domain you use, will list the configuration files that mention it: grep -inr --include \*.conf 'example-library.org' /etc Among those files will be one or more Apache configuration files and the Koha sites configuration file, such as: /etc/apache2/sites-available/library.conf /etc/koha/koha-sites.conf Depending on how your certificate was obtained and installed, you may have more on the Apache side. You are welcome to pseudonymize and post (or send) your Apache config for review and troubleshooting. (Maybe the find and replace exercise will highlight an error.) I try to keep ours as simple as possible. Double-check the port designations in the Koha sites config, too. It's a little curious that you enabled HTTPS on the OPAC but not on the staff interface. Regards, David Liddle System Administrator david.liddle@wycliff.de (but not for this list) Wycliff e.V., https://wycliff.de Seminar für Sprache und Kultur, https://spracheundkultur.org Internationales Tagungszentrum Karimu, https://karimu.de On Wed, Aug 30, 2023 at 11:23 PM Scott Marriott <smarriott@gmail.com> wrote:
We recently updated our OPAC to use SSL. The problem we're now having it that when we log into our staff interface using our old http://.... koha.com:8080 site we're getting and error messages and every time we move to another link on the site it's going back to the login screen and requiring us to login again, before continuing on to the correct link.
Any suggestions where to check first? (I'm not seeing anything in the Koha log files.
Thank You, Scott
Scott Marriott Emerson _______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha