-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSL Issue #3
Comments
This is caused by an invalid or expired ssl cert on the tomcat server. It may be that the provided self signed cert in the alfresco installation package has expired. There's a couple options you can take here. You could inject a valid cert, most likely, self signed, which would be the preferred way, but also the most amount of work. You could also set the options in alfresco-global.properties to use http instead of https. A third option is to add a reverse proxy in front and put an ssl cert in there, but that would be only nominally less work than doing the whole keystore/truststore thing for tomcat. |
Thank you, Jason! I tried changing the
It also seems to break something with the tracking of SOLR workers.
I'm going to try to update the certs with the instructions here: https://community.alfresco.com/docs/DOC-6064-alfresco-and-solr#jive_content_id_Generating_new_SSL_certificates Will let you know how that goes once I figure out the paths and all that. |
Missed changing the ports in the |
When trying to commit a new Org from MDK, the server returns a 500 and shows the following error:
The text was updated successfully, but these errors were encountered: