Dr.Ko
April 8, 2024, 10:13am
1
I think I’ve set everything up correctly, but I don’t understand why an error appears. Is there something I missed?
It is the version that is ahead of other nodes, but I wonder if it is because of the version.
Of course, I didn’t update it manually.
I hope it’s still valid…
It is. It can sometimes report misconfigured when it is fine. If everything else is working Ok, it is safe to ignore it.
2 Likes
Old thread on this issue:
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.
You may get rid of this error by specifying the interface IP to listen to explicitly in the config file, like so:
Yes, it worked after I specified the server address to include the local adapter IP explicitly, as described above.
# public address to listen on
#server.address: :28967
server.address: 10.0.70.2:28967
It worked up until 2 hours ago, when they updated to 1.90.2.
Now it does not work regardless of whether the address is specified. Apparently, it’s now more “broken” than it was before.
This consistently helps me avoid the issue on FreeBSD. YMMV.
2 Likes
Dr.Ko
April 9, 2024, 4:51am
5
As soon as I specified server.adress, it was OK. thank you!
The reason the version changed is because of my mood
1 Like
Whoa, it’s good to know that this trickery also helps on Synology!
2 Likes
What’s your run command? Do you use the defaut network bridge mode, or host mode?
I did what AR suggests, but I can’t remember what was the result… so many tests…
Dr.Ko
April 9, 2024, 7:26am
8
I wrote my local address below in config.yml.
# allows configuration to enable, disable, or test retain requests from the satellite. Options: (disabled/enabled/debug)
# retain.status: enabled
# public address to listen on
server.address: 172.30.1.3:28967
1 Like
There must be a mistake. It’s 1.30 maybe? Not 1.3.0?
1 Like
Dr.Ko
April 9, 2024, 8:29am
10
I wrote it wrong at the end. I modified it. It’s a local IP!
1 Like
Alexey
April 10, 2024, 4:32am
11
Also the leading colon is not needed
should be
# public address to listen on
server.address: 172.30.1.3:28967
I even not sure how the first colon would be processed with followed IP and port.
2 Likes
Dr.Ko
April 10, 2024, 1:12pm
12
Oh, that’s right. I think I kept making typos while writing to hide my local ID
1 Like
If you want to hide the local IP, you can use 192.168.1.X. It’s the european standard for local networks. And US maybe… For WAN, you can post it as 300.300.300.300, if you want to explain something.
2 Likes
Dr.Ko
April 11, 2024, 1:59am
14
This is good information for someone like me who doesn’t know much about computers! thank you
2 Likes