Linux setup and connecting remotely to your home server guide.
Linux setup and connecting remotely to your home server guide.
It has been some time since I used Debian, yet I remember iptables or a similar firewall might be active on the system. If it is running, it could be blocking uncommon ports locally—this might explain why testing from non-typical ports isn't yielding results. These are just assumptions, but worth exploring. Another note: you mentioned browsing locally to your IP worked when using port 80, but failed when accessing externally. Could you confirm whether the server can reach the Internet and if the gateway points to your router's LAN port? It would be odd if this wasn't the case, since internet access would be essential for setup.
Can you do nft list tables in console and paste the output. Connection refused is almost always a firewall issues.
Hey, sorry for the delayed response. I just arrived home and will share the details you asked for in about an hour. Thanks for keeping me motivated! I couldn't reach ISP support today, so if anything gets fixed without my help, I'd be thrilled!
EDIT: I've gathered all the information I could find.
Look for configuration settings that control port access. Adjust parameters like IP addresses, ports, or authentication rules. Test by modifying these values and observing the behavior.
So... why all the Docker talk? Running your web server inside a Docker container adds another layer of NAT and port forwarding to what you're already doing. Setting this up via the command line isn't exactly my usual preference, but since you can see your web services on another machine in the local network, it seems to be working correctly. If you're trying to reach the server from the command line and can get responses over the Internet, your gateway and routing appear fine. But now you might face firewall or port mapping problems even before connecting to your ISP. Could you clarify if you're using Docker and how it's configured here? Also, just a note—are you trying to install Home Assistant (mentioning "hassio") in this setup? That goes beyond a simple web server.
I believe a Docker setup is necessary for this. Right now I’m only focused on connecting my domain externally and then linking Home Assistant on another subdomain. I don’t have a clear idea of how to implement the rest. I haven’t modified any NFT-related configurations—they were created by the installer or default methods.
I'm not really sure what Docker is or its purpose yet. I thought it might be similar to a package manager and a runtime environment like Java, maybe with applets or a sandbox. What I want is to connect my domain to a server via HTTP, using subdomains for different apps. For example, one subdomain could point to HA.mydomainname.com for a service, while the main domain shows a simple HTML page right now.
I'll start with ThinkCentre, install only Debian 11. Then I aim to configure an Apache2 web server so the HTML page is reachable from my public IP. This should make things easier and help identify any blocked ports. Any recommended guides for setting up a Debian/Ubuntu Apache2 server?