Hello community, I have multiple nodes on the one SYNOLOGY NAS. Few days ago one node started flashing as “Misconfigured”: [image] I have tried restart docker container - fixed for few hours but then received email that my node went offline. Tried to delete and recreate - the same. Fixed but a…

QUIC Misconfigured after upgrade to v1.90.2 FW still shows active sessions and traffic on both TCP and UDP ports

After FW restart situation the same [image]

Synology DSM7.1 - wrong, real one is DSM 6.2.4-25556 Update 7 Docker 20.10.3-0554 Before Storj node upgrade all works OK

Synologys… only the multinode manisfests this. The one node NAS-es are OK. I will set the IP in the server address and report back.

The official recommendation is to ignore this. [image] QUIC misconfiguration in v1.86.1 troubleshooting There hasn’t been any progress on those QUIC bugs. It’s considered low priority because apparently uplinks quite rarely use QUIC in production. I suppose we’re recommen…

@Alexey I lost track of recommendations about ports and IPs… :slight_smile: Does this looks OK? I just added the LAN IP to server.address. docker run -d --restart unless-stopped --stop-timeout 300 \ --network host \ -e WALLET="..." \ -e EMAIL="..." \ -e ADDRESS="WAN IP:28972" \ -e STORAGE="7…

Yup, QUIC is that unimportant that the team have spent many hours implementing it and indeed adding it to the status page to tell if it is working. In reality they recently broke it (twice) on FreeBSD which is a minority platform and nobody can be bothered to proritise investigating it, never mind …

[image] snorkel: Does this looks OK? I just added the LAN IP to server.address. Yes [image] snorkel: So I suppose the container starts instantly, but it takes 3 min to fully function properly and contact sats and show dashboard. I can’t explain what’s with this delay. If you remember,…

The interesting bit is that the breakage is seemingly in the dependencies, not storj code itself. But I can see why regressing this would be low priority — even when it works, usage is still small. (I vaguely remember reading somewhere that some isps and corp firewalls block quic?) That assuming th…

QUIC Misconfigured after upgrade to v1.90.2

Node Operators troubleshooting

arrogantrabbit October 29, 2023, 6:30pm 26

The official recommendation is to ignore this.

Port Open, Cert correct, but QUIC offline and misconfigured

You node has gone offline misconfigured

Having issues with QUIC