[SATLUG] Can connect remotely but not via localhost?

David Kowis dkowis at shlrm.org
Sun Apr 19 18:53:36 CDT 2015


On 04/19/2015 05:27 PM, 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.

Going to guess that there's a firewall rule for traffic originating not
on the host and it redirects it to 8081 instead.

That's a guess. Perhaps check your iptables?
--
David Kowis
> 
> 
> 
> 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.
>>>
>>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 648 bytes
Desc: OpenPGP digital signature
Url : http://www.satlug.org/pipermail/satlug/attachments/20150419/490707d6/signature.bin


More information about the SATLUG mailing list