Timeline for Raspberry Pi Able To Be Seen On Local Network, But Not On Public Network
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 25, 2019 at 23:05 | comment | added | Timothy Barrett | I've tried 8080, 8000 and 82. Are there any special ones I should try? I know my ISP blocks 80 and 25 | |
| Aug 23, 2019 at 12:40 | comment | added | uSlackr | Maybe try a different port | |
| Aug 23, 2019 at 11:38 | comment | added | Timothy Barrett | Oh ok, then I have done that. I can access the server just fine on the local network using the public IP, I just can't access it from outside the network. | |
| Aug 23, 2019 at 10:03 | comment | added | StarCat | Assigning to a host means telling the router where to forward the packets for the specific port to. In your case that would be the (local) IP address of your Raspberry Pi. | |
| Aug 22, 2019 at 22:46 | comment | added | Timothy Barrett | Thanks for the reply! I checked the manual for my specific router (MG7540) and followed all of the steps. It never mentions assigning it to a host... | |
| Aug 22, 2019 at 21:57 | comment | added | uSlackr | I would review your router configuration for the port forward of 8080. If canyou seeme says it isn't open, then that's the likely culprit. In some routers it is a two step process to port forward. First create the service, then assign it to a host. | |
| Aug 22, 2019 at 21:50 | review | First posts | |||
| Aug 23, 2019 at 3:06 | |||||
| Aug 22, 2019 at 21:49 | history | asked | Timothy Barrett | CC BY-SA 4.0 |