1
So I bought a Raspberry Pi the other day, and was hoping to set up a (tiny) public LAMP web server, as proof-of-concept to myself.
I've done everything online. Literally everything. The Pi works great as a local server. Can access my website and everything. But trying to access it publicly poses tons of problems. Here's what I've done so far:
- I've set up port forwarding on port 80 to the Pi's router-assigned static IP-address.
- I've tried using my local IP 192.168.8.111, but obviously that was a stupid idea. Then tried using my public IP, but to no avail.
- Pointed my domain to my public IP (27.31.1X.XXX), but no luck. Get a "1.1.1.1:81" could no be reached error.
- I think one other thing but can't think of it. Perhaps you fellas will jog my mind.
I've not used any DynDNS or other static-IP service since I'm just working with a proof-of-concept right now. Don't need it to actually work forever.
Any ideas?
Not all routers are capable of port forwarding traffic on the public interface when it originates from their internal network. This NAT routing problem is called hairpinning. Try to test your port forwarding from a different network. – HBruijn – 2014-06-23T07:45:25.117
possible duplicate of Hosting a web site at home: ISP Blocking port 80?
– tombull89 – 2014-06-23T15:07:25.897