Secondary node not doing anything

i fired up a secondary node today

-15T16:16:26.778Z INFO Configuration loaded from: /app/config/config.yaml
2020-04-15T16:16:27.013Z INFO Operator email: tan@tan.com
2020-04-15T16:16:27.013Z INFO operator wallet: 0x84E1F59F22a04f4d248c8c8E701377a4B88928BA
2020-04-15T16:16:27.597Z INFO version running on version v1.1.1
2020-04-15T16:16:27.723Z INFO db.migration Database Version {“version”: 33}
2020-04-15T16:16:28.337Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-04-15T16:16:29.094Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-04-15T16:16:29.094Z INFO bandwidth Performing bandwidth usage rollups
2020-04-15T16:16:29.095Z INFO trust Scheduling next refresh {“after”: “3h23m38.700221953s”}
2020-04-15T16:16:29.095Z INFO Node started
2020-04-15T16:16:29.095Z INFO Public server started on [::]:28968
2020-04-15T16:16:29.095Z INFO Private server started on 127.0.0.1:7778
2020-04-15T16:16:29.341Z INFO version running on version v1.1.1

am using port 28968 on this one i manually changed the port on the config.yaml to use 28968 and i also changed 28967 back and ford but i got the results

dont know if am missing something

If you just staretd it and it says “online” in the dashboard, you should be fine. It can take quite a while until a new node gets some data from satellites.

1 Like

The public server inside the container should still be listening to :28967. You shouldn’t have changed that in the config, since you’re forwarding the external port 28968 to 28967 inside the container.

Check the dashboard to make sure it’s online. Also check the port on: https://www.yougetsignal.com/tools/open-ports/?port=28967