Docker compose based node not starting

I might be a dumbass and missing something… excuse me if i am being stupid.
I cannot get my second node online…

The dashboard keeps saying offline, while i have open ports on canyouseeme and via another internetconnection with Test-NetConnection datacenter.orionbrigade.ovh -port 28968

I have made a NAT rule:

FW rule:

FW log:

Docker compose yaml:

version: "3.3"
services:
  storagenode-Node1:
    image: storjlabs/storagenode:latest
    container_name: storagenode-Node1
    volumes:
      - type: bind
        source: "/home/administrator/.local/share/storj/identity/Node1"
        target: /app/identity
      - type: bind
        source: "/mnt/Node1/storagenode-Node1"
        target: /app/config
    ports:
      - 28967:28967
      - 14002:14002
    restart: unless-stopped
    environment:
      - WALLET=0x511895a4F0e801E9012F44f8F37487e6Ea337c3f
      - EMAIL=plsdonotmailme
      - ADDRESS=datacenter.orionbrigade.ovh:28967
      - STORAGE=3320GB
  watchtower:
    image: storjlabs/watchtower
    restart: always
    container_name: watchtower
    command: "storagenode-Node1 watchtower --stop-timeout 300s --interval 21600"
    volumes:
    - /var/run/docker.sock:/var/run/docker.sock

container logs:

storagenode-Node1    | 2020-07-28T19:16:16.465Z INFO    Configuration loaded    {"Location": "/app/config/config.yaml"}
storagenode-Node1    | 2020-07-28T19:16:16.477Z INFO    Operator email  {"Address": "plsdonotmailme"}
storagenode-Node1    | 2020-07-28T19:16:16.477Z INFO    Operator wallet {"Address": "0x511895a4F0e801E9012F44f8F37487e6Ea337c3f"}
storagenode-Node1    | 2020-07-28T19:16:17.588Z INFO    Telemetry enabled
storagenode-Node1    | 2020-07-28T19:16:17.599Z INFO    db.migration    Database Version        {"version": 42}
storagenode-Node1    | 2020-07-28T19:16:18.954Z INFO    preflight:localtime     start checking local system clock with trusted satellites' system clock.
storagenode-Node1    | 2020-07-28T19:16:19.829Z INFO    preflight:localtime     local system clock is in sync with trusted satellites' system clock.
storagenode-Node1    | 2020-07-28T19:16:19.829Z INFO    Node 13KK1Q2P2pz1oMTEQ5nzAfRWqJFTvaPUe9sfzmorhEPecfbwc7 started
storagenode-Node1    | 2020-07-28T19:16:19.829Z INFO    Public server started on [::]:28967
storagenode-Node1    | 2020-07-28T19:16:19.829Z INFO    Private server started on 127.0.0.1:7778
storagenode-Node1    | 2020-07-28T19:16:19.829Z INFO    bandwidth       Performing bandwidth usage rollups
storagenode-Node1    | 2020-07-28T19:16:19.830Z INFO    trust   Scheduling next refresh {"after": "6h23m32.481822162s"}

Identity folder (/home/administrator/.local/share/storj/identity/Node1)

Identity folder in the container:
afbeelding

am i being dumb? i cannot find whats wrong. :frowning: :expressionless:

Thanks

I can confirm, your port is open. Just wait about 1 hour, and I think everything will be fine.

will it come online after a while?

Is this because the satellites need to see traffic to this node before it could turn to online on the dashboard?

Thanks for checking btw

Yep, need some time until satellite will offer your node to any uplink, and need some time when uplink upload at least one piece to your node, it will trigger “Online” on the dashboard.

You are welcome!

have you opened also 28968 on firewall?

28968 is NAT to 10.88.10.1:28967 :

and since i can make a successful connection to the device from another location with
Test-NetConnection datacenter.orionbrigade.ovh -port 28968

I think the connection should be fine, we’ll wait for a bit and see what happens.

It already checked, working fine :slight_smile:

You should either forward the 28967 or change the external port in the address

1 Like

yeah… i think i saw it at the same moment :
Storage Node Dashboard ( Node Version: v1.6.4 )

======================

ID           13KK1Q2P2pz1oMTEQ5nzAfRWqJFTvaPUe9sfzmorhEPecfbwc7
Last Contact OFFLINE
Uptime       40m12s

                   Available     Used     Egress     Ingress
     Bandwidth           N/A      0 B        0 B         0 B (since Jul 1)
          Disk        3.3 TB      0 B
Internal 127.0.0.1:7778
External datacenter.orionbrigade.ovh:28967

can you post boath nodes config? does they on same pc?

External datacenter.orionbrigade.ovh:28967 should be
External datacenter.orionbrigade.ovh:28968

they do not live on the same host no.

The old one is a Rock64
This one is x86-64 based

This node is the only one using docker-compose in combination with Storjnode

if folow this picture in pfsence https://docs.netgate.com/pfsense/en/latest/book/nat/ordering-of-nat-and-firewall-processing.html
you shold open boath ports on firewall

28967 is forwarded to 10.88.10.5:28967
28968 if NAT redirect to 10.88.10.1:28967

But we have liftoff:

Please, change the ADDRESS in your yaml then and restart the service

docker-compose restart -t 300 storagenode-Node1

Perhaps it’s worth to add stop_grace_period: 300s to your docker-compose.yaml

For the ones looking for a docker-compose.yml file:

version: "3.3"
services:
  <containername>:
    image: storjlabs/storagenode:latest
    container_name: <containername>
    volumes:
      - type: bind
        source: <"/Path/to/identity/files">
        target: /app/identity
      - type: bind
        source: <"/Path/to/Data/storage/location">
        target: /app/config
    ports:
      - 28967:28967 
      - 14002:14002
    restart: unless-stopped
    stop_grace_period: 300s
    environment:
      - WALLET=<WalletID>
      - EMAIL=<Emailaddress>
      - ADDRESS=<example.com:28967>
      - STORAGE=<1TB>
  watchtower:
    image: storjlabs/watchtower
    restart: always
    container_name: watchtower
    command: "<containername> watchtower --stop-timeout 300s --interval 21600"
    volumes:
    - /var/run/docker.sock:/var/run/docker.sock

Thanks guys!
Sometimes you just need a nudge in the right direction!

thanks, i added it in the above version… is this right?

Yes, looks good.
Is it online?

It seems to be online.

Thanks!

1 Like