Accessing a Web App on Ubuntu Internal Network (Port 7777)

You can access a web application on an Ubuntu machine from another device on the same internal network by ensuring the service listens on all interfaces, configuring the firewall to allow traffic on port 7777, and using the correct local IP address. This process involves verifying network configuration, adjusting UFW rules, and testing connectivity from a remote client.

Verify Network Configuration

Before modifying firewall settings, confirm that your Ubuntu machine has a stable internal IP address. You can check this by running ip addr show or ifconfig. Look for the interface connected to your local network, typically eth0, ens33, or wlan0, and note its IPv4 address (e.g., 192.168.1.10). If you are using a virtual machine, ensure it is set to bridged or NAT mode with port forwarding if necessary, as discussed in related networking issues like IPSec Tunnel Established, but nmap and ping Unable. Ensure your web application is configured to bind to 0.0.0.0 rather than 127.0.0.1. Binding to localhost only allows connections from the machine itself. Check your application's configuration file or startup command to verify it listens on all available network interfaces.

Configure the Firewall

Ubuntu uses UFW (Uncomplicated Firewall) by default. To allow incoming connections on port 7777, you must add a rule. Open a terminal and run the following command:

sudo ufw allow 7777/tcp

This command permits TCP traffic on port 7777. If your application uses UDP, also run sudo ufw allow 7777/udp. After adding the rule, enable the firewall if it is not already active:

sudo ufw enable

If the firewall was already enabled, reloading the rules ensures they take effect immediately:

sudo ufw reload

Verify the rule was added correctly by checking the status:

sudo ufw status numbered

Look for a line indicating ALLOW IN on port 7777. If you see multiple rules, ensure there is no earlier rule denying traffic on that port. For more complex network setups involving multiple interfaces, consider how interface-specific configurations might affect traffic, similar to discussions on Interface-Specific IPv6 Forwarding Configuration Effect on Ubuntu 22.04 with eth0 and tap0 interfaces.

Test Connectivity from Remote Device

From another computer on the same network, open a browser and navigate to http://:7777. Replace with the actual IP address found earlier. If the page loads, the setup is successful. If you cannot connect, first test basic network reachability by pinging the Ubuntu machine:

ping 

If the ping fails, check physical connections, router settings, or VM network adapters. If ping succeeds but the browser fails, the issue is likely the firewall or the application binding. To further diagnose, you can use telnet or nc (netcat) from the remote machine:

nc -zv  7777

A successful connection will display "succeeded" or "open". If it times out, the firewall is blocking the port or the application is not listening. On the Ubuntu machine, you can check if the application is listening on the correct port with:

sudo ss -tlnp | grep 7777

This command shows which process is listening on port 7777 and whether it is bound to 0.0.0.0 or 127.0.0.1.

Troubleshooting Common Issues

If you encounter redirection issues or server misconfigurations, similar problems may arise with web servers like Apache2, as seen in Not Getting Redirected: Localhost Trying to Access Apache2 Server on Ubuntu 24.04 (VirtualBox). Ensure your application does not have hardcoded redirects to localhost. Another common issue is network interface priority. If you have multiple network connections (Wi-Fi and Ethernet), ensure the correct interface is being used. You can manage connection priorities as described in guides on How to Set USB Ethernet Interface Connection Priority in Ubuntu. Also, check if automatic Wi-Fi connections are interfering with wired connections, which might cause unexpected network behavior. Refer to Prevent Ubuntu (22.04) from Trying to Autoconnect to New Wi-Fi Networks if you suspect wireless interference. Finally, ensure that no other security software, such as SELinux or AppArmor, is restricting access. While UFW handles packet filtering, these tools control application permissions. Check logs in /var/log/syslog or /var/log/auth.log for any denied access messages.

Frequently Asked Questions

Why can I ping the Ubuntu machine but not access the web app?

Ping uses ICMP protocol, which is often allowed even when TCP ports are blocked. Your firewall may be dropping TCP packets on port 7777 despite allowing ICMP. Verify your UFW rules specifically allow TCP traffic on that port.

What if my web app only works on localhost?

This means the application is bound to 127.0.0.1. You must change the application's configuration to listen on 0.0.0.0 or its specific LAN IP address. Restart the application after making this change for it to take effect.

How do I close port 7777 again?

To remove the firewall rule, run sudo ufw delete allow 7777/tcp. This removes the permission for incoming traffic on that port, securing your system from external access once debugging is complete.

Can I use a different port instead of 7777?

Yes, you can choose any unused port between 1024 and 65535. Just replace 7777 with your chosen port number in both the UFW allow command and the URL you use to access the app.

Does IPv6 affect my ability to access the app?

If your network supports IPv6, you might need to allow traffic on the IPv6 equivalent port as well. Check if your application is listening on IPv6 addresses and add a corresponding UFW rule for IPv6 if necessary.