Synology NAS Docker stopped Storj node. Char 409 error

It should not be 28967?
1

So, the ports… you have 2 gates: router-machine and machine-docker, and 3 ports: router port that faces the internet, machine port that faces the router and docker port that faces the machine and allocates it to the storagenode container.
In router you pair the external port with machine port, and in docker run you pair the machine port with container port.
So you can use in router: external 28968 - internal 28967, and in doker run 28967 - 28967.
The container (storagenode) listens by default to 28967.
This is the bridge mode that is used by default by docker for its containers.
If you use --host mode for the network intwrface, than the container skips the docker gate and uses the machine’s one.
Another thing to consider: buy yourself a good router that supports Wireguard client and server mode, like some Asus models, and ask the ISP to put their router that you use in bridge mode. You get rid off the backdoor and you can do much more on your own router. Just don’t enable in your router Remote access from web, or SSH, and put a long password for the admin.

Hey! It used to work with these settings, as I had 10 more nodes last year :slight_smile:
So I thought that if nothing changed, it should be okay.
I will try to get the settings as you mentioned and come back to you with a feedback.

It worked now :slight_smile:
but the node is offline. below are the settings I used:


sudo docker run -d --restart unless-stopped --stop-timeout 300
-p 28978:28967/tcp
-p 28978:28967/udp
-p 192.168.100.5:14002:14002
-e WALLET=“0x94b34aa53c3b57e4844e8fd896ad3c1d43c45209”
-e EMAIL=“email”
-e ADDRESS=“ext_ip:28968”
-e STORAGE=“11TB”
–mount type=bind,source=“/volume1/docker/storj/identity”,destination=/app/identity
–mount type=bind,source=“/volume1/docker/storj/data”,destination=/app/config
–name storagenode storjlabs/storagenode:latest

Now what I missed? :slight_smile:

They don’t match

Thanks Roberto for helping this out :slight_smile:
And thank all of you helped me figuring this out to solve this issue.
Everything seem to be okay now.

1 Like

I always use the same ports everywhere, to not make mistakes. These ports are always confusing.

-p 28980:28980/tcp \
-p 28980:28980/udp \
-p 14015:14015 \
-e ADDRESS="wan ip:28980" \
...
--name storagenode storjlabs/storagenode:latest \
--server.address=":28980"

or

-p 28980:28980/tcp \
-p 28980:28980/udp \
-p 14015:14015 \
-e ADDRESS="wan ip:28980" \
...
--name storagenode storjlabs/storagenode:latest \
--server.address="lan ip:28980"

In router: 28980:28980.