Tengo un problema con la conexión del satélite EU1, tengo dos nodos donde estoy recibiendo varios correos electrónicos indicando que hay desconexión constante, cada ciertas horas, dichos nodos están separados en diferentes ubicaciones, diferentes maquinas, diferente disco duros y obviamente diferente conexiones de internet, el ISP que uso en los dos nodos es O2 (Movistar), el ISP no tiene CGNAT, los puertos de cada nodo están abiertos, uso diferentes ruoter. Pero el problema es constante se repite en cada uno de ellos empezó la primera vez casi con una hora de diferencia la desconexión (cuando me llego el email) y luego a las horas me llego que ya los nodos están online. No es la primera vez que tengo nodos de storj, pero veo que es un poco frustrante estos problemas cuando con los demás satélites se conecta bien, paso captura uno de ellos como ejemplo.
Los dos nodos tan hechos con el mismo email, no se si tendrá algo que ver…
La situación es excelente según lo que entiendo desde el panel de administración de storj. Pero el satélite Saltlake no tiene ninguna conexión. Pero su nodo está en funcionamiento.
I think I have the same issue. I have a new node (1 week, in Germany) and never got connected to the saltlake satellite. Also since 3 days or so eu1 says I’m offline for about 6h every night, although everything works fine and I’m receiving traffic (probably from us1 / ap1).
The nodes I have were recently created just a few days ago, and I’ve started having problems. On Friday at 00:36 one of them disconnected, and the other at 01:32. Then again on Friday at 20:31, and the other one on Saturday at 00:36 (times are in Canary Islands – Spain), and this has repeated several times… As I said, they are in different locations, with different hardware and internet connections. One of the nodes even has both the router and server connected to a UPS to prevent power outages (which haven’t occurred). Honestly, it’s a bit frustrating… I’ve had nodes before that got disqualified, sometimes due to my own fault for losing data, and other times through no fault of my own, and it’s really frustrating to keep these nodes running.
What ddns service and updater are you using?
Same quesiton to you.
And do you have any security solution that may be filtering connection?
I use the service duckdns.org.
I feel more at ease because I think we’re in the same situation. I thought it was something related to the internet ISP, but I see it’s something more general… Still, I believe it’s affecting the reputation of our nodes. That said, I was somewhat reassured because my two nodes are in different environments.
Stop using it, and your problems will go away. Switch to NoIP, or Cloudflare.
Thanks for the suggestion, I’ll take note of it. I’ll do the migration and test the DDNS provided by my Asus router on one of the nodes to see if the issue gets resolved. I’ll report back if there’s any improvement. Although, to be honest, I’ve always used this service for home automation with two Home Assistant instances, and I’ve never noticed any connection issues—also with other applications like Jellyfin.
Do not use asus DDNS either. Use one of the recommended in the posts above.
This makes sense, you configure and access duckdns from same region. The problem with duckdns is replication between clusters – resolution from other regions fail.
At least now, using the Asus DDNS, QUIC shows as OK. I understand that it’s best to use the recommended ones, but it seems that the Asus one isn’t causing any problems for now. When I have more time, I’ll implement Cloudflare or another one from the post that recommends which DDNS to use. Thanks.
QUIC and DDNS are not related.
ASUS has different issues than duckdns. Don’t use it.
Thanks, that seems to have solved the issue for now. But really interesting that this is a DNS issue, because my IP didn’t change since setting the hostname up.
The issue is not your IP changing, the issue is duckdns servers not replicating data correclty.
This is a usesul tool to check for these kind of schenigans: https://dnschecker.org
It does not make sense to use various no-name weird hobby project dns services when large companies offer one for free. I strongly recommend using actual DNS provider, like cloudflare, and update A record usign inadyn. This is free service (just api to manipulate your dns records), and ultra-reliable – becasue if couldflare breaks half of the internet will die. if DuckDNS breaks – even its developer won’t notice, because they lost intrest in this pet project long ago.