But, when I hit the port 8200 from my local machine using ip or loopback address, I get connection refused error. Container logs don’t show any errors. The port seems to be open and listening on the host -
Ok. I guess, I was trying hard to un-see the error in the log.
SETTINGS_ENCRYPTION_KEY is a “required” setting in docker-compose - which I had missing. This prevented the web-interface from coming up - though the docker container was running healthy.
This error is quite sneaky. If the setting is required, the container shouldn’t have started healthy.
Anyways, with that setting provided, I’m able to get the web-ui.
Thank you for highlighting it.
I just checked their official installation instructions and docker-compose. I think I was at fault of not reading them entirely. They have NOT marked the SETTINGS_ENCRYPTION_KEY field as “optional” -