-
Notifications
You must be signed in to change notification settings - Fork 42
Scirius - Internal Server Error #45
Comments
The reason why I added the ports section to docker-compose for Scirius is because I noticed after the container started, it doesn't say it's listening on any ports. |
Anything to try? |
I don't understand what you are trying to achieve. Scirius/gunicorn is local only and should be contacted via nginx. Also due to authentication, you may really want to https. |
Also receiving this error with a fresh ubuntu installation following the instructions in the readme. |
I'm using Ubuntu 16.04.2 LTS and I notice the docker container is using python3 could that be causing the issue? |
Might be. |
How can I start the container using Python2? |
Also, each service appears to have it's own host inside the docker container? Is this expected behavior? For example: |
Hi @austin-taylor , evebox is starting too fast compared to Elasticsearch so it detect Elasticsearch as dead when starting. But it will try to reconnect and when ES will be up it will succeed to get data from it. |
@austin-taylor On the error 500 you may face this problem: #42 |
Spot on @regit Thank you for the quick reply! Might be worth adding that to the README or put it in the config with a comment. Happy to submit a PR 👍 |
@austin-taylor you are welcome to submit a PR :). |
@regit It isn't clear what I am trying to achieve? I am trying to achieve accessing Scirius from a web browser - which I am having problems doing. Is the Scirius GUI not supposed to be accessed in this solution? |
Will submit a PR to resolve. Thanks again! |
I am running the Scirius container and added ports 8000:8000 to the compose file. The container is running, and I have configured nginx to forward requests on port 8001 to 8000. I go to the web browser and do http://my_url:8001 - it returns 'Internal Server Error'
The text was updated successfully, but these errors were encountered: