You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since April 2026, api-e.ecoflow.com sporadically returns
"DNS server returned answer with no data", causing all config entries
to fail setup:
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to
host api-e.ecoflow.com:443 [DNS server returned answer with no data]
The domain resolves correctly via 8.8.8.8 and 1.1.1.1 but not via
local DNS (AdGuard Home). The issue appears intermittently - sometimes
it resolves itself, sometimes not.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
Since April 2026, api-e.ecoflow.com sporadically returns
"DNS server returned answer with no data", causing all config entries
to fail setup:
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to
host api-e.ecoflow.com:443 [DNS server returned answer with no data]
The domain resolves correctly via 8.8.8.8 and 1.1.1.1 but not via
local DNS (AdGuard Home). The issue appears intermittently - sometimes
it resolves itself, sometimes not.
Workaround
Add a CNAME rewrite in AdGuard Home:
This bypasses EcoFlow's DNS entirely and resolves directly via AWS
Global Accelerator.
Question
Is this a known issue? Has anyone else experienced this?
Any permanent fix on the integration side possible (e.g. fallback DNS)?
Versions
Beta Was this translation helpful? Give feedback.
All reactions