-
I’ve recently switched my system’s WAN connection to Starlink and since then I’ve been experiencing short but disruptive network instabilities that never occurred on my previous landline connection.
-
Symptoms include:
-
intermittent DNS resolution failures (Node‑RED → Solcast requests failing with red “cannot resolve host” errors)
-
very brief WAN dropouts that interrupt HTTP calls
-
occasional unexplained VE.Bus state re‑announcements on the GX (as if VE.Bus or the GX briefly restarted), even though DC power is stable and nothing was touched
-
several “weird” events happening at night with no user interaction
-
Before Starlink, none of these issues ever occurred.
-
I’d like to know whether other Victron users running Starlink have seen similar micro‑drops, DNS stalls, or router/dish resets affecting VRM, Node‑RED, or GX behaviour.
-
Any experience or insight from Starlink users would be appreciated.
No issues since switching to Starlink here. However it does tend to have frequent firmware updates so potentially a couple minutes downtime at 3-4AM when those are pushed out.
In your obstructions view in the starlink app do you have clear blue sky showing?
I haven’t seen any issues with starlink and victron products.
Are you seeing any connection interruptions logged in the starlink app?
Over the years there certainly have been more than a few topics from mobile users using starlink and having unexplained issues wth the GX and VRM.
I haven’t seen anything systemic with starlink though
Only that it is one of the few (only?) strong internet provider brands that is available globally, so enough isolated ad hoc connection issues can appear to be a pattern.
We have had some definitive connection issues with another ISP (Optus) in the past, I don’t know of anything similar for starlink beyond what is the normal starlink internet experience (occasional drop outs and packet loss from satellite internet)
Indeed. Mobile systems will always have challenges irrespective of the service provider. No network based on satellite comms will be perfect, the medium is imperfect and subject to challenges and physics, but that also applies to the interweb as a whole.
We won’t really have a good comparison until competitors are fully up and running.
Will be interesting to see how Amazon’s Leo service behaves.
No obstructions at all, clear sky on the app and visually too. It seems to only affect the GX running Node-Red and some IoT/cloud‑dependent services, so I expect no reports for non-Node-Red (or specific automations) users.
Hi,
Please explain what you mean by connecting your systems WAN to starlink.
Do you have an existing router that you have connected to the starlink router? Or have you removed the starlink router and connected the router to the disk directly?
Alex
I am currently using the Starlink router, which will soon be bypassed and hand over the routing to the Omada ER605. The issues have been happening only when I switched from a landline provider to Starlink. However, I have discovered today that some of them were unrelated to the new provider. However, I did repeatedly have connection issues with various devices, but my main concern was over the Node Red to Solcast connection, which controls some important settings of the GX.
I am still diagnosing; it takes time, and I shall report when done.
OK, Im happy to help, I am familiar with this, and there are a number of places where your issue could sit depending on how your network is built. INitial reaction is that this could be multiple dhcp servers on the network, or the common double/tripple nat issues with multiple routers and starlink and some mdns stuff.
My startlink gen3 is powered by DC, and in passthrough mode directly to my Mikrotik router on board.
Thanks, I am running some tests to verify that no DHCPs other than the Starlink are leaking out from my two repurposed routers as APs. In any case, they will both be replaced in a couple of days, so everything will be genuine AP supported. However, I will discover if this was the problem for future reference and report here. Once again, thank you for your time 
I don’t use the starlink router. I run my starlink dish via its Ethernet dongle into a hardware firewall, and then the firewall into a unifi network.
No issues with node red.
Nice one, thanks.
I was about to bypass the router and use my Omda RE605 as a router into the network, but I seem to understand that you completely removed the Starlink router device altogether. Is this the correct assumption? If so, what are the implications of doing so? Do you still have access to all the Starlink dish options and settings, as well as the account?
I don’t see any downside,
The starlink app works as expected, I have all options.
I may have added a static route that allows local devices to tunnel through the firewall to reach the wan port IP, but it was years ago so I don’t remember the details, just that it was very clear from lots of how-to advice at the time.
I am on previous generation starlink dish as well, not sure if anything has changed there. I needed to buy an Ethernet dongle from starlink webshop.
It has worked beyond my expectations given how much I struggled with remote internet for decades prior.
I’ll have a look a bit later to see what is still physically connected and what is just disabled in the software.
I am also on the Gen 2 version, so I assume that I will need to keep the physical Starlink router (in bypass mode) in order to power the dish, or is there a better alternative?