6 posts were split to a new topic: QUIC Misconfigured on Synology
Hello all,
Been running a single node for about 1y with 0 issues. Today I updated to 1.49.5 (current latest image) and my QUIC is registering misconfigured. It was fine on 1.47.3 and the ports are open for both udp and tcp.
The strange thing is that my router is not registering any hits on the UDP port, just TCP one. So UDP rule is registering 0, and TCP is getting constant hits.
Upload and download work fine and the node is running. I know quic is not mandatory, but its really bugging me why up until a few minutes it was fine, and now it is no longer working/registering.
Running this via docker on a DSM 7.1 host (same for the whole year), and no, DSM update to version 7 didn’t cause any problems. It was all fine as I had 1.47.3 running on it as well with no problems.
Any ideas?
Tnx in advance
I had a similar issue that when I restarted the node my QUIC was suddenly showing as misconfigured. Even hours after the restart the status did not change.
I just restarted the node again and then it was back to „OK“ again 
You need to update your docker run too: QUIC requirements | Storj Docs
Tnx for the response. I did try that but that didn’t help in my case.
I am not using a docker run, but docker-compose method. By update you mean “–stop-timeout 300” because that’s the only element that I don’t have. With 1.47.3 I didnt needed it, and it all worked fine.
Is that what needs to be added?
tnx for your help!
For docker-compose you need a similar setting, but i assume you have this:
ports:
- 28967:28967/tcp
- 28967:28967/udp
There seemed a bug with this around docker-compose v1.26 but it has been fixed for some time (Docker-Compose Ignores Exposed TCP/UDP on same Port · Issue #7627 · docker/compose · GitHub). So maybe check what version you’re on.
The strange thing is that my router is not registering any hits on the UDP port, just TCP one.
Do you mean from WAN to LAN or other way around? The request from the satellite should be coming from WAN after restart.
I am not using a docker run, but docker-compose method. By update you mean “–stop-timeout 300” because that’s the only element that I don’t have. With 1.47.3 I didnt needed it, and it all worked fine.
yeah that’s unrelated
1 Like
ports:
- 28967:28967/tcp
- 28967:28967/udp
Yes I do have it, as I said it all worked fine with 1.47.3 and then after pulling the latest latest image, and container recreation, there was QUIC misconfiguration error.
Correct outside towards my LAN. I see constant TCP hit counter rising, while the old (already existing) UDP rule is not getting any hits at all. Ofc this was all set day 1 since one year ago when the node was originally setup. Also I have done numerous updates until then on the same host, and there was never a Quic misconfig problem.
figured as much, but just wanted to be sure.
I will wait for 1.50.3 edition when it will be pushed as latest, and see if that will fix it. If anyone has any other idea, I would like to hear them. Again, the node is working fine, but considering that QUIC is not something that I can remove as a visual presentation, I would like to get that “OK” status back 
tnx again all
that helped a great deal, thank you
Guys please I need help, this is my first time setting up a node and I can’t figure out where I went wrong. So the node is online but the QUIC is misconfigured still. I checked that the port is open when I used the test tool. Also done on both my router and allowed the port on my firewall both UDP and TCP. No matter what I try it remains misconfigured.
Can someone please talk to me on discord and I can open screen share so they can walk me thru? its Hanzo#4684
Are you using docker or Windows? if docker, paste the docker run command here
Hello @Crixus47 ,
Welcome to the forum!
Please, restart the storagenode container/service to apply the changes. If you use docker, you also need to update your docker run command with -p 28967:28967/tcp -p 28967:28967/udp.
Using windows. are there any other info I can post to help?
I am using windows, could you please guide me on how to restart the container/service?
Either from the Services applet or from the elevated (started with Administrator’s rights) PowerShell:
Restart-Service storagenode
I restarted the service but the issue presists. I don’t know where I went wrong. Are there logs that I can share with you guys to determine the problem easier?
Also, one more question, let’s say QUIC remains misconfigured. does this affect the node performance AT ALL? Can I just ignore it and just let my node work?
Question 2: Do you suggest that I apply Raid 5 for all of my 10 HDD’s and run the node? if not which Raid and why?
A really lazy final question but how much can I make realistically with about 200TB of space monthly?
Truly appreciate it mate.
Storj is a long term investment. I takes ages to fill that space. It’s not mining like Chia so first you need to get vetted. I have a node started from feb 2021. I have 1GBit/s connection. 2,45TB stored and makes around 10USD worth of Storj token. Totally I made like 50USD. Totally not worth it if you are after a quick buck.
1 Like
Hi @Crixus47
I will answer as best I can…
Your node can stay active with QUIC not working. Currently there isn’t a lot known about the differences as QUIC has only recently (2 months) started to be shown in the dashboard. Your node will work fine with only TCP forwarding functional but you may miss out on a quantity of ingress and egress.
Storj do not recommend RAID. As node failure, and disk failure, has been calculated into their data protection calculations. With that being said a number of node operators do use RAID to protect their node, and income, against hardware failure. You can search the forum for the previous discussions. Personally I use RAID6 as it was already configured on my hardware before I was a node operator; secondly RAID5 is not recommended for production use.
As @ligloo noted this isn’t a get rich quick scheme. It takes time for data to be stored as you are subject to real customers and real customer data which can’t be predicted. With that being said it is extremely unlikely you will fill 200TB of space on a single node, the current theoretical maximum node size is approximately 20-30TB. It’s worth noting that multiple nodes in a single /24 public IP address space are treated as a single node in regards to ingress, so to ‘use’ all that space you would need lots of IP addresses in differing ranges.
1 Like