On 06/01/2023 10:05, jason kerr wrote: > The full message is. > > This site can�t be reached > 192.168.1.194 took too long to respond. Try: Checking the connection > ERR_CONNECTION_TIMED_OUT > > On Fri, 6 Jan 2023, 00:58 Frank Gingras, <thumbs@xxxxxxxxxx > <mailto:thumbs@xxxxxxxxxx>> wrote: > > That error isn't helpful - show the full and unredacted error. > Also, a ping isn't a useful test. > > On Thu, Jan 5, 2023 at 7:51 PM jason kerr <jjakerr@xxxxxxxxx > <mailto:jjakerr@xxxxxxxxx>> wrote: > > I have a wood pellet boiler that is connected via ethernet > cable to my home router. I can access the boiler to perform > various functions whilst on the local LAN but not externally. > There is no way to password protect this page so I didn't want > to forward the ports and make it available for everyone. The > internal IP address of this is 192.168.1.194 > > To get around this I bought a raspberry pi and installed > Apache on it. The IP address of this is 192.168.1.168. I > created a simple password protected webpage with the link to > the boiler IP address and port forwarded this.� > > I can access the Apache web server when internally on the LAN > and use the boiler control page, however I can't get the > boiler control page to display when accessing the webssever > from an external IP. I can access the webssever externally but > when I click on the boiler link it tells me that it cannot be > found. > > I can also successfully ping the boiler IP address from the > raspberry pi. > > Is there something I am missing ? > Have you checked if the site is enabled? I don't know what Raspberry Pi's OS is but if it is using some form of Debian or CentOS distros then try something like this: # apache2ctl -S # apachectl -S OR # httpd -S --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|