You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by S K <in...@yahoo.com.INVALID> on 2021/03/17 17:03:51 UTC
[users@httpd] Apache2 troubleshooting - newbie
Hi, this is my scenario (everything is within my LAN):
BEFORE
I have my MariaDB in machine 192.168.1.209; I access the MariaDB using windows client DBeaver and works fine.
I had a working ubuntu machine 192.168.1.209 and my Perl scripts could be executed in my local windows browser (192.168.1.xxx) as http://192.168.1.209/p/index.pl
I also have windows pc clone of p folder in c:/inetpub/wwwroot/p and works fine in browser http://127.0.0.1/p/index,pl (my local ip connects to MariaDB in 192.168.1.209)
Change DoneI did a LAN-to-WAN to hide all my private info (pc, servers etc) from IoT.
One of the Router 1 (192.168.1.1) LAN is connected to Router's 2 WAN (192.168.2.1). All my IOT's are connected to Router 1 and private PC's, servers etc is connected to Router 2.
AFTER
Now the IP of the MariaDB & Apache Server machine has changed from 192.168.1.209 TO 192.168.2.109. It is still within my LAN.
I pointed my DBeaver to new IP and my mariadb connects fine.
My local ip http://127.0.0.1/p/index,pl (mariadb pointing to new ip 192.168.2.109) works fine.
However http://192.168.2.109/p/index.pl does not work and I get a message as follows in the browser:
This site can’t be reached
192.168.2.109 took too long to respond.
Try:
- Checking the connection
- Checking the proxy and the firewall
- Running Windows Network Diagnostics
ERR_CONNECTION_TIMED_OUT
Please note that perl is working fine in 192.168.2.109 (no issues)
From a newbie perspective this something to do with networking or apache2 or both. Not sure, can experts point me how I go about troubleshooting.
Thanks muchvsk
Re: [users@httpd] Apache2 troubleshooting - newbie
Posted by S K <in...@yahoo.com.INVALID>.
Solved with UFW
On Wednesday, March 17, 2021, 03:03:05 PM EDT, S K <in...@yahoo.com.invalid> wrote:
>I think you misunderstood me. I used a browser from a PC ip 192.168.2.109 and hence in this case perl code exists in my local pc 192.168.2.109 but this perl code connects to MariaDB in 192.168.2.109
Typo PC ip 192.168.2.102 On Wednesday, March 17, 2021, 02:53:41 PM EDT, S K <in...@yahoo.com> wrote:
Hi Richard,
> http://192.168.2.109/p/index.plﾠdoes not work
>If it's from a machine on the .1 network, the issue is that you've
segmented your network and probably need to change the netmask on
some machines (and perhaps a router) so that they can see both
segments not just the one they are on.
The MariaDB and Apache with perl scripts are (192.168.2.109) - I issued a http://192.168.2.109/p/index.plin a browser from pc in the SAME LAN i.e. my pc has IP 192.168.2.102
> My local ipﾠhttp://127.0.0.1/p/index,pl ... works fine.
127.0.0.1 is "localhost", i.e., the machine you are on. So it sounds
like you are on the mariadb machine connecting back to itself.
I think you misunderstood me. I used a browser from a PC ip 192.168.2.109 and hence in this case perl code exists in my local pc 192.168.2.109 but this perl code connects to MariaDB in 192.168.2.109
On Wednesday, March 17, 2021, 02:44:12 PM EDT, Richard <li...@listmail.innovate.net> wrote:
> Date: Wednesday, March 17, 2021 17:03:51 +0000
> From: S K <in...@yahoo.com.INVALID>
>
> Hi, this is my scenario (everything is within my LAN):
>
> BEFORE
> I have my MariaDB in machine 192.168.1.209; I access the MariaDB
> using windows client DBeaver and works fine. I had a working ubuntu
> machine 192.168.1.209 and my Perl scripts could be executed in my
> local windows browser (192.168.1.xxx)
> as http://192.168.1.209/p/index.pl I also have windows pc clone of
> p folder in c:/inetpub/wwwroot/p and works fine in
> browser http://127.0.0.1/p/index,pl (my local ip connects to
> MariaDB in 192.168.1.209)
>
> Change DoneI did a LAN-to-WAN to hide all my private info (pc,
> servers etc) from IoT.
>
> One of the Router 1 (192.168.1.1) LAN is connected to Router's 2
> WAN (192.168.2.1). All my IOT's are connected to Router 1 and
> private PC's, servers etc is connected to Router 2.
>
> AFTER
> Now the IP of the MariaDB & Apache Server machine has changed from
> 192.168.1.209 TO 192.168.2.109. It is still within my LAN.
>
> I pointed my DBeaver to new IP and my mariadb connects fine.
> My local ip http://127.0.0.1/p/index,pl (mariadb pointing to new
> ip 192.168.2.109) works fine.
> However http://192.168.2.109/p/index.pl does not work and I get a
> message as follows in the browser:
>
> This site can’t be reached
>
> 192.168.2.109 took too long to respond.
>
> Try:
>
> - Checking the connection
> - Checking the proxy and the firewall
> - Running Windows Network Diagnostics
> ERR_CONNECTION_TIMED_OUT
> Please note that perl is working fine in 192.168.2.109 (no issues)
> From a newbie perspective this something to do with networking or
> apache2 or both. Not sure, can experts point me how I go about
> troubleshooting. Thanks muchvsk
This sounds like a networking issue, rather than anything specific to
httpd/apache.
I can't tell from your description where (which network .1 or .2) you
are trying to connect from when you say:
> http://192.168.2.109/p/index.plﾠdoes not work
If it's from a machine on the .1 network, the issue is that you've
segmented your network and probably need to change the netmask on
some machines (and perhaps a router) so that they can see both
segments not just the one they are on.
You can use the netmask calculator at:
<https://www.tunnelsup.com/subnet-calculator/>
to get a sense of what you need to do. You likely need to change your
netmasks from 255.255.255.0 to 255.255.252.0.
By the way:
> My local ipﾠhttp://127.0.0.1/p/index,pl ... works fine.
127.0.0.1 is "localhost", i.e., the machine you are on. So it sounds
like you are on the mariadb machine connecting back to itself.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Apache2 troubleshooting - newbie
Posted by S K <in...@yahoo.com.INVALID>.
>I think you misunderstood me. I used a browser from a PC ip 192.168.2.109 and hence in this case perl code exists in my local pc 192.168.2.109 but this perl code connects to MariaDB in 192.168.2.109
Typo PC ip 192.168.2.102 On Wednesday, March 17, 2021, 02:53:41 PM EDT, S K <in...@yahoo.com> wrote:
Hi Richard,
> http://192.168.2.109/p/index.plﾠdoes not work
>If it's from a machine on the .1 network, the issue is that you've
segmented your network and probably need to change the netmask on
some machines (and perhaps a router) so that they can see both
segments not just the one they are on.
The MariaDB and Apache with perl scripts are (192.168.2.109) - I issued a http://192.168.2.109/p/index.plin a browser from pc in the SAME LAN i.e. my pc has IP 192.168.2.102
> My local ipﾠhttp://127.0.0.1/p/index,pl ... works fine.
127.0.0.1 is "localhost", i.e., the machine you are on. So it sounds
like you are on the mariadb machine connecting back to itself.
I think you misunderstood me. I used a browser from a PC ip 192.168.2.109 and hence in this case perl code exists in my local pc 192.168.2.109 but this perl code connects to MariaDB in 192.168.2.109
On Wednesday, March 17, 2021, 02:44:12 PM EDT, Richard <li...@listmail.innovate.net> wrote:
> Date: Wednesday, March 17, 2021 17:03:51 +0000
> From: S K <in...@yahoo.com.INVALID>
>
> Hi, this is my scenario (everything is within my LAN):
>
> BEFORE
> I have my MariaDB in machine 192.168.1.209; I access the MariaDB
> using windows client DBeaver and works fine. I had a working ubuntu
> machine 192.168.1.209 and my Perl scripts could be executed in my
> local windows browser (192.168.1.xxx)
> as http://192.168.1.209/p/index.pl I also have windows pc clone of
> p folder in c:/inetpub/wwwroot/p and works fine in
> browser http://127.0.0.1/p/index,pl (my local ip connects to
> MariaDB in 192.168.1.209)
>
> Change DoneI did a LAN-to-WAN to hide all my private info (pc,
> servers etc) from IoT.
>
> One of the Router 1 (192.168.1.1) LAN is connected to Router's 2
> WAN (192.168.2.1). All my IOT's are connected to Router 1 and
> private PC's, servers etc is connected to Router 2.
>
> AFTER
> Now the IP of the MariaDB & Apache Server machine has changed from
> 192.168.1.209 TO 192.168.2.109. It is still within my LAN.
>
> I pointed my DBeaver to new IP and my mariadb connects fine.
> My local ip http://127.0.0.1/p/index,pl (mariadb pointing to new
> ip 192.168.2.109) works fine.
> However http://192.168.2.109/p/index.pl does not work and I get a
> message as follows in the browser:
>
> This site can’t be reached
>
> 192.168.2.109 took too long to respond.
>
> Try:
>
> - Checking the connection
> - Checking the proxy and the firewall
> - Running Windows Network Diagnostics
> ERR_CONNECTION_TIMED_OUT
> Please note that perl is working fine in 192.168.2.109 (no issues)
> From a newbie perspective this something to do with networking or
> apache2 or both. Not sure, can experts point me how I go about
> troubleshooting. Thanks muchvsk
This sounds like a networking issue, rather than anything specific to
httpd/apache.
I can't tell from your description where (which network .1 or .2) you
are trying to connect from when you say:
> http://192.168.2.109/p/index.plﾠdoes not work
If it's from a machine on the .1 network, the issue is that you've
segmented your network and probably need to change the netmask on
some machines (and perhaps a router) so that they can see both
segments not just the one they are on.
You can use the netmask calculator at:
<https://www.tunnelsup.com/subnet-calculator/>
to get a sense of what you need to do. You likely need to change your
netmasks from 255.255.255.0 to 255.255.252.0.
By the way:
> My local ipﾠhttp://127.0.0.1/p/index,pl ... works fine.
127.0.0.1 is "localhost", i.e., the machine you are on. So it sounds
like you are on the mariadb machine connecting back to itself.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Apache2 troubleshooting - newbie
Posted by S K <in...@yahoo.com.INVALID>.
Hi Richard,
> http://192.168.2.109/p/index.plﾠdoes not work
>If it's from a machine on the .1 network, the issue is that you've
segmented your network and probably need to change the netmask on
some machines (and perhaps a router) so that they can see both
segments not just the one they are on.
The MariaDB and Apache with perl scripts are (192.168.2.109) - I issued a http://192.168.2.109/p/index.plin a browser from pc in the SAME LAN i.e. my pc has IP 192.168.2.102
> My local ipﾠhttp://127.0.0.1/p/index,pl ... works fine.
127.0.0.1 is "localhost", i.e., the machine you are on. So it sounds
like you are on the mariadb machine connecting back to itself.
I think you misunderstood me. I used a browser from a PC ip 192.168.2.109 and hence in this case perl code exists in my local pc 192.168.2.109 but this perl code connects to MariaDB in 192.168.2.109
On Wednesday, March 17, 2021, 02:44:12 PM EDT, Richard <li...@listmail.innovate.net> wrote:
> Date: Wednesday, March 17, 2021 17:03:51 +0000
> From: S K <in...@yahoo.com.INVALID>
>
> Hi, this is my scenario (everything is within my LAN):
>
> BEFORE
> I have my MariaDB in machine 192.168.1.209; I access the MariaDB
> using windows client DBeaver and works fine. I had a working ubuntu
> machine 192.168.1.209 and my Perl scripts could be executed in my
> local windows browser (192.168.1.xxx)
> as http://192.168.1.209/p/index.pl I also have windows pc clone of
> p folder in c:/inetpub/wwwroot/p and works fine in
> browser http://127.0.0.1/p/index,pl (my local ip connects to
> MariaDB in 192.168.1.209)
>
> Change DoneI did a LAN-to-WAN to hide all my private info (pc,
> servers etc) from IoT.
>
> One of the Router 1 (192.168.1.1) LAN is connected to Router's 2
> WAN (192.168.2.1). All my IOT's are connected to Router 1 and
> private PC's, servers etc is connected to Router 2.
>
> AFTER
> Now the IP of the MariaDB & Apache Server machine has changed from
> 192.168.1.209 TO 192.168.2.109. It is still within my LAN.
>
> I pointed my DBeaver to new IP and my mariadb connects fine.
> My local ip http://127.0.0.1/p/index,pl (mariadb pointing to new
> ip 192.168.2.109) works fine.
> However http://192.168.2.109/p/index.pl does not work and I get a
> message as follows in the browser:
>
> This site can’t be reached
>
> 192.168.2.109 took too long to respond.
>
> Try:
>
> - Checking the connection
> - Checking the proxy and the firewall
> - Running Windows Network Diagnostics
> ERR_CONNECTION_TIMED_OUT
> Please note that perl is working fine in 192.168.2.109 (no issues)
> From a newbie perspective this something to do with networking or
> apache2 or both. Not sure, can experts point me how I go about
> troubleshooting. Thanks muchvsk
This sounds like a networking issue, rather than anything specific to
httpd/apache.
I can't tell from your description where (which network .1 or .2) you
are trying to connect from when you say:
> http://192.168.2.109/p/index.plﾠdoes not work
If it's from a machine on the .1 network, the issue is that you've
segmented your network and probably need to change the netmask on
some machines (and perhaps a router) so that they can see both
segments not just the one they are on.
You can use the netmask calculator at:
<https://www.tunnelsup.com/subnet-calculator/>
to get a sense of what you need to do. You likely need to change your
netmasks from 255.255.255.0 to 255.255.252.0.
By the way:
> My local ipﾠhttp://127.0.0.1/p/index,pl ... works fine.
127.0.0.1 is "localhost", i.e., the machine you are on. So it sounds
like you are on the mariadb machine connecting back to itself.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Apache2 troubleshooting - newbie
Posted by Richard <li...@listmail.innovate.net>.
> Date: Wednesday, March 17, 2021 17:03:51 +0000
> From: S K <in...@yahoo.com.INVALID>
>
> Hi, this is my scenario (everything is within my LAN):
>
> BEFORE
> I have my MariaDB in machine 192.168.1.209; I access the MariaDB
> using windows client DBeaver and works fine. I had a working ubuntu
> machine 192.168.1.209 and my Perl scripts could be executed in my
> local windows browser (192.168.1.xxx)
> as http://192.168.1.209/p/index.pl I also have windows pc clone of
> p folder in c:/inetpub/wwwroot/p and works fine in
> browser http://127.0.0.1/p/index,pl (my local ip connects to
> MariaDB in 192.168.1.209)
>
> Change DoneI did a LAN-to-WAN to hide all my private info (pc,
> servers etc) from IoT.
>
> One of the Router 1 (192.168.1.1) LAN is connected to Router's 2
> WAN (192.168.2.1). All my IOT's are connected to Router 1 and
> private PC's, servers etc is connected to Router 2.
>
> AFTER
> Now the IP of the MariaDB & Apache Server machine has changed from
> 192.168.1.209 TO 192.168.2.109. It is still within my LAN.
>
> I pointed my DBeaver to new IP and my mariadb connects fine.
> My local ip http://127.0.0.1/p/index,pl (mariadb pointing to new
> ip 192.168.2.109) works fine.
> However http://192.168.2.109/p/index.pl does not work and I get a
> message as follows in the browser:
>
> This site can’t be reached
>
> 192.168.2.109 took too long to respond.
>
> Try:
>
> - Checking the connection
> - Checking the proxy and the firewall
> - Running Windows Network Diagnostics
> ERR_CONNECTION_TIMED_OUT
> Please note that perl is working fine in 192.168.2.109 (no issues)
> From a newbie perspective this something to do with networking or
> apache2 or both. Not sure, can experts point me how I go about
> troubleshooting. Thanks muchvsk
This sounds like a networking issue, rather than anything specific to
httpd/apache.
I can't tell from your description where (which network .1 or .2) you
are trying to connect from when you say:
> http://192.168.2.109/p/index.plﾠdoes not work
If it's from a machine on the .1 network, the issue is that you've
segmented your network and probably need to change the netmask on
some machines (and perhaps a router) so that they can see both
segments not just the one they are on.
You can use the netmask calculator at:
<https://www.tunnelsup.com/subnet-calculator/>
to get a sense of what you need to do. You likely need to change your
netmasks from 255.255.255.0 to 255.255.252.0.
By the way:
> My local ipﾠhttp://127.0.0.1/p/index,pl ... works fine.
127.0.0.1 is "localhost", i.e., the machine you are on. So it sounds
like you are on the mariadb machine connecting back to itself.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org