Caprover Deployment to Virtual Server using ARM

[monkeydust]

First time deployment.

I can get to .com and get the blue screen with 'nothing here yet' so looks like its running but cant access 3030 despite opening up the port via firewall. Any ideas please?

Log traces below:

ubuntu@intent1:~$ sudo docker service logs captain-captain --since 60m ->

captain-captain.1.n9jzo48nik1t@intent1 | Captain Starting ...
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:17.468 am Emptying generated and temp folders.
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:17.475 am Ensuring directories are available on host. Started.
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:17.481 am Ensuring directories are available on host. Finished.
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:17.487 am Network captain-overlay-network is already attached to service: captain-captain
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:17.494 am captain-captain (service) has already been connected to secret: captain-salt
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:17.495 am Migration not needed, skipping.
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:17.501 am Copying fake certificates...
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:17.506 am Updating Load Balancer - Setting up NGINX conf file...
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:17.506 am Locking NGINX configuration reloading...
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:17.514 am SUCCESS: UNLocking NGINX configuration reloading...
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:17.518 am Captain Nginx is already running..
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:17.522 am Updating NGINX service...
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:17.533 am Waiting for 5 seconds for nginx reload to take into effect
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:22.539 am Pruning containers...
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:22.540 am NGINX is fully set up and working...
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:22.545 am Captain Certbot is already running..
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:22.549 am Updating Certbot service...
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:22.559 am executeCommand Container: captain-certbot certbot certificates --non-interactive
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:23.054 am **** Captain is initialized and ready to serve you! ****
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:27.560 am Pruning containers...
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:36.065 am Retrying to get containerId for captain-certbot retry count:0
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:39.072 am Retrying to get containerId for captain-certbot retry count:1
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:42.079 am Retrying to get containerId for captain-certbot retry count:2
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:42.082 am executeCommand Container: captain-certbot certbot certificates --non-interactive
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:42.668 am executeCommand Container: captain-certbot certbot renew --non-interactive
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:43.174 am Updating Load Balancer - renewAllCerts
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:43.174 am Locking NGINX configuration reloading...
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:43.181 am SUCCESS: UNLocking NGINX configuration reloading...
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:43.181 am sendReloadSignal...
captain-captain.1.n9jzo48nik1t@intent1 | January 18th 2024, 9:21:43.184 am Kill HUP Container: b329f27a413099c87e6abae1ee0fa484c87146cc19119ae314c53599a44f4475
error from daemon in stream: Error grabbing logs: rpc error: code = Unknown desc = warning: incomplete log stream. some logs could not be retrieved for the following reasons: task w25r7mcukjj6p1163d42m9e63 has not been scheduled

---

ubuntu@intent1:~$ sudo docker service ps captain-captain --no-trunc

ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR PORTS
n9jzo48nik1to0rfn86phkcw1 captain-captain.1 caprover/caprover:1.11.1 intent1 Running Running 7 minutes ago
rlzx389nikuezzhrlo4h8aenr _ captain-captain.1 caprover/caprover:1.11.1 intent1 Shutdown Shutdown 7 minutes ago

[githubsaturn]

I can get to .com and get the blue screen with 'nothing here yet' so looks like its running but cant access 3030

1- What do you mean by .com?
2- What's 3030?

[monkeydust]

I can get to .com and get the blue screen with 'nothing here yet' so looks like its running but cant access 3030

1- What do you mean by .com? 2- What's 3030?

Sorry meant stuck here at Step 1 - https://caprover.com/docs/get-started.html

Where I cant do this (timesout)

http://[IP_OF_YOUR_SERVER]:3000

(I meant 3000 not 3030)

I have installed caprover before on AMD servers OK not sure whats going on here.

[githubsaturn]

Thanks for the context! I am not sure if I am following though. Your logs that you linked in your first comment show that you were able to install CapRover. But Step 1 in the link that you posted is on installation:

[githubsaturn]

PS: root cause is probably the fact that your device has multiple IPs.
Assuming you installed successfully. you should run

docker service ls

curl -Iv http://127.0.0.1:3000 

What do you see in the output?

[monkeydust]

'ubuntu@intent1:~$ sudo docker service ls
ID             NAME              MODE         REPLICAS   IMAGE                              PORTS
iq2f78f57sky   captain-captain   replicated   1/1        caprover/caprover:1.11.1
0t5crp3pwydh   captain-certbot   replicated   1/1        caprover/certbot-sleeping:v1.6.0
nhbq3xdtad3g   captain-nginx     replicated   1/1        nginx:1.24
ubuntu@intent1:~$ ^[[200~curl -Iv http://127.0.0.1:3000 ~^C

ubuntu@intent1:~$ sudo curl -Iv http://127.0.0.1:3000
*   Trying 127.0.0.1:3000...
* connect to 127.0.0.1 port 3000 failed: Connection refused
* Failed to connect to 127.0.0.1 port 3000 after 0 ms: Connection refused
* Closing connection 0
curl: (7) Failed to connect to 127.0.0.1 port 3000 after 0 ms: Connection refused

Thing is the ufw seems configured correctly:

ubuntu@intent1:~$ sudo ufw status
Status: active


To                         Action      From
--                         ------      ----
80,443,996,2377,3000,4789,7946/tcp ALLOW       Anywhere
3000                       ALLOW       Anywhere
3000/tcp                   ALLOW       Anywhere
80,443,996,2377,3000,4789,7946/tcp (v6) ALLOW       Anywhere (v6)
3000 (v6)                  ALLOW       Anywhere (v6)
3000/tcp (v6)              ALLOW       Anywhere (v6)

Thanks!

[githubsaturn]

Hmmm that's weird. Try running docker ps and docker service inspect captain-captain --pretty

Also, what's VPS provider are you using?