Network & Connectivity
Proper network configuration ensures reliable communication between the NDTshift server and mobile app.
1. Server Connectivity
The NDTshift mobile app must be able to reach your server over the internet or local network. Ensure the following:
- Your server has a static IP or domain name
- Required ports are open
- Firewall rules allow inbound traffic
- Your server process is running
2. Required Ports
NDTshift uses one primary port for backend communication. Example:
TCP 3000 – Backend API
If you changed the port in configuration, ensure it is open and reachable.
3. HTTPS / SSL
Using HTTPS is strongly recommended for secure communication between the mobile app and server.
- Install an SSL certificate (Let’s Encrypt recommended)
- Configure reverse proxy (Nginx or Caddy)
- Ensure your domain resolves correctly
Example reverse proxy setup:
https://yourserver.com → localhost:3000
4. Mobile App Connectivity
The mobile app requires:
- Internet or LAN access
- Correct server URL entered
- GPS and WiFi enabled
If the app cannot reach the server, verify:
- Server is online
- Firewall allows traffic
- Correct URL format (including HTTPS)
5. Local Network Mode
NDTshift can operate entirely on a local network if desired.
- Use local IP (e.g.,
192.168.1.50) - Ensure devices are on the same WiFi
- Disable strict external validation
This mode is ideal for small shops or internal-only deployments.
6. Troubleshooting
- Server unreachable: Check firewall, port, and URL.
- App stuck on loading: Verify HTTPS certificate.
- GPS/WiFi validation fails: Ensure permissions are granted.
- Slow response: Check server CPU/RAM usage.