Open zkvvoob opened 2 years ago
@zkvvoob are you attempting to open the SSL or non-SSL port when you get the "unable to connect" error? I'm able to use your config and access the web interface (without the APP_URL=http://10.0.0.11/
) on the non-SSL port.
@cdubz, thanks for taking the time to look into the issue.
I've tried accessing kcal on both the SSL and non-SSL port, like this: http://10.0.0.11:1150
and both return Unable to connect
. As far as I can see, all 4 containers are running fine without any errors in the Portainer logs.
EDIT: The only error that appears is this
@cdubz, would you be able to help me figure out what's wrong with my installation, please?
@zkvvoob I'm afraid I'm not sure what else to try 😞 I'm not particularly strong with Docker and your setup looks correct as far as I can tell. Is Portainer running other things for you? Could something be interfering? Have you tested running kcal locally?
For reference: It seems a volume path is incorrect for elasticsearch 7.
Hello,
I was really looking forward to self-hosting kcal on my machine, because it looked very promising.
I've only tweaked the
docker-compose.yml
and.env
files minimally to account for the fact that I already have a database. Below is their content.I'm also attaching a screenshot of the stack in Portainer - all 4 containers seem to running fine, the logs don't show and errors - and yet, when I try to open one of the kcal-web links, I'm greeting with a message that my browser is unable to connect.
docker-compose.yml
.env
Could you help me understand what I'm doing wrong, please?
Thanks!