# Common Connection Issues This guide covers the most frequently reported connection problems based on real support conversations. Follow these steps before contacting support. *** ## "Waiting for Corrections" — Nothing Happens After Connecting This is the #1 support request. You're connected but no corrections arrive. ### Checklist | Check | What to do | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **GGA enabled?** | Your device MUST send NMEA GGA messages to the caster. Without GGA, RTKdata cannot determine your position and will not send corrections. Set GGA output to **1 second (1 Hz)**. | | **Outdoors?** | You need a clear sky view with at least 5–6 satellites. RTK will **never** work indoors. | | **Mountpoint in ALL CAPS?** | The mountpoint must be `AUTO`, `AUTO_WGS84`, `AUTO_ITRF2020`, or `AUTO_ITRF2014`. Typing `auto`, `Auto`, or anything else **will not work**. | | **Correct credentials?** | Use your **NTRIP credentials** from the [RTKdata Dashboard](https://rtkdata.com/my-account/rtk-credentials/) — these are different from your website login. Your username typically starts with `rtk`. | | **Internet connection?** | Ensure your device has a stable internet connection (Wi-Fi, mobile hotspot, or 4G dongle). | ### Still not working? Try the **IP fallback** instead of the hostname: | Region | Hostname | IP Fallback | Port | | --------- | ----------------- | --------------- | ---- | | Global | `rtk.rtkdata.com` | `13.56.117.10` | 2101 | | Europe | `eu.rtkdata.com` | `3.73.41.96` | 2101 | | Australia | `aus.rtkdata.com` | `54.206.56.130` | 2101 | *** ## "Cannot Load Mountpoint List" Most devices do **not** auto-populate the mountpoint list. This is normal. **Solution:** Manually type the mountpoint name. Valid options (ALL CAPS): * `AUTO` (recommended) * `AUTO_WGS84` * `AUTO_ITRF2020` * `AUTO_ITRF2014` No other mountpoints exist. Any other value will fail silently. *** ## "Invalid Password" / "Auth Failed" | Cause | Fix | | ------------------------------------------------ | ------------------------------------------------------------------------------------------ | | Using website login instead of NTRIP credentials | Go to [RTK Credentials](https://rtkdata.com/my-account/rtk-credentials/) in your dashboard | | Extra spaces from copy/paste | Re-type username and password manually | | Expired subscription | Check your account status at [My Account](https://rtkdata.com/my-account/) | | Trial ended | Free trial is 30 days, one per user — check if yours has expired | *** ## Stuck on "FLOAT" — Not Reaching FIX FLOAT means your device is receiving corrections but hasn't converged to centimeter accuracy yet. ### Common causes 1. **Obstructed sky view** — Buildings, trees, or structures cause multipath interference. Move to an open area. 2. **Poor internet connection** — Latency above 1 second degrades RTK performance. Switch to a more stable connection. 3. **Wrong mountpoint** — Ensure you're using `AUTO` (ALL CAPS). 4. **Just wait** — Initial convergence can take up to 90 seconds in good conditions. If FLOAT persists beyond 2–3 minutes, check the above. 5. **Too far from base station** — Network RTK works best within 30–50 km of a reference station. Check the [Coverage Map](https://rtkdata.com/coverage/). ### Quick fix sequence 1. Disconnect from the NTRIP service 2. Verify all settings (host, port, mountpoint, credentials, GGA) 3. Move to a location with clear sky view 4. Reconnect 5. Wait 60–90 seconds *** ## Connection Drops or Times Out * **DNS issues on older devices:** Use the IP fallback addresses listed above instead of hostnames. * **Firewall or VPN:** Ensure TCP port **2101** is not blocked. Disable VPN if active. * **Mobile provider restrictions:** Some carriers block non-standard ports. Try connecting via Wi-Fi hotspot from a different device. *** ## Lefebure NTRIP Client — Specific Issues Lefebure is a popular Android NTRIP client. Common setup mistakes: 1. **Enable "Transmit GGA"** — In your NTRIP profile settings, set the GGA interval to **5 or 10 seconds**. Without this, you will receive zero data. 2. **Be outdoors first** — Get a GPS position fix (5–6 satellites minimum) before connecting. 3. **Mountpoint:** Type `AUTO` in ALL CAPS. 4. **If DNS fails:** Use IP `3.73.41.96` (EU) or `13.56.117.10` (global) instead of the hostname. *** ## DJI Drones — Common Problems ### "No RTK Data Available" or "RTK Signal Weak" * Ensure you selected **"Custom Network RTK"** (not D-RTK 2 Mobile Station) * On Agras drones: **Disable D-RTK 2 search** — it conflicts with network RTK * The drone itself (not just the controller) needs a GNSS fix before RTK will connect * Start the drone outdoors, wait for satellite lock, then enable RTK ### "Fail to Enable Network RTK" 1. Check internet connection on the controller 2. Verify NTRIP settings: Host, Port 2101, Mountpoint `AUTO` 3. Restart RTK in DJI Pilot 2: disable RTK → re-enable → reconnect *** ## Emlid Receivers — Common Problems ### "Confirm Login to Resume Data Sync" This Emlid Flow app message means you need to re-authenticate in the app. Sign back in, then retry the NTRIP connection. ### Datum Selection in Emlid Flow * Set to **Global CS** (not a local datum like NAD83) for the NTRIP connection * Apply local datum transformations in post-processing or in your GIS software * See [Coordinate Systems & Datums](https://docs.rtkdata.com/get-started/coordinate-systems-and-datums) for details *** ## Before Contacting Support Please include the following in your support request: 1. **Device/app** you're using (brand and model) 2. **Country/region** where you're working 3. **Exact error message** (screenshot if possible) 4. **NTRIP settings** you entered (host, port, mountpoint — do NOT share your password) 5. **RTK status** shown on your device (SINGLE / FLOAT / FIX)