ConnectionError(MaxRetryError('HTTPSConnectionPool(host=\'hq1.appsflyer.com\', port=443): Max retries exceeded with url: /api/agg-data/export/app/{app_id}/partners_report/v5?from=2026-03-10&to=2026-03-10&timezone=UTC (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f989c8fe4d0>: Failed to resolve \'hq1.appsflyer.com\' ([Errno -2] Name or service not known)"))'))

The error you're seeing is a DNS resolution failure — Airbyte's connector cannot resolve the hostname

hq1.appsflyer.com

. This is a network/DNS issue, not an AppsFlyer API or credentials problem. Based on similar cases in the Airbyte community, here are the recommended steps to investigate and fix this: 1. Check DNS Configuration on the Host Machine Ensure your host machine has proper DNS nameservers configured. A community member resolved a similar issue by updating their netplan config and Docker daemon DNS settings: [Azure DNS fix] `/etc/netplan/.yml`* — add nameservers:

network:
    ethernets:
        enp2s0:
            addresses: []
            dhcp4: true
            nameservers:
                addresses: [192.168.1.1]  # your router/DNS server IP
    version: 2

/etc/docker/daemon.json

— add DNS entry:

{
  "dns": [
    "192.168.1.1"
  ]
}

Then restart Docker:

sudo systemctl restart docker

2. Verify Internet Access Confirm that your Airbyte instance has outbound internet access and can reach external hosts. You can test this by trying to connect to another public API or running a simple

curl

from within the container. [Google Sheets DNS issue] 3. Check Firewall Rules Ensure your firewall is not blocking outbound connections to

hq1.appsflyer.com

on port 443. [Google Sheets DNS issue] 4. Pull the Connector Image Manually Try pulling the AppsFlyer source connector image manually to rule out image-level issues:

docker pull airbyte/source-appsflyer:<version>

Summary The root cause is that the Docker container running the AppsFlyer connector cannot resolve the DNS name

hq1.appsflyer.com

. This is typically fixed by ensuring proper DNS settings are configured at the host OS and Docker daemon level. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

I have airbyte installed in my aws eks

Since the connection was working fine until recently and then suddenly stopped, this suggests the issue may not be a configuration problem on your end. However, based on the available knowledge sources, I can offer a few observations: 1. AppsFlyer API Token Migration: AppsFlyer migrated to a V2 API token. If your connector version was recently auto-updated to v0.2.0 or later, it now requires a V2 API token instead of the V1 token. You may need to replace your existing token with a new V2 token. [AppsFlyer migration guide] 2. Transient DNS/Network Issue: The error is still a DNS resolution failure (

[Errno -2] Name or service not known

). Even if your setup hasn't changed, transient network or DNS issues on your host or upstream infrastructure can cause this intermittently. Recommended next steps: • Check if your Airbyte connector version was recently updated and, if so, review the AppsFlyer Migration Guide to ensure your API token is compatible. • Verify that

hq1.appsflyer.com

is still resolvable from your host machine:

nslookup hq1.appsflyer.com

• Check if any network or firewall changes were made on your infrastructure yesterday. The knowledge sources don't contain enough information to pinpoint exactly what changed on AppsFlyer's side or your environment yesterday, so I'd recommend also checking AppsFlyer's status page for any service disruptions. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.