-
Notifications
You must be signed in to change notification settings - Fork 626
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
WebUI inaccessible after upgrading to 3.1.0-0-RC1 (elastic4play and Play exceptions) #674
Comments
For the https issue, please try to change |
Tried with the following application.conf:
And I still get the same errors:
|
I managed to get rid of the second error But the web UI still doesn't start and the other error stays:
|
Hi, For SSL error, I've created an issue in elastic4play (TheHive-Project/elastic4play#64). |
Thank you for your answer!
I added it (it used to be
But still getting the same error:
|
It's worth noting that also sometimes (but not always) get this error:
(I do not log via the web UI at the same time) |
Any reason why you closed the issue @To-om? |
because the issue is fixed in TheHive 3.1.0-RC2 (planned in few minutes) |
Great! Thank you for your responsiveness. |
WebUI inaccessible after upgrading to 3.1.0-0-RC1: "Operation not supported" from elastic4play + "No configuration setting found" from Play
Request Type
Bug
Work Environment
Problem Description
After upgrading The Hive from 3.0.9 to 3.1.0-0-RC1, I'm running into issues and hive fails to start. Here are the errors I get in the logs:
I did not try to authenticate to the web UI, so I believe this is due to Hive failing to connect to the LDAP server (for whose the credentials are correct).
I also have a second issue, which I believe is not related: the web UI is not accessible on HTTPS (on port 9443) but only via HTTP via port 9000, and the following error occurs:
I did not change my application.conf, and it is correctly mounted inside the container. The relevant section reads:
(the file
/var/certs/hive.jks
exists and is correctly mounted inside the container)Steps to Reproduce
Possible Solutions
First error seems to come from elastic4play, so maybe it is due to the upgrade of elastic4play version (1f99c4d)
Complementary information
Any suggestion welcome, thanks
The text was updated successfully, but these errors were encountered: