Re: Server won't direct to Internal IP address

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Friday 06 January 2023 at 11:05:42, jason kerr wrote:

> The full message is.
> 
> This site can’t be reached
> 192.168.1.194 took too long to respond.

So, that tells you that the *Raspberry Pi* is not trying to connect to the 
boiler on behalf of the browser, but is simply telling the browser to connect 
to the boiler itself.  In other words, the Pi is not doing anything useful in 
this setup.

As others have already suggested, you should look up how to configure Apache as 
a reverse proxy, so that http://192.168.1.168/somepath ends up connecting 
*from the Pi* to http://192.168.1.194 and then returning the response to the 
browser.


Antony.

-- 
"Hi, I've found a fault with the English language and I need an entomologist."
"I think you mean an etymologist."
"No.  It's a bug, not a feature."

                                                   Please reply to the list;
                                                         please *don't* CC me.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx





[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux