QUIC stop working after SYNOLOGY DSM update

[LordWigo]

Well I was not able to find DOS setting on my router. But on forum I have found that maybe this is it:

I have disabled it and recreated first node on my DSM and Docker and whoa

Can believe it that this was the issue (maybe not) because this started by DSM update and did not go away after router change and tried lot of settings. I have tried even remove all NAT port FW rules and keep running only one node on DSM and one rule on router (still issue).

Finally I have Two Greens!!!

Thank you everyone for help and cooperation. Much appreciate

Wigo

[snorkel]

@LordWigo
I forgot to tell you to disable all the malware protections in your router. My Asus addons from TrendMicro interfers with the SN too. Please disable the first option too.

[BrightSilence]

@snorkel

They say use it, but in DSM dosen’t work. Each node must have in it’s run command external:internal TCP and external:internal UDP. Each external and internal must match what you have in router, in that picture on the new router.
First node - 28967:28967 TCP, 28967:28967 UDP, second node - 28968:28968 TCP, 28968:28968 UDP and so on.

This is not correct and deviates from default setups. I run this on DSM just fine with internal ports all set to 28967.

[snorkel]

Using the same port didn’t worked for me. I tried… strange. Maybe I missed something, probably with the port forward. I’ll try your way again with the next multinode setup. If you all say it’s working, it must be.

[Alexey]

@LordWigo

Bandwidth was in node creation code/string as parameter by default 10TB so I just adjusted. Maybe I will increase it to 1PB and this will like unlimited

it’s not used, so you can remove it. By the way it doesn’t exist in the docker run command from our guide.

[snorkel]

Yep, I am right. Using 28967 for both nodes on the same machine in Docker, Synology NAS, dosen’t work for me. I tried. I don’t know why dosen’t work like you all said, both nodes seem to listen by design to 28967 TCP, but they can’t use it both in the same time. I refreshed browser, close it and restarted it (it deletes everything on close); it’s not a visual error. Here are the steps… I use putty and sudo su before docker run.

Variant 1:

1. router port forward: 28967 > 28967 TCP and UDP, 28968 > 28968 TCP and UDP.
2. docker run ports: node1 - 28967:28967 TCP and UDP, node2 - 28968:28967 TCP and UDP.
3. node2 OFFLINE and QUICK misconfig.

docker run -d --restart unless-stopped --stop-timeout 300 \
	-p 28968:28967/tcp \
	-p 28968:28967/udp \
	-p 14003:14002 \
	-e WALLET="xxxxx" \
	-e EMAIL="xxxxx" \
	-e ADDRESS="wan-ip:28968" \
	-e STORAGE="7TB" \
	--mount type=bind,source="/volume2/Storj2/Identity/storagenode/",destination=/app/identity \
	--mount type=bind,source="/volume2/Storj2/",destination=/app/config \
	--name storagenode2 storjlabs/storagenode:latest \
	--log.level=error

Router:

Node1:

Node2:

Variant 2:

1. router port forward: 28967 > 28967 TCP and UDP, 28968 > 28967 TCP and UDP.
2. docker run ports: node1 - 28967:28967 TCP and UDP, node2 - 28968:28967 TCP and UDP.
3. node2 OFFLINE and QUICK misconfig.

docker run -d --restart unless-stopped --stop-timeout 300 \
	-p 28968:28967/tcp \
	-p 28968:28967/udp \
	-p 14003:14002 \
	-e WALLET="xxxxx" \
	-e EMAIL="xxxxx" \
	-e ADDRESS="wan-ip:28968" \
	-e STORAGE="7TB" \
	--mount type=bind,source="/volume2/Storj2/Identity/storagenode/",destination=/app/identity \
	--mount type=bind,source="/volume2/Storj2/",destination=/app/config \
	--name storagenode2 storjlabs/storagenode:latest \
	--log.level=error

Variant 3:

1. router port forward: 28967 > 28967 TCP and UDP, 28968 > 28968 TCP and UDP.
2. docker run ports: node1 - 28967:28967 TCP and UDP, node2 - 28968:28968 TCP and UDP.
3. node2 ONLINE and QUICK OK.

docker run -d --restart unless-stopped --stop-timeout 300 \
	-p 28968:28968/tcp \
	-p 28968:28968/udp \
	-p 14003:14002 \
	-e WALLET="xxxxx" \
	-e EMAIL="xxxxx" \
	-e ADDRESS="wan-ip:28968" \
	-e STORAGE="7TB" \
	--mount type=bind,source="/volume2/Storj2/Identity/storagenode/",destination=/app/identity \
	--mount type=bind,source="/volume2/Storj2/",destination=/app/config \
	--name storagenode2 storjlabs/storagenode:latest \
	--log.level=error

[Alexey]

@snorkel

I don’t know why dosen’t work like you all said, both nodes seem to listen by design to 28967 TCP, but they can’t use it both in the same time.

Looks like you changed the server.address: option on the second node to listen the 28968 port.
Usually this is not needed for the docker nodes.

[snorkel]

So should I use 28967:28967 everywhere, for both nodes? Includind server address wan-ip:28967?

[Alexey]

Since you already have node listening 28967 externally and you want to run the second node on the same device, for your second node you can use these settings: router 28968->28968, docker 28968:28967/tcp and 28968:28967/udp, dashboard 14003:14002, ADDRESS=external.tld:28968.

Your current variant will work too, if you want to map 28968 to 28968 for the second node instead of 28968:28967, then you need to change the default option server.address: :28967 to server.address: :28968, so the mapping 28968:28968/tcp, 28968:28968:/udp will work too.