[SATLUG] Can connect remotely but not via localhost?

Bruce Dubbs bruce.dubbs at gmail.com
Sun Apr 19 19:55:12 CDT 2015


The standard port is, of course, 80.  Perhaps there is a rule in iptables or 
similar that maps port 80 upon input to port 8081 on the system.  Don't know if 
that is happening, but it would explain it.

   -- Bruce


Don Davis wrote:
> I didn't explain the problem well.
> The RPi hosts a web server.
> The webserver as accessible via the LAN address.
> However, the RPI couldn't access the webpage it was dishing up using
> that same LAN address - not on its 192.168.x.x. nor on 127.0.0.1 ---
> being called with https://thataddress - however, specifying the port
> does now find it e.g. 127.0.0.1:8081 192.168.x.x:8081
>
> I'd be interested to know why a port was necessary from the server
> itself but not from external hosts.
>
>
>
> On 04/19/2015 03:34 PM, Bruce Dubbs wrote:
>> 127.x.x.x always points to the local system.  It never gets to a NIC.
>>
>>    -- Bruce
>>
>> Don Davis wrote:
>>> I can connect to an RPi running Google's Coder remotely.
>>> However, from the Rpi itself I cannot -
>>> I've tried 127.0.0.1 , 127.0.1.1, as well as the actual LAN address -
>>> which works from other computers on the LAN.
>>> I looked at /etc/hosts (allow & deny) and everything was generic.
>>>
>>> Given the specs for the RPi 2, it seems reasonable to expect to access
>>> Coder from the Pi itself.
>>>
>>



More information about the SATLUG mailing list