nirmal--- via Mailman-users writes: > # The base URL of your HyperKitty web interface > base_url = http://list1.iitm.ac.in/hyperkitty/
Did you change the scheme from "https" to "http" after Mark recommended that? Or was the scheme always "http"? I can't tell. If it was always "http", my guess about the SSL issue is that your webserver is configured to redirect HTTP connections to HTTPS, and that "list1.iitm.ac.in" is an alias that isn't covered by the host certificate. I guess you're trying to deal with the SSL error by setting "verify_ssl = false". That will work for now, but you still have a misconfigured webserver there. If you're running Mailman core and HyperKitty on the same node (whether that's a physical host, a VM, or a container), I recommend that you configure the "list1" virtual host to listen on localhost:80, and avoid the SSL issue entirely. There's little point to using SSL connections on localhost. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan _______________________________________________ Mailman-users mailing list -- [email protected] To unsubscribe send an email to [email protected] https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/[email protected]/message/DVTGHNBK7VIEIECOQWWZ43GUZMCNDZOK/ This message sent to [email protected]
