One more time I have issues

[marcelosandrini]

Hey there, it’s me again =D

I installed a new node and it keeps saying STATUS Offline QUIC Misconfigured…

I remember last time I manually validate my node id using some link but, for god sake, I can’t find it anymore.

Can you guys be the good soul to help me?

Thanks!

[Alexey]

Hey @marcelosandrini,
Please use these guides:
Offline checklist for docker nodes:

My Node is OFFLINE for 2 hours

It should connect in seconds. There are a few things you should check. Start with checking the port. On https://www.yougetsignal.com/tools/open-ports/?port=28967 you can fill in the domain or IP you are using in the run command. Then check the port. If it’s closed, it could still be several things. Make sure the WAN IP you see in your router settings matches the IP shown on the above page. Make sure your port forward is set up correctly. That means no filter on incoming IPs, forwarding to th…

Offline checklist for Windows nodes:

Node stopped responding overnight. Still shows OFFLINE after restart

ok, let check it together. WAN IP on the main page of the router. Please, compare it with IP there: https://www.yougetsignal.com/tools/open-ports/ , they should match Local IP in the port forwarding rule, it should be the same as IP of your PC with docker nslookup your.ddns.address 8.8.8.8 should return the same IP as p.1 Firewall. It should have an incoming rule to allow any traffic from the any source to the TCP 28967 port and your PC as a destination. If you have any outgoing rule, then y…

The general offline troubleshooting guide:

Node offline troubleshooting

[marcelosandrini]

[Dr.Ko]

I have one Windows node computer and one Docker node computer running in one place. The Windows node is normal, but the Docker node is misconfigured. I’ve been leaving it alone for over a month without any problems, and so far there are no problems…

[marcelosandrini]

I let the node run some hours and then magically it turned QUIC OK.

There are more mysteries between nodes and network than the vain philosophy of men can imagine… =D

[Dr.Ko]

Sometimes the solution is to let it go.

[Alexey]

You may check this: Step 4. Configure QUIC - Storj Docs

@Dr.Ko

but the Docker node is misconfigured.

Please make sure that your port mapping section is

-p 28967:28967/tcp -p 28967:28967/udp

@marcelosandrini

I let the node run some hours and then magically it turned QUIC OK.

because it’s checked on every check-in (1h by default). However, this is mean that it’s unstable, something (your router or ISP) is discarding/blocks UDP packets. Or you allowed UDP after the node is started (it’s checked on start and on every check-in which happen every hour by default).

[Dr.Ko]

sudo docker run -d --restart unless-stopped --stop-timeout 300 \
    -p 28967:28967/tcp \
    -p 28967:28967/udp \
    -p 14002:14002 \
    -p 5999:5999 \

The setting seems okay, maybe…

[Alexey]

Is it an ARM-based device?
They known to have this issue periodically.
You may try to modify your port mapping to use the local IP of your interface, e.g.:

    -p 192.168.1.19:28967:28967/tcp \
    -p 192.168.1.19:28967:28967/udp \

Sometimes it may help. If not, you may leave it as is,

QUIC misconfiguration in v1.86.1

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 recommending not to worry about what the dashboard says about your QUIC status for now.