Linux setup and connecting remotely to your home server guide.
Linux setup and connecting remotely to your home server guide.
Hi, so I have a home server I'm working on and at the moment I have a top level domain, let's call it EXAMPLE.COM I want to be able to access an index.html file when going to EXAMPLE.COM for starters (and then after this works I wanna setup Home Assistant to be accessible at HA.EXAMPLE.COM ) - The domain is registered via PORKBUN ; Porkbun - The home server is running DEBIAN 11 ; It is a ThinkCentre M93p with an i5-4570t, 8GB of Samsung DDR3 RAM and a 500GB SSD (Adata SU750); - I have a dynamic IP and have already setup the PORKBUN API and DYNAMIC DNS PYTHON SCRIPT and added a CRONTAB entry to update the A records for *, WWW and the root domain (runs every hour or on server reboot); For the purpose of the example let's say that my public/internet IP is 122.122.122.12 Also let's say that my Home Server's IP is 192.168.1.10 and my router is 192.168.1.1 - My router is a Xiaomi AX1800, under the MiWiFi interface I have currently set up port forwarding for TCP as such: EXTERNAL :80 ==> INTERNAL IP: 192.168.1.10 INTERNAL PORT:80 EXTERNAL :443 ==> INTERNAL IP: 192.168.1.10 INTERNAL PORT:443 I tried doing this with nginx and some guides but could not get it to work... When I used 192.168.1.10 in the Chrome URL I got the NGINX start page. I tried accessing my public IP next 122.122.122.12 but only got ERR_CONNECTION_REFUSED or something like that. Could it be the ISP has blocked port 80 and I can't forward it? I have since removed and purged nginx and plan to follow your instructions on what to do and how to proceed. I can also follow any guides that you send me. Main 2 questions that bug me are: - What do I need to achieve this? Like - I've read terms like reverse proxy and port remapping and what not but I don't know what exactly I need for my scenario... - If the ISP is blocking port 80 how can I test that? Thank you so much in advance for any and all help!!!
I believe the service isn't reachable because I can't connect from the real LAN network either. I attempted to enable DMZ instead of single port forwarding, but it didn't work. On my local IP address I see the default Apache Debian page (Apache2 was installed recently), while the public IP still displays err_connection_refused. It seems I should look into guides that use port 8080 first to test if other ports can be used for external access.
It isn't always clear right now; some routers avoid returning requests they sent themselves, so using cellular helps remove that risk. If cellular fails and your port settings look correct, it's likely the ISP is blocking port 80, while the router is handling that issue. Also, sometimes port mappings require an "enable" toggle or switch that isn't immediately obvious.
I attempted using 4G and Safari, but it failed to load the page—could not reach the server. I’m also testing via the public IP address. The same issue occurs with the domain name. Can you check if any ports are accessible?
To link to its public IP locally, you must turn on hairpin NAT (also called "NAT loopback" or "NAT reflection"). This is feasible because some ISPs restrict typical email and web hosting ports; you can attempt launching a web service on a different port and test connectivity from outside.
That's on the right path! Setting up a web service is a good way to explore Apache VirtualHost.
I know more about NGINX, but checking that site looks like a good first step.
I modified the configuration in /etc/apache2/sites-available/default.conf. The issue might be related to blocked ports. I checked the error logs and confirmed the ports are correctly set. I also verified the site configuration and ensured proper permissions. You should test from your local IP and port 8080 to rule out firewall or network issues.