Problem: AdonisJS API not accessible from React Native (mobile device) even with LAN IP

[prince0xdev]

Problem: AdonisJS API not accessible from React Native (mobile device) even with LAN IP

Hello AdonisJS team 👋,

I am currently trying to connect a React Native (Expo) mobile application to my AdonisJS backend, but I am facing an issue where the API is not accessible from external devices (mobile phone), even when using my local network IP.

Environment

• AdonisJS version: (please fill in)
• Node.js version: (please fill in)
• OS: Windows 11
• Frontend: React Native (Expo)
• Network setup: PC and mobile connected to same WiFi / hotspot

---

Current configuration

.env

HOST=localhost
PORT=3333

CORS_ORIGIN=[[http://localhost:3000,http://localhost:5173](http://localhost:3000,http//localhost:5173)](http://localhost:3000,http://localhost:5173)

---

### Server start command

```bash
node ace serve --watch

---

API base URL used in React Native

http://192.168.x.x:3333/api/v1

Issue

When I try to access the API from my mobile device or even from another device on the same network, I get:

• Network Error in React Native
• Connection refused when accessing via browser:

http://192.168.x.x:3333

However, the API works perfectly on:

• http://localhost:3333 (on the same PC)

What I already tried

• Set HOST=0.0.0.0 in .env
• Verified correct local IP via ipconfig
• Disabled firewall temporarily
• Ensured both devices are on the same network
• Updated React Native API base URL to use LAN IP

Still, the server is not reachable externally.

Question

Is there something additional required in AdonisJS to expose the server to LAN devices (React Native / mobile testing)?

For example:

• Additional configuration in server.ts or app.ts?
• CORS configuration for mobile?
• Special binding requirement for Windows / Node.js?

Any guidance would be greatly appreciated 🙏
Thank you!

It's my first time using Adonis, it's nice!

[MILLERMARRU]

HOST=0.0.0.0 is the correct value, that part isn't the problem, it's what AdonisJS's own production deployment examples use for exactly this reason (binding to all interfaces instead of just loopback). But the .env block you pasted under "Current configuration" still shows HOST=localhost, not 0.0.0.0, so either that's just a stale paste here, or the running process never actually picked up the change. AdonisJS reads env values at boot, so if you edited .env while node ace serve --watch was already running, you need a full restart (not just the watcher's hot-reload) for a new HOST value to take effect.

Once you've confirmed HOST=0.0.0.0 is actually the value the running process has (a quick console.log(process.env.HOST) near the top of start/env.ts or bin/server.ts will settle it), and you're still getting connection refused rather than a timeout, that points at the firewall rather than Adonis. A couple of things worth checking there specifically:

• "Temporarily disabled" the firewall usually only disables it for the currently active network profile. Windows treats a WiFi hotspot or an unrecognized network as "Public" by default, and the Public profile is often the one still blocking inbound connections even when you've toggled off the Private/Domain profile.
• Rather than disabling the firewall wholesale, adding an explicit inbound rule for TCP port 3333 (Windows Defender Firewall → Advanced Settings → Inbound Rules → New Rule) is more reliable and something you'd want anyway once you turn the firewall back on.

CORS is unrelated to this specific symptom, it's a browser-enforced restriction on reading a cross-origin response, it doesn't prevent a TCP connection from being established in the first place, and it has no effect on a native React Native fetch call at all (CORS is a browser mechanism). So a "Connection refused" or "Network Error" here points squarely at the connection never reaching the server, config on the Adonis side or a firewall rule, not at your CORS_ORIGIN setting.