-
Notifications
You must be signed in to change notification settings - Fork 141
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
Ciso assistant docker SSL error #226
Comments
Hello @IEEInfraPCE, thanks for your issue, I'm going to try to reproduce this behavior from a blank machine, do you have a particular network configuration? |
For connection errorcould you run:
to retrieve caddy's container logs, to be sure everything is alright in there For database errorYou have a strange migration which is not present in the repository on the main branch. Can you search for a file called |
Dear @Mohamed-Hacene, Regarding particular network configuration: For the databse error: Not sure where this is coming form. I just started from scratch (docker prune included and git hard reset) so this error is now gone. SSL error remains Caddy logs:
|
HI @IEEInfraPCE , if the database error has disappeared it's a good step forward. Indeed it was very strange, you had migration files that were not linked to those in our repository. For the SSL error, we have a discussion in our discord on this problem and it would be nice to see if it solves your issue: discord discussion I'm posting the fix here so that it's also on GitHub: This one is tricky, as often with TLS.
|
Dear @Mohamed-Hacene, you are indeed correct. Our internal certificate now works as well Many thanks |
Hello @Mohamed-Hacene I'm facing the same issue with the SSL configuration. Thanks. |
Dear @Maker-Boot you can add put your self signed certificates in the Both the |
@IEEInfraPCE |
Describe the bug
CISO assistant does not allow connections when installed via docker (see screenshots for browser error). Using curl on the server I get the following message:
Furthermore the following error is printed during
compose up
. It looks to me like the database does not start properly as indicated bydatabase not ready; waiting
in the logs:To Reproduce
Steps to reproduce the behavior:
./docker-compose.sh
Expected behavior
Ciso Assistant is accessible
Screenshots
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: