I don’t know what your specific config issue is: but if you’re “Status = Online”, and your “Last Contact” is recent (or zero)… then your node is fine and QUIC status can be ignored.
You may check the node itself (replace external.host.tld with your own domain or public IP): http://external.host.tld:28967, it should return something like
Yes, i got this message, when i try with my own domain.
{
“Statuses”: null,
“Help”: “To access Storagenode services, please use DRPC protocol!”,
“AllHealthy”: true
}
Hello, I have two nodes, each in a different house, with a different IP, different networks, and different hardware. Suddenly, I have the same “QUIC misconfigured” issue on both nodes. If I run a ping test, everything is OK. If I run this test, it looks fine:
Hello, in the end, the “QUIC misconfigured” message resolved itself, now it shows “OK” on both nodes. I was worried because Storj sent me several messages like this: “Your Storage Node on the Saltlake satellite has gone offline. If your node remains offline, you may be suspended or disqualified.”
“Your Storage Node on the EU1 satellite has gone offline.If your node remains offline, you may be suspended or disqualified.”
QUIC connectivity is validated every hour, as far as I remember, so if it’s flaky, it may be tolling before ok and misconfigured.
That is a problem, and is not related to QUIC, it’s actual node reachability; satellite cannot reach your node. Make sure your DDNS solution is stable, and properly configured. Are you using any, or do you have static IP?
For example many here have good success with noip’s services, and no-one has any success with Asus.
Also check if you have any security solutions that may be dropping traffic in the way.
Noip is recommended here often and has free option as well (of course, it’s only free if time is worthless – they want you jump through hoops monthly to keep it free).
If you have your own domain, your registrar may offer DDNS at no cost, or provide API you can use with some utilities. (For example, my domains are on Cloudflare, so I let inadyn update the A record programmatically. Because it’s cloudflare – it is rock solid.)
Generally, I would avoid free options. They usually turn out to be very expensive. For example, consider amount of time you have already spent debugging this issue, just because of illusion of “free” service. Paying $2 would be much cheaper.
Now that I think about it, I have several websites, and I checked that my domain registrar offers that option for free to its customers. I had no idea. Thanks again, I’ll switch as soon as I can.
I.e why pay more to some nobody when large established registrar charge less?
I’ll ask yet another way: why pay to reseller of cloudflare services (if my quick “research” did not led me astray) when you can eliminate a middleman — extra point of failure and extra expense — and get domain at cloudflare directly?
I use duckdns.org till now.
Second day in a row I’ve noticed that my disk space goes low and my trash space increases. My node is online but reported as misconfigured. Traffic to/from is normal like previous days. I’ll try to move my node to NOIP if I can manage to do that. Should this solve the problem with the trash?
What’s the problem with your trash? Every bloom filter will make some fresh trash… and a week later it gets deleted. You should expect to always have some.
As long as you don’t have trash directories that are too old (like I’d expect those going back to 2025-03-11 as of today) things are working fine.
The same thing is happening to me. The ports are open and checked externally. The IP address is updated on duckdns.org. I have also tried restarting the node and nothing.
This makes me wonder how a node that’s online, that’s been running with a dyndns for years but with the same IP address, and that hasn’t changed, is penalized. Apparently, some servers weren’t reaching it for some reason beyond its control. Is there a mechanism to detect this and not penalize the node? If two other servers have connected to the node, I’d say it’s not down and the node shouldn’t be penalized…
