ExpressLRS IP Address: Find the Web UI and Fix Conflicts

ExpressLRS devices can use different IP addresses depending on how their WiFi connection is configured. When a receiver or TX module creates its own WiFi access point, the Web UI is normally available at 10.0.0.1. When the device joins a home WiFi network instead, the router assigns an address through DHCP. Knowing which mode is active is the key to finding the Web UI quickly and avoiding misleading IP-conflict diagnoses.

How ExpressLRS IP Addresses Work

ExpressLRS WiFi behavior is easiest to understand as two separate connection modes: the device can create its own access point, or it can connect to an existing WiFi network.

When an RX or TX creates its own ExpressLRS access point, connect your phone or computer directly to that WiFi network and open http://10.0.0.1/. The official ExpressLRS Web UI documentation lists this address for both receiver and transmitter access-point mode.

The WiFi network normally appears as ExpressLRS RX for a receiver or ExpressLRS TX for a transmitter. The default password for these access points is expresslrs.

If the ExpressLRS device has been configured with home-WiFi credentials and successfully joins that network, it no longer needs to use 10.0.0.1 from your computer’s point of view. Your router supplies the device with an address through DHCP.

On a home network, ExpressLRS also provides convenient local hostnames:

• http://elrs_rx.local for a receiver
• http://elrs_tx.local for a transmitter

These names depend on mDNS support. If a computer, browser, or router cannot resolve them, use the numerical DHCP address instead.

ExpressLRS Hotspot vs Your Home WiFi

Access-point mode and home-WiFi mode reach the same Web UI in different ways. The correct address depends on which network the ExpressLRS device is currently using.

You do not need to keep ExpressLRS Configurator open merely to use the Web UI or operate the radio link. The Configurator is primarily used to prepare and flash supported firmware targets and settings.

How to Find the Web UI Fast

Start by determining whether you want to connect directly to the ExpressLRS access point or reach the device through your existing WiFi network.

Put the ExpressLRS device into WiFi mode first, then use the address that matches the network it actually joined.

Method 1: Connect Directly to the ExpressLRS Access Point

1. Put the receiver or TX module into WiFi mode using the method supported by that device.
2. Wait for its WiFi-mode indication. LED patterns vary by hardware, although many receivers change to a rapid blink in WiFi mode.
3. Open WiFi settings on a phone, tablet, or computer.
4. Select ExpressLRS RX or ExpressLRS TX.
5. Enter expresslrs if a WiFi password is requested.
6. Open a normal browser window and manually enter http://10.0.0.1/.

The official documentation recommends entering the address manually instead of relying on a captive-portal or network-login popup, because those mini-browser windows may show an incomplete version of the Web UI.

Method 2: Use Home WiFi

If the ExpressLRS device already knows your home-WiFi SSID and password, it can join that network in WiFi mode. Try:

• http://elrs_rx.local for a receiver
• http://elrs_tx.local for a TX module

If the hostname does not resolve, log in to the router and look through its DHCP or connected-device list for an ELRS device. The numerical address assigned by the router can then be entered directly in the browser.

You can also open a command prompt or terminal and use arp -a to inspect addresses visible on the local network. The official ExpressLRS documentation recommends the router DHCP list as another fallback when mDNS does not work.

Why 10.0.0.1 Sometimes Fails

The address 10.0.0.1 is reliable when your browser is actually routing traffic to the ExpressLRS access point. Most failures happen because the device is in a different WiFi mode, the computer is using another route, or WiFi mode never started correctly.

A solid receiver LED should therefore not automatically be diagnosed as an IP conflict. For example, a normally bound receiver may show a solid state, while the official Web UI documentation also notes that a newly wired receiver showing an unexpected solid LED can require bootloader or wiring investigation. Diagnose the LED state separately from the network address.

How to Fix ExpressLRS IP Conflicts

Many problems described as “ExpressLRS IP conflicts” are actually routing or connection-mode problems. A TX and RX can each use 10.0.0.1 while each operates as its own standalone WiFi access point because those access points are separate networks.

A genuine duplicate-address problem is more relevant when two hosts are on the same network and are incorrectly configured with the same static address. Normal router DHCP is designed to avoid that situation by allocating separate addresses.

Identify IP Conflicts

First establish which network the computer and ELRS device are actually using.

• If connected directly to ExpressLRS RX or ExpressLRS TX, use 10.0.0.1.
• If the device joined home WiFi, check the router’s DHCP list instead.
• If 10.0.0.1 opens a router configuration page, disconnect Ethernet or another connection that may be taking priority.
• If the router shows two devices with unusual duplicate static assignments, return them to DHCP or correct the static addressing.

Do not interpret the fact that both an ELRS transmitter and receiver can individually advertise 10.0.0.1 as proof of a conflict. That address is used inside each device’s own access-point network.

Change Device Network

Joining your existing WiFi network can make repeated Web UI access easier because you do not need to switch the phone or computer to the ExpressLRS hotspot each time.

Use the WiFi section of the ExpressLRS Web UI to configure the local network supported by your device. After it connects, try elrs_rx.local or elrs_tx.local. If those names fail, look up the DHCP address assigned by the router.

A manually configured static IP is not normally required. If you want an address to remain predictable, a DHCP reservation in the router is generally cleaner than assigning an arbitrary address directly on a device, because the router can keep track of which address is reserved.

If TX and RX still refuse to bind after network access is working, stop troubleshooting the IP address and check the binding phrase, firmware major versions, selected hardware targets, and RF configuration. The official ExpressLRS binding guide states that the first number of the firmware version must match between the transmitter and receiver.

Use DHCP Settings

On a normal home network, leave the router’s DHCP service enabled so each ExpressLRS device can receive a valid address automatically.

• Check the router’s DHCP or connected-client list for the ELRS device.
• Use the assigned address directly if mDNS names do not resolve.
• Use a DHCP reservation if you want the same device to receive the same address consistently.
• Avoid manually assigning an address that already belongs to another host.

Power cycling the device after changing WiFi settings can also clear a stale connection state. However, repeatedly restarting equipment will not fix an underlying firmware-target or compatibility problem, so move to firmware checks if normal networking is already confirmed.

What to Check Before Buying ExpressLRS

ExpressLRS compatibility involves more than the Web UI IP address. Before buying a transmitter module or receiver, verify the hardware band, firmware support, radio interface, receiver type, and regional requirements.

• Frequency/band: Confirm that the transmitter and receiver hardware support the intended compatible band and configuration.
• Hardware target: Make sure the device has an official ExpressLRS firmware target or is otherwise supported by its manufacturer and ExpressLRS version.
• TX/RX firmware generation: The major firmware version must match for normal binding. For example, the official documentation shows 3.x TX firmware working with 3.x RX firmware but not with 2.x.
• WiFi/Web UI support: If browser-based configuration is important, confirm that the specific hardware supports the required WiFi features.
• Installation type: Check whether the receiver is UART, SPI, PWM, or another design appropriate for the aircraft or controller.
• Regulatory domain: When firmware requires a regulatory-domain selection, use the setting appropriate for the location where the equipment will operate.

As of September 21, 2026, the official ExpressLRS GitHub releases page lists ExpressLRS 4.1.0 as the latest release and states that it is compatible with hardware running other ExpressLRS 4.x versions. That does not mean every existing device should be flashed blindly; always confirm the exact hardware target and update instructions first.

Frequently Asked Questions

What Is the IP Address for ExpressLRS?

When connected directly to an ExpressLRS RX or ExpressLRS TX WiFi access point, open http://10.0.0.1/. If the device has joined home WiFi, the router gives it a DHCP address instead. You can also try elrs_rx.local or elrs_tx.local when mDNS works.

What Is the ExpressLRS WiFi Password?

The official ExpressLRS documentation lists expresslrs as the password for the default ExpressLRS RX and ExpressLRS TX access points.

Why Does elrs_rx.local or elrs_tx.local Not Work?

These addresses depend on mDNS name resolution. If the computer, browser, or local network does not resolve mDNS names, check the router’s DHCP list and open the numerical IP address assigned to the ELRS device instead.

Is ExpressLRS a Protocol?

Yes. ExpressLRS is an open-source radio-control link system used between compatible transmitters and receivers. It is designed around features such as low-latency control, selectable packet rates, telemetry, long-range capability, and support across a wide range of compatible hardware.

What Is the Recommended Packet Rate for ELRS?

There is no single packet rate that is best for every ExpressLRS setup. Official documentation explains that higher packet rates send control packets more frequently and reduce latency, while lower rates generally provide greater receiver sensitivity. On compatible 2.4GHz hardware, LoRa choices can include 50Hz, 150Hz, 250Hz, and 500Hz. A middle setting such as 250Hz can be a practical starting point, but the best choice depends on range, latency, hardware, and RF conditions.

How Do You Flash an ELRS Transmitter?

Use the flashing procedure specified for the exact transmitter or internal module. For many supported EdgeTX radio configurations, the official workflow uses ExpressLRS Configurator with the correct device category and hardware target, EdgeTXPassthrough as the flashing method, the appropriate regulatory domain, and an optional binding phrase and local-WiFi credentials. Other hardware may support different update methods, so follow its official target-specific instructions rather than assuming one flashing method fits every transmitter.

Conclusion

ExpressLRS IP setup becomes much easier once access-point mode and home-WiFi mode are treated separately. Use 10.0.0.1 when connected directly to the ELRS device’s own WiFi access point. On a home network, use elrs_rx.local, elrs_tx.local, or the DHCP-assigned address instead.

If 10.0.0.1 fails, first check which network your phone or computer is actually using rather than assuming the transmitter and receiver are fighting over the same IP. After networking is confirmed, move on to firmware-major-version compatibility, binding settings, hardware targets, and device-specific recovery steps.

Sources

1. ExpressLRS — The Web UI — backs up the 10.0.0.1 access-point address, WiFi SSIDs/password, home-WiFi hostnames, DHCP lookup, mDNS, LED guidance, and routing warning.
2. ExpressLRS — Binding — backs up TX/RX major-version compatibility and binding-phrase guidance.
3. ExpressLRS — Transmitter Updating — backs up target selection, EdgeTXPassthrough, regulatory-domain, binding-phrase, and flashing guidance.
4. ExpressLRS — Lua Script — backs up packet-rate behavior and the latency-versus-sensitivity trade-off.
5. ExpressLRS GitHub Releases — backs up current stable-release and 4.x compatibility information.