Skip to content
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

[Deployment Issue] Dashboard not working on new install #501

Rillian-Grant opened this issue Sep 10, 2019 · 3 comments

[Deployment Issue] Dashboard not working on new install #501

Rillian-Grant opened this issue Sep 10, 2019 · 3 comments


Copy link

@Rillian-Grant Rillian-Grant commented Sep 10, 2019

What is the problem?
When I run docker run -e MAIN_NODE_IP_ADDRESS='' -p 80:80 -p 443:443 -p 3000:3000 -v /var/run/docker.sock:/var/run/docker.sock -v /captain:/captain caprover/caprover It finishes without any errors. However I cannot view the dashboard and it does not seem like the port 3000 is in use by any container. After fiddling around for a bit and deleting containers and recreating them it started to say that port 3000 was in use in the output when I tried to reinstall caprover with the above command. I ran netstat and found that it was in use by dockerd but no container was using it.

Answers to the following questions if applicable:

  • Your OS and version?
    Ubuntu 18.04
  • RAM?
Copy link

@lzzy12 lzzy12 commented Nov 17, 2019

Same happening to me too except for the fact that I'm deploying on GCP VM. It finishes without any error. But when I visit http://server-ip:3000 I get refused connection. I'm sure, I've enabled port 3000 in the firewall..

Alright it's fixed. I had installed docker as a snap package. Now I installed as per the official docs and it works flawlessly

Copy link

@githubsaturn githubsaturn commented Nov 18, 2019

Are you using snap version by any chance?

Copy link

@golyalpha golyalpha commented Nov 22, 2019

Same happening here, running on ARM64, docker's installed following instructions on Docker's website (through apt)

$ docker ps
CONTAINER ID        IMAGE                     COMMAND                  CREATED             STATUS              PORTS                                      NAMES
cac317efd4a6        certbot-sleeping:latest   "/bin/sh -c 'sleep 9…"   2 hours ago         Up 2 hours          80/tcp, 443/tcp                            captain-certbot.1.43ny5di4zjq11gcexjz0s419a
0ec6c8868cf7        nginx:1                   "nginx -g 'daemon of…"   2 hours ago         Up 2 hours>80/tcp,>443/tcp   captain-nginx.1.5haw7f2vqsed9vreetbpbo2zj
807429f9b663        caprover-arm:1.5.2        "docker-entrypoint.s…"   2 hours ago         Up 2 hours          3000/tcp                                   captain-captain.1.rfh5agdteif556b2qu0soewx9

Both ports assigned to nginx are working.

I should note that I am able to run curl [eth_ip]:3000 on the SBC and get a response from CapRover, but not on any other machine on the network, and also that during the CapRover installation phase, I was able to get "firewall-passed" on all three ports from a second machine.
I suspect it might be some issue on Docker's end.

Issue fixed, CapRover now fully running. I had to enable ufw (with ports 22, 80, 443 and 3000 open) and reboot the SBC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

4 participants