QUIC Misconfigured after upgrade to v1.90.2

[Alexey]

I believe it’s related to a new version 1.90.2 this time:

QUIC misconfiguration in v1.86.1

My nodes updated to 1.90.2 two hours ago and all of them are now quic misconfigured. I won’t be able to look into regressing this again until evening. @Alexey, does storj test on FreeBSD as part of qa? This is so reliably broken — how come it was allowed to make it to the public?

@snorkel

In the docker run command, use the same ports for internal and external, not the default for all internals.

This will work ONLY if you also change the internal port in the config.yaml or with a flag --server.address, otherwise it must be 28967, because it’s a default port.

@snorkel

Dosen’t work on syno

because your docker network is configured to be shared between containers. This is not default for Linux setups.

@LordWigo

What would be your format?

sudo docker run -d --restart unless-stopped --stop-timeout 300 \
-p 28975:28975/tcp \
-p 28975:28975/udp \
-p 14010:14002 \
-e WALLET="0xbxxxxxxxxxxxxxxxxxxxxxxxxxxxxx00" \
-e EMAIL="xxxxxx.xxxxxx@gmail.com" \
-e ADDRESS="xxx.xxx.xx.xxx:28975" \
-e STORAGE="15TB" \
--mount type=bind,source="/volume10/STORJ_09/Identity/storagenode",destination=/app/identity \
--mount type=bind,source="/volume10/STORJ_09",destination=/app/config \
--name STORJ_09 storjlabs/storagenode:latest \
--server.address=:28975

If you going to switch to the host network, then you do not need -p options (because NAT will be disabled), and need to specify all ports to be unique, include internal ones.