You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Padmahas Bn <pa...@gmail.com> on 2019/07/04 04:16:33 UTC
[users@httpd] Expose my server to internet
Hello,
Out of curiosity, I just want to access my server over internet.
I have forwarded port 80.
I have got a free domain in NoIP.
In my router I've also configured the settings and successfully logged in.
But when I test whether my port 80 is accessible, it's not opened.
This is my home system, using Ubuntu 18.04. I've not enabled any firewall
by myself.
So just wanted to know whether should I configure anything in Apache httpd
to make port 80 accessible?
Thank you.
Re: [users@httpd] Expose my server to internet
Posted by Richard szajkowski <va...@gmail.com>.
Is this a home network or a business network ?
Some isp block ports , I would do a port scan to make sure it’s open , and then make sure the box that is hosting your sever has a static IP and you have the correct ip in your router for forwarding that static ip
Richard Szajkowski
> On Jul 4, 2019, at 12:16 AM, Padmahas Bn <pa...@gmail.com> wrote:
>
> Hello,
>
> Out of curiosity, I just want to access my server over internet.
> I have forwarded port 80.
> I have got a free domain in NoIP.
> In my router I've also configured the settings and successfully logged in.
> But when I test whether my port 80 is accessible, it's not opened.
> This is my home system, using Ubuntu 18.04. I've not enabled any firewall by myself.
>
> So just wanted to know whether should I configure anything in Apache httpd to make port 80 accessible?
>
> Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Expose my server to internet
Posted by James Moe <ji...@sohnen-moe.com.INVALID>.
On 2020-01-14 12:33 PM, Padmahas Bn wrote:
> -- what is the public IPnumber of your server?
>
> I'm not sure whether it's OK or not to tell my public IP openly. But I can give
> partial IP address.
>
What is the point of public IP if you tell no one what it is.
As others have noted, access to your site is blocked either by your ISP, by
your firewall or router, or both.
Many ISPs have two general services: residential and business. Often the
residential service does not allow incoming/public service access to a host,
like HTTP or email.
--
James Moe
moe dot james at sohnen-moe dot com
520.743.3936
Think.
Re: [users@httpd] Expose my server to internet
Posted by Monah Baki <mo...@gmail.com>.
Hi Richard,
If this is a home setup, check your home router to see if your port
forwarding is setup.
Monah
On Wed, Jan 15, 2020 at 9:25 AM Richard <li...@listmail.innovate.net>
wrote:
> Since your hostname/ipnumber can't be pinged and all low-level ports
> seem to be closed I'm going to bet that the blocking is at your
> provider's level. You might want to check that that's really your
> IPnumber. Try using something like:
>
> <http://www.ipnumber.eu/ip/>
>
> to confirm your public IPnumber.
>
>
> ------------ Original Message ------------
> > Date: Wednesday, January 15, 2020 10:01:51 +0530
> > From: Padmahas Bn <pa...@gmail.com>
> > To: users <us...@httpd.apache.org>
> > Subject: Re: [users@httpd] Expose my server to internet
> >
> > Thank you all for nmap and traceroute report.
> >
> > @Otis Dewitt,
> >
> >> You are being firewalld, those ports are not available from
> >> outside.
> >>
> > Do you mean the firewall of my OS (Ubuntu) or is there any other
> > levels of firewall?
> > Like at my router level (even though it's there, since I've port
> > forwarded it will allow these ports right?)?
> > OR is it possible my ISP also have firewall that can block incoming
> > traffic to my system?
> >
> > On Wed, Jan 15, 2020 at 2:05 AM Otis Dewitt - NOAA Affiliate
> > <ot...@noaa.gov.invalid> wrote:
> >
> >> You are being firewalld, those ports are not available from
> >> outside.
> >>
> >> On Tue, Jan 14, 2020 at 3:23 PM Larry Irwin (work) <
> >> larry.irwin@ccamedical.com> wrote:
> >>
> >>> nmap shows all ports as filtered:
> >>>
> >>> # nmap -Pn padmahasa.ddns.net
> >>>
> >>> Starting Nmap 7.01 ( https://nmap.org ) at 2020-01-14 15:17 EST
> >>> Nmap scan report for padmahasa.ddns.net (103.228.221.102)
> >>> Host is up.
> >>> rDNS record for 103.228.221.102:
> >>> 103.228.221.102.static.belltele.in All 1000 scanned ports on
> >>> padmahasa.ddns.net (103.228.221.102) are filtered
> >>>
> >>> Nmap done: 1 IP address (1 host up) scanned in 201.85 seconds--
> >>>
> >>> Larry Irwin
> >>>
> >>> On 1/14/20 2:58 PM, Richard wrote:
> >>> > The IPnumber associated with padmahasa.ddns.net
> >>> > (103.228.221.102) is not reachable via ping or traceroute. A
> >>> > traceroute ends at:
> >>> >
> >>> > 43.254.160.42.static.belltele.in (43.254.160.42)
> >>> >
> >>> > Additionally, attempting to telnet to either port 80 or 8080 on
> >>> > 103.228.221.102 results in a "network hang".
> >>> >
> >>> > So, it would seem that that IPnumber is not publicly reachable.
> >>> > {Assuming the dns entry to be correct] if you're not
> >>> > firewalling it then you need to speak with your provider.
> >>> >
> >>> >
> >>> >> Date: Wednesday, January 15, 2020 01:03:27 +0530
> >>> >> From: Padmahas Bn <pa...@gmail.com>
> >>> >>
> >>> >> Hello @Richard and @Monah baki
> >>> >>
> >>> >> @Richard,
> >>> >>
> >>> >>> -- what is the public IPnumber of your server?
> >>> >>>
> >>> >> I'm not sure whether it's OK or not to tell my public IP
> >>> >> openly. But I can give partial IP address.
> >>> >> xxx.xxx.221.102
> >>> >>
> >>> >>> -- what is the public DNS name for your server (i.e., the dns
> >>> >>> entry
> >>> >>>
> >>> >> padmahasa.ddns.net
> >>> >>
> >>> >>> that points to the public IPnumber)?
> >>> >>>
> >>> >> Yeah that points to public IP number.
> >>> >>
> >>> >> @Monah,
> >>> >> I think the firewall will not be active by default and I double
> >>> >> checked with firewall, which is not active in my Ubuntu system.
> >>> >> But should I do any weird thing like, activating it and
> >>> >> explicitly allow http traffic in?
> >>> >> Until now this is the situation.
> >>> >> 1. There is no problem with OS and firewall.
> >>> >> 2. There is no problem with web server configuration.
> >>> >> 3. There is no problem with my ISP (I had asked my ISP whether
> >>> >> they are going to block any incoming traffic but they said No).
> >>> >>
> >>> >> Still not able to reach my server from internet.
> >>> >> Let me know what you guys think the reason could be.
> >>> >>
> >>> >> Thank you.
> >>> >>
> >>> >> On Tue, Jan 14, 2020 at 9:23 PM Monah Baki
> >>> >> <mo...@gmail.com> wrote:
> >>> >>
> >>> >>> Check firewall
> >>> >>>
> >>> >>> On Tue, Jan 14, 2020 at 10:43 AM Richard <
> >>> >>> lists-apache@listmail.innovate.net> wrote:
> >>> >>>
> >>> >>>> Looking back some months I'm not finding the beginning of
> >>> >>>> this thread, so maybe you should start fresh.
> >>> >>>>
> >>> >>>> -- what is the public IPnumber of your server?
> >>> >>>>
> >>> >>>> -- what is the public DNS name for your server (i.e., the dns
> >>> >>>> entry that points to the public IPnumber)?
> >>> >>>>
> >>> >>>>
> >>> >>>>> Date: Tuesday, January 14, 2020 09:28:45 +0530
> >>> >>>>> From: Padmahas Bn <pa...@gmail.com>
> >>> >>>>>
> >>> >>>>> Continued from my previous email.
> >>> >>>>> One more interesting observation.
> >>> >>>>>
> >>> >>>>> I've forwarded both both port 80 and port 8080.
> >>> >>>>> On port 80 my Apache web server is running on port 8080,
> >>> >>>>> Tomcat server is running.
> >>> >>>>>
> >>> >>>>> When I hit IP_ADDR:80, I got "Connection timed out".
> >>> >>>>> When I hit IP_ADDR:8080, I got "This site can't be reached".
> >>> >>>>>
> >>> >>>>> Any reason why this happened?
> >>> >>>>>
> >>> >>>>
> >>> >>>> ------------------------------------------------------------
> >>> >>>> ----- ---- To unsubscribe, e-mail:
> >>> >>>> users-unsubscribe@httpd.apache.org For additional commands,
> >>> >>>> e-mail: users-help@httpd.apache.org
> >>> >>>>
> >>> >>>>
> >>> > ------------ End Original Message ------------
> >>> >
> >>> >
> >>> >
> >>> > ---------------------------------------------------------------
> >>> > ------ To unsubscribe, e-mail:
> >>> > users-unsubscribe@httpd.apache.org For additional commands,
> >>> > e-mail: users-help@httpd.apache.org
> >>> >
> >>>
> >>>
> >>> -----------------------------------------------------------------
> >>> ---- To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> >>> For additional commands, e-mail: users-help@httpd.apache.org
> >>>
> >>>
>
> ------------ End Original Message ------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
Re: [users@httpd] Expose my server to internet
Posted by Richard <li...@listmail.innovate.net>.
Since your hostname/ipnumber can't be pinged and all low-level ports
seem to be closed I'm going to bet that the blocking is at your
provider's level. You might want to check that that's really your
IPnumber. Try using something like:
<http://www.ipnumber.eu/ip/>
to confirm your public IPnumber.
------------ Original Message ------------
> Date: Wednesday, January 15, 2020 10:01:51 +0530
> From: Padmahas Bn <pa...@gmail.com>
> To: users <us...@httpd.apache.org>
> Subject: Re: [users@httpd] Expose my server to internet
>
> Thank you all for nmap and traceroute report.
>
> @Otis Dewitt,
>
>> You are being firewalld, those ports are not available from
>> outside.
>>
> Do you mean the firewall of my OS (Ubuntu) or is there any other
> levels of firewall?
> Like at my router level (even though it's there, since I've port
> forwarded it will allow these ports right?)?
> OR is it possible my ISP also have firewall that can block incoming
> traffic to my system?
>
> On Wed, Jan 15, 2020 at 2:05 AM Otis Dewitt - NOAA Affiliate
> <ot...@noaa.gov.invalid> wrote:
>
>> You are being firewalld, those ports are not available from
>> outside.
>>
>> On Tue, Jan 14, 2020 at 3:23 PM Larry Irwin (work) <
>> larry.irwin@ccamedical.com> wrote:
>>
>>> nmap shows all ports as filtered:
>>>
>>> # nmap -Pn padmahasa.ddns.net
>>>
>>> Starting Nmap 7.01 ( https://nmap.org ) at 2020-01-14 15:17 EST
>>> Nmap scan report for padmahasa.ddns.net (103.228.221.102)
>>> Host is up.
>>> rDNS record for 103.228.221.102:
>>> 103.228.221.102.static.belltele.in All 1000 scanned ports on
>>> padmahasa.ddns.net (103.228.221.102) are filtered
>>>
>>> Nmap done: 1 IP address (1 host up) scanned in 201.85 seconds--
>>>
>>> Larry Irwin
>>>
>>> On 1/14/20 2:58 PM, Richard wrote:
>>> > The IPnumber associated with padmahasa.ddns.net
>>> > (103.228.221.102) is not reachable via ping or traceroute. A
>>> > traceroute ends at:
>>> >
>>> > 43.254.160.42.static.belltele.in (43.254.160.42)
>>> >
>>> > Additionally, attempting to telnet to either port 80 or 8080 on
>>> > 103.228.221.102 results in a "network hang".
>>> >
>>> > So, it would seem that that IPnumber is not publicly reachable.
>>> > {Assuming the dns entry to be correct] if you're not
>>> > firewalling it then you need to speak with your provider.
>>> >
>>> >
>>> >> Date: Wednesday, January 15, 2020 01:03:27 +0530
>>> >> From: Padmahas Bn <pa...@gmail.com>
>>> >>
>>> >> Hello @Richard and @Monah baki
>>> >>
>>> >> @Richard,
>>> >>
>>> >>> -- what is the public IPnumber of your server?
>>> >>>
>>> >> I'm not sure whether it's OK or not to tell my public IP
>>> >> openly. But I can give partial IP address.
>>> >> xxx.xxx.221.102
>>> >>
>>> >>> -- what is the public DNS name for your server (i.e., the dns
>>> >>> entry
>>> >>>
>>> >> padmahasa.ddns.net
>>> >>
>>> >>> that points to the public IPnumber)?
>>> >>>
>>> >> Yeah that points to public IP number.
>>> >>
>>> >> @Monah,
>>> >> I think the firewall will not be active by default and I double
>>> >> checked with firewall, which is not active in my Ubuntu system.
>>> >> But should I do any weird thing like, activating it and
>>> >> explicitly allow http traffic in?
>>> >> Until now this is the situation.
>>> >> 1. There is no problem with OS and firewall.
>>> >> 2. There is no problem with web server configuration.
>>> >> 3. There is no problem with my ISP (I had asked my ISP whether
>>> >> they are going to block any incoming traffic but they said No).
>>> >>
>>> >> Still not able to reach my server from internet.
>>> >> Let me know what you guys think the reason could be.
>>> >>
>>> >> Thank you.
>>> >>
>>> >> On Tue, Jan 14, 2020 at 9:23 PM Monah Baki
>>> >> <mo...@gmail.com> wrote:
>>> >>
>>> >>> Check firewall
>>> >>>
>>> >>> On Tue, Jan 14, 2020 at 10:43 AM Richard <
>>> >>> lists-apache@listmail.innovate.net> wrote:
>>> >>>
>>> >>>> Looking back some months I'm not finding the beginning of
>>> >>>> this thread, so maybe you should start fresh.
>>> >>>>
>>> >>>> -- what is the public IPnumber of your server?
>>> >>>>
>>> >>>> -- what is the public DNS name for your server (i.e., the dns
>>> >>>> entry that points to the public IPnumber)?
>>> >>>>
>>> >>>>
>>> >>>>> Date: Tuesday, January 14, 2020 09:28:45 +0530
>>> >>>>> From: Padmahas Bn <pa...@gmail.com>
>>> >>>>>
>>> >>>>> Continued from my previous email.
>>> >>>>> One more interesting observation.
>>> >>>>>
>>> >>>>> I've forwarded both both port 80 and port 8080.
>>> >>>>> On port 80 my Apache web server is running on port 8080,
>>> >>>>> Tomcat server is running.
>>> >>>>>
>>> >>>>> When I hit IP_ADDR:80, I got "Connection timed out".
>>> >>>>> When I hit IP_ADDR:8080, I got "This site can't be reached".
>>> >>>>>
>>> >>>>> Any reason why this happened?
>>> >>>>>
>>> >>>>
>>> >>>> ------------------------------------------------------------
>>> >>>> ----- ---- To unsubscribe, e-mail:
>>> >>>> users-unsubscribe@httpd.apache.org For additional commands,
>>> >>>> e-mail: users-help@httpd.apache.org
>>> >>>>
>>> >>>>
>>> > ------------ End Original Message ------------
>>> >
>>> >
>>> >
>>> > ---------------------------------------------------------------
>>> > ------ To unsubscribe, e-mail:
>>> > users-unsubscribe@httpd.apache.org For additional commands,
>>> > e-mail: users-help@httpd.apache.org
>>> >
>>>
>>>
>>> -----------------------------------------------------------------
>>> ---- To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>>> For additional commands, e-mail: users-help@httpd.apache.org
>>>
>>>
------------ End Original Message ------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Expose my server to internet
Posted by Padmahas Bn <pa...@gmail.com>.
Thank you all for nmap and traceroute report.
@Otis Dewitt,
> You are being firewalld, those ports are not available from outside.
>
Do you mean the firewall of my OS (Ubuntu) or is there any other levels of
firewall?
Like at my router level (even though it's there, since I've port forwarded
it will allow these ports right?)?
OR is it possible my ISP also have firewall that can block incoming traffic
to my system?
On Wed, Jan 15, 2020 at 2:05 AM Otis Dewitt - NOAA Affiliate
<ot...@noaa.gov.invalid> wrote:
> You are being firewalld, those ports are not available from outside.
>
> On Tue, Jan 14, 2020 at 3:23 PM Larry Irwin (work) <
> larry.irwin@ccamedical.com> wrote:
>
>> nmap shows all ports as filtered:
>>
>> # nmap -Pn padmahasa.ddns.net
>>
>> Starting Nmap 7.01 ( https://nmap.org ) at 2020-01-14 15:17 EST
>> Nmap scan report for padmahasa.ddns.net (103.228.221.102)
>> Host is up.
>> rDNS record for 103.228.221.102: 103.228.221.102.static.belltele.in
>> All 1000 scanned ports on padmahasa.ddns.net (103.228.221.102) are
>> filtered
>>
>> Nmap done: 1 IP address (1 host up) scanned in 201.85 seconds--
>>
>> Larry Irwin
>>
>> On 1/14/20 2:58 PM, Richard wrote:
>> > The IPnumber associated with padmahasa.ddns.net (103.228.221.102) is
>> > not reachable via ping or traceroute. A traceroute ends at:
>> >
>> > 43.254.160.42.static.belltele.in (43.254.160.42)
>> >
>> > Additionally, attempting to telnet to either port 80 or 8080 on
>> > 103.228.221.102 results in a "network hang".
>> >
>> > So, it would seem that that IPnumber is not publicly reachable.
>> > {Assuming the dns entry to be correct] if you're not firewalling it
>> > then you need to speak with your provider.
>> >
>> >
>> >> Date: Wednesday, January 15, 2020 01:03:27 +0530
>> >> From: Padmahas Bn <pa...@gmail.com>
>> >>
>> >> Hello @Richard and @Monah baki
>> >>
>> >> @Richard,
>> >>
>> >>> -- what is the public IPnumber of your server?
>> >>>
>> >> I'm not sure whether it's OK or not to tell my public IP openly.
>> >> But I can give partial IP address.
>> >> xxx.xxx.221.102
>> >>
>> >>> -- what is the public DNS name for your server (i.e., the dns entry
>> >>>
>> >> padmahasa.ddns.net
>> >>
>> >>> that points to the public IPnumber)?
>> >>>
>> >> Yeah that points to public IP number.
>> >>
>> >> @Monah,
>> >> I think the firewall will not be active by default and I double
>> >> checked with firewall, which is not active in my Ubuntu system.
>> >> But should I do any weird thing like, activating it and explicitly
>> >> allow http traffic in?
>> >> Until now this is the situation.
>> >> 1. There is no problem with OS and firewall.
>> >> 2. There is no problem with web server configuration.
>> >> 3. There is no problem with my ISP (I had asked my ISP whether they
>> >> are going to block any incoming traffic but they said No).
>> >>
>> >> Still not able to reach my server from internet.
>> >> Let me know what you guys think the reason could be.
>> >>
>> >> Thank you.
>> >>
>> >> On Tue, Jan 14, 2020 at 9:23 PM Monah Baki <mo...@gmail.com>
>> >> wrote:
>> >>
>> >>> Check firewall
>> >>>
>> >>> On Tue, Jan 14, 2020 at 10:43 AM Richard <
>> >>> lists-apache@listmail.innovate.net> wrote:
>> >>>
>> >>>> Looking back some months I'm not finding the beginning of this
>> >>>> thread, so maybe you should start fresh.
>> >>>>
>> >>>> -- what is the public IPnumber of your server?
>> >>>>
>> >>>> -- what is the public DNS name for your server (i.e., the dns
>> >>>> entry that points to the public IPnumber)?
>> >>>>
>> >>>>
>> >>>>> Date: Tuesday, January 14, 2020 09:28:45 +0530
>> >>>>> From: Padmahas Bn <pa...@gmail.com>
>> >>>>>
>> >>>>> Continued from my previous email.
>> >>>>> One more interesting observation.
>> >>>>>
>> >>>>> I've forwarded both both port 80 and port 8080.
>> >>>>> On port 80 my Apache web server is running on port 8080, Tomcat
>> >>>>> server is running.
>> >>>>>
>> >>>>> When I hit IP_ADDR:80, I got "Connection timed out".
>> >>>>> When I hit IP_ADDR:8080, I got "This site can't be reached".
>> >>>>>
>> >>>>> Any reason why this happened?
>> >>>>>
>> >>>>
>> >>>> -----------------------------------------------------------------
>> >>>> ---- To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>> >>>> For additional commands, e-mail: users-help@httpd.apache.org
>> >>>>
>> >>>>
>> > ------------ End Original Message ------------
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>> > For additional commands, e-mail: users-help@httpd.apache.org
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>> For additional commands, e-mail: users-help@httpd.apache.org
>>
>>
Re: [users@httpd] Expose my server to internet
Posted by Otis Dewitt - NOAA Affiliate <ot...@noaa.gov.INVALID>.
You are being firewalld, those ports are not available from outside.
On Tue, Jan 14, 2020 at 3:23 PM Larry Irwin (work) <
larry.irwin@ccamedical.com> wrote:
> nmap shows all ports as filtered:
>
> # nmap -Pn padmahasa.ddns.net
>
> Starting Nmap 7.01 ( https://nmap.org ) at 2020-01-14 15:17 EST
> Nmap scan report for padmahasa.ddns.net (103.228.221.102)
> Host is up.
> rDNS record for 103.228.221.102: 103.228.221.102.static.belltele.in
> All 1000 scanned ports on padmahasa.ddns.net (103.228.221.102) are
> filtered
>
> Nmap done: 1 IP address (1 host up) scanned in 201.85 seconds--
>
> Larry Irwin
>
> On 1/14/20 2:58 PM, Richard wrote:
> > The IPnumber associated with padmahasa.ddns.net (103.228.221.102) is
> > not reachable via ping or traceroute. A traceroute ends at:
> >
> > 43.254.160.42.static.belltele.in (43.254.160.42)
> >
> > Additionally, attempting to telnet to either port 80 or 8080 on
> > 103.228.221.102 results in a "network hang".
> >
> > So, it would seem that that IPnumber is not publicly reachable.
> > {Assuming the dns entry to be correct] if you're not firewalling it
> > then you need to speak with your provider.
> >
> >
> >> Date: Wednesday, January 15, 2020 01:03:27 +0530
> >> From: Padmahas Bn <pa...@gmail.com>
> >>
> >> Hello @Richard and @Monah baki
> >>
> >> @Richard,
> >>
> >>> -- what is the public IPnumber of your server?
> >>>
> >> I'm not sure whether it's OK or not to tell my public IP openly.
> >> But I can give partial IP address.
> >> xxx.xxx.221.102
> >>
> >>> -- what is the public DNS name for your server (i.e., the dns entry
> >>>
> >> padmahasa.ddns.net
> >>
> >>> that points to the public IPnumber)?
> >>>
> >> Yeah that points to public IP number.
> >>
> >> @Monah,
> >> I think the firewall will not be active by default and I double
> >> checked with firewall, which is not active in my Ubuntu system.
> >> But should I do any weird thing like, activating it and explicitly
> >> allow http traffic in?
> >> Until now this is the situation.
> >> 1. There is no problem with OS and firewall.
> >> 2. There is no problem with web server configuration.
> >> 3. There is no problem with my ISP (I had asked my ISP whether they
> >> are going to block any incoming traffic but they said No).
> >>
> >> Still not able to reach my server from internet.
> >> Let me know what you guys think the reason could be.
> >>
> >> Thank you.
> >>
> >> On Tue, Jan 14, 2020 at 9:23 PM Monah Baki <mo...@gmail.com>
> >> wrote:
> >>
> >>> Check firewall
> >>>
> >>> On Tue, Jan 14, 2020 at 10:43 AM Richard <
> >>> lists-apache@listmail.innovate.net> wrote:
> >>>
> >>>> Looking back some months I'm not finding the beginning of this
> >>>> thread, so maybe you should start fresh.
> >>>>
> >>>> -- what is the public IPnumber of your server?
> >>>>
> >>>> -- what is the public DNS name for your server (i.e., the dns
> >>>> entry that points to the public IPnumber)?
> >>>>
> >>>>
> >>>>> Date: Tuesday, January 14, 2020 09:28:45 +0530
> >>>>> From: Padmahas Bn <pa...@gmail.com>
> >>>>>
> >>>>> Continued from my previous email.
> >>>>> One more interesting observation.
> >>>>>
> >>>>> I've forwarded both both port 80 and port 8080.
> >>>>> On port 80 my Apache web server is running on port 8080, Tomcat
> >>>>> server is running.
> >>>>>
> >>>>> When I hit IP_ADDR:80, I got "Connection timed out".
> >>>>> When I hit IP_ADDR:8080, I got "This site can't be reached".
> >>>>>
> >>>>> Any reason why this happened?
> >>>>>
> >>>>
> >>>> -----------------------------------------------------------------
> >>>> ---- To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> >>>> For additional commands, e-mail: users-help@httpd.apache.org
> >>>>
> >>>>
> > ------------ End Original Message ------------
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
Re: [users@httpd] Expose my server to internet
Posted by "Larry Irwin (work)" <la...@ccamedical.com>.
nmap shows all ports as filtered:
# nmap -Pn padmahasa.ddns.net
Starting Nmap 7.01 ( https://nmap.org ) at 2020-01-14 15:17 EST
Nmap scan report for padmahasa.ddns.net (103.228.221.102)
Host is up.
rDNS record for 103.228.221.102: 103.228.221.102.static.belltele.in
All 1000 scanned ports on padmahasa.ddns.net (103.228.221.102) are filtered
Nmap done: 1 IP address (1 host up) scanned in 201.85 seconds--
Larry Irwin
On 1/14/20 2:58 PM, Richard wrote:
> The IPnumber associated with padmahasa.ddns.net (103.228.221.102) is
> not reachable via ping or traceroute. A traceroute ends at:
>
> 43.254.160.42.static.belltele.in (43.254.160.42)
>
> Additionally, attempting to telnet to either port 80 or 8080 on
> 103.228.221.102 results in a "network hang".
>
> So, it would seem that that IPnumber is not publicly reachable.
> {Assuming the dns entry to be correct] if you're not firewalling it
> then you need to speak with your provider.
>
>
>> Date: Wednesday, January 15, 2020 01:03:27 +0530
>> From: Padmahas Bn <pa...@gmail.com>
>>
>> Hello @Richard and @Monah baki
>>
>> @Richard,
>>
>>> -- what is the public IPnumber of your server?
>>>
>> I'm not sure whether it's OK or not to tell my public IP openly.
>> But I can give partial IP address.
>> xxx.xxx.221.102
>>
>>> -- what is the public DNS name for your server (i.e., the dns entry
>>>
>> padmahasa.ddns.net
>>
>>> that points to the public IPnumber)?
>>>
>> Yeah that points to public IP number.
>>
>> @Monah,
>> I think the firewall will not be active by default and I double
>> checked with firewall, which is not active in my Ubuntu system.
>> But should I do any weird thing like, activating it and explicitly
>> allow http traffic in?
>> Until now this is the situation.
>> 1. There is no problem with OS and firewall.
>> 2. There is no problem with web server configuration.
>> 3. There is no problem with my ISP (I had asked my ISP whether they
>> are going to block any incoming traffic but they said No).
>>
>> Still not able to reach my server from internet.
>> Let me know what you guys think the reason could be.
>>
>> Thank you.
>>
>> On Tue, Jan 14, 2020 at 9:23 PM Monah Baki <mo...@gmail.com>
>> wrote:
>>
>>> Check firewall
>>>
>>> On Tue, Jan 14, 2020 at 10:43 AM Richard <
>>> lists-apache@listmail.innovate.net> wrote:
>>>
>>>> Looking back some months I'm not finding the beginning of this
>>>> thread, so maybe you should start fresh.
>>>>
>>>> -- what is the public IPnumber of your server?
>>>>
>>>> -- what is the public DNS name for your server (i.e., the dns
>>>> entry that points to the public IPnumber)?
>>>>
>>>>
>>>>> Date: Tuesday, January 14, 2020 09:28:45 +0530
>>>>> From: Padmahas Bn <pa...@gmail.com>
>>>>>
>>>>> Continued from my previous email.
>>>>> One more interesting observation.
>>>>>
>>>>> I've forwarded both both port 80 and port 8080.
>>>>> On port 80 my Apache web server is running on port 8080, Tomcat
>>>>> server is running.
>>>>>
>>>>> When I hit IP_ADDR:80, I got "Connection timed out".
>>>>> When I hit IP_ADDR:8080, I got "This site can't be reached".
>>>>>
>>>>> Any reason why this happened?
>>>>>
>>>>
>>>> -----------------------------------------------------------------
>>>> ---- To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>>>> For additional commands, e-mail: users-help@httpd.apache.org
>>>>
>>>>
> ------------ End Original Message ------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Expose my server to internet
Posted by Richard <li...@listmail.innovate.net>.
The IPnumber associated with padmahasa.ddns.net (103.228.221.102) is
not reachable via ping or traceroute. A traceroute ends at:
43.254.160.42.static.belltele.in (43.254.160.42)
Additionally, attempting to telnet to either port 80 or 8080 on
103.228.221.102 results in a "network hang".
So, it would seem that that IPnumber is not publicly reachable.
{Assuming the dns entry to be correct] if you're not firewalling it
then you need to speak with your provider.
> Date: Wednesday, January 15, 2020 01:03:27 +0530
> From: Padmahas Bn <pa...@gmail.com>
>
> Hello @Richard and @Monah baki
>
> @Richard,
>
>> -- what is the public IPnumber of your server?
>>
> I'm not sure whether it's OK or not to tell my public IP openly.
> But I can give partial IP address.
> xxx.xxx.221.102
>
>> -- what is the public DNS name for your server (i.e., the dns entry
>>
> padmahasa.ddns.net
>
>> that points to the public IPnumber)?
>>
> Yeah that points to public IP number.
>
> @Monah,
> I think the firewall will not be active by default and I double
> checked with firewall, which is not active in my Ubuntu system.
> But should I do any weird thing like, activating it and explicitly
> allow http traffic in?
> Until now this is the situation.
> 1. There is no problem with OS and firewall.
> 2. There is no problem with web server configuration.
> 3. There is no problem with my ISP (I had asked my ISP whether they
> are going to block any incoming traffic but they said No).
>
> Still not able to reach my server from internet.
> Let me know what you guys think the reason could be.
>
> Thank you.
>
> On Tue, Jan 14, 2020 at 9:23 PM Monah Baki <mo...@gmail.com>
> wrote:
>
>> Check firewall
>>
>> On Tue, Jan 14, 2020 at 10:43 AM Richard <
>> lists-apache@listmail.innovate.net> wrote:
>>
>>> Looking back some months I'm not finding the beginning of this
>>> thread, so maybe you should start fresh.
>>>
>>> -- what is the public IPnumber of your server?
>>>
>>> -- what is the public DNS name for your server (i.e., the dns
>>> entry that points to the public IPnumber)?
>>>
>>>
>>> > Date: Tuesday, January 14, 2020 09:28:45 +0530
>>> > From: Padmahas Bn <pa...@gmail.com>
>>> >
>>> > Continued from my previous email.
>>> > One more interesting observation.
>>> >
>>> > I've forwarded both both port 80 and port 8080.
>>> > On port 80 my Apache web server is running on port 8080, Tomcat
>>> > server is running.
>>> >
>>> > When I hit IP_ADDR:80, I got "Connection timed out".
>>> > When I hit IP_ADDR:8080, I got "This site can't be reached".
>>> >
>>> > Any reason why this happened?
>>> >
>>>
>>>
>>> -----------------------------------------------------------------
>>> ---- To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>>> For additional commands, e-mail: users-help@httpd.apache.org
>>>
>>>
------------ End Original Message ------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Expose my server to internet
Posted by Padmahas Bn <pa...@gmail.com>.
Hello @Richard and @Monah baki
@Richard,
> -- what is the public IPnumber of your server?
>
I'm not sure whether it's OK or not to tell my public IP openly. But I can
give partial IP address.
xxx.xxx.221.102
> -- what is the public DNS name for your server (i.e., the dns entry
>
padmahasa.ddns.net
> that points to the public IPnumber)?
>
Yeah that points to public IP number.
@Monah,
I think the firewall will not be active by default and I double checked
with firewall, which is not active in my Ubuntu system.
But should I do any weird thing like, activating it and explicitly allow
http traffic in?
Until now this is the situation.
1. There is no problem with OS and firewall.
2. There is no problem with web server configuration.
3. There is no problem with my ISP (I had asked my ISP whether they are
going to block any incoming traffic but they said No).
Still not able to reach my server from internet.
Let me know what you guys think the reason could be.
Thank you.
On Tue, Jan 14, 2020 at 9:23 PM Monah Baki <mo...@gmail.com> wrote:
> Check firewall
>
> On Tue, Jan 14, 2020 at 10:43 AM Richard <
> lists-apache@listmail.innovate.net> wrote:
>
>> Looking back some months I'm not finding the beginning of this
>> thread, so maybe you should start fresh.
>>
>> -- what is the public IPnumber of your server?
>>
>> -- what is the public DNS name for your server (i.e., the dns entry
>> that points to the public IPnumber)?
>>
>>
>> > Date: Tuesday, January 14, 2020 09:28:45 +0530
>> > From: Padmahas Bn <pa...@gmail.com>
>> >
>> > Continued from my previous email.
>> > One more interesting observation.
>> >
>> > I've forwarded both both port 80 and port 8080.
>> > On port 80 my Apache web server is running on port 8080, Tomcat
>> > server is running.
>> >
>> > When I hit IP_ADDR:80, I got "Connection timed out".
>> > When I hit IP_ADDR:8080, I got "This site can't be reached".
>> >
>> > Any reason why this happened?
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>> For additional commands, e-mail: users-help@httpd.apache.org
>>
>>
Re: [users@httpd] Expose my server to internet
Posted by Monah Baki <mo...@gmail.com>.
Check firewall
On Tue, Jan 14, 2020 at 10:43 AM Richard <li...@listmail.innovate.net>
wrote:
> Looking back some months I'm not finding the beginning of this
> thread, so maybe you should start fresh.
>
> -- what is the public IPnumber of your server?
>
> -- what is the public DNS name for your server (i.e., the dns entry
> that points to the public IPnumber)?
>
>
> > Date: Tuesday, January 14, 2020 09:28:45 +0530
> > From: Padmahas Bn <pa...@gmail.com>
> >
> > Continued from my previous email.
> > One more interesting observation.
> >
> > I've forwarded both both port 80 and port 8080.
> > On port 80 my Apache web server is running on port 8080, Tomcat
> > server is running.
> >
> > When I hit IP_ADDR:80, I got "Connection timed out".
> > When I hit IP_ADDR:8080, I got "This site can't be reached".
> >
> > Any reason why this happened?
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
Re: [users@httpd] Expose my server to internet
Posted by Richard <li...@listmail.innovate.net>.
Looking back some months I'm not finding the beginning of this
thread, so maybe you should start fresh.
-- what is the public IPnumber of your server?
-- what is the public DNS name for your server (i.e., the dns entry
that points to the public IPnumber)?
> Date: Tuesday, January 14, 2020 09:28:45 +0530
> From: Padmahas Bn <pa...@gmail.com>
>
> Continued from my previous email.
> One more interesting observation.
>
> I've forwarded both both port 80 and port 8080.
> On port 80 my Apache web server is running on port 8080, Tomcat
> server is running.
>
> When I hit IP_ADDR:80, I got "Connection timed out".
> When I hit IP_ADDR:8080, I got "This site can't be reached".
>
> Any reason why this happened?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Expose my server to internet
Posted by Padmahas Bn <pa...@gmail.com>.
Continued from my previous email.
One more interesting observation.
I've forwarded both both port 80 and port 8080.
On port 80 my Apache web server is running on port 8080, Tomcat server is
running.
When I hit IP_ADDR:80, I got "Connection timed out".
When I hit IP_ADDR:8080, I got "This site can't be reached".
Any reason why this happened?
Thank you,
On Tue, Jan 14, 2020 at 8:52 AM Padmahas Bn <pa...@gmail.com> wrote:
> Hello @Bob Cochran, @James Moe
>
> Sorry for the very late reply. I was not able to work on this until
> yesterday.
> @Bob Cochran, I gave right argument (my network interface name was eno1)
> for tcpdump and have got very long output. Below are the first few lines.
> And I got reply from my ISP that they wont block any incoming requests.
> And they gave the reason, if port 80 was blocked I would not be able to use
> internet at all. I thought blocking port and blocking requests are 2
> different things. So I've again asked them for clarification on blocking
> incoming requests.
> Output of tcpdump
>
> sudo tcpdump -i eno1 -vvvSXn port 80
> tcpdump: listening on eno1, link-type EN10MB (Ethernet), capture size
> 262144 bytes
> 08:34:36.311747 IP (tos 0x0, ttl 64, id 2906, offset 0, flags [DF], proto
> TCP (6), length 60)
> 192.168.0.106.53348 > 35.222.85.5.80: Flags [S], cksum 0x3a24
> (incorrect -> 0x2c43), seq 3571338894, win 64240, options [mss
> 1460,sackOK,TS val 3757642427 ecr 0,nop,wscale 7], length 0
> 0x0000: 4500 003c 0b5a 4000 4006 f56c c0a8 006a E..<.Z@.@..l...j
> 0x0010: 23de 5505 d064 0050 d4de 4e8e 0000 0000 #.U..d.P..N.....
> 0x0020: a002 faf0 3a24 0000 0204 05b4 0402 080a ....:$..........
> 0x0030: dff9 12bb 0000 0000 0103 0307 ............
> 08:34:36.542112 IP (tos 0x0, ttl 57, id 0, offset 0, flags [DF], proto TCP
> (6), length 60)
> 35.222.85.5.80 > 192.168.0.106.53348: Flags [S.], cksum 0x5b44
> (correct), seq 2985042357, ack 3571338895, win 28160, options [mss
> 1420,sackOK,TS val 3577197868 ecr 3757642427,nop,wscale 7], length 0
> 0x0000: 4500 003c 0000 4000 3906 07c7 23de 5505 E..<..@.9...#.U.
> 0x0010: c0a8 006a 0050 d064 b1ec 21b5 d4de 4e8f ...j.P.d..!...N.
> 0x0020: a012 6e00 5b44 0000 0204 058c 0402 080a ..n.[D..........
> 0x0030: d537 b52c dff9 12bb 0103 0307 .7.,........
> 08:34:36.542189 IP (tos 0x0, ttl 64, id 2907, offset 0, flags [DF], proto
> TCP (6), length 52)
> 192.168.0.106.53348 > 35.222.85.5.80: Flags [.], cksum 0x3a1c
> (incorrect -> 0xf50b), seq 3571338895, ack 2985042358, win 502, options
> [nop,nop,TS val 3757642658 ecr 3577197868], length 0
> 0x0000: 4500 0034 0b5b 4000 4006 f573 c0a8 006a E..4.[@.@..s...j
> 0x0010: 23de 5505 d064 0050 d4de 4e8f b1ec 21b6 #.U..d.P..N...!.
> 0x0020: 8010 01f6 3a1c 0000 0101 080a dff9 13a2 ....:...........
> 0x0030: d537 b52c
>
> I checked the status of Ubuntu firewall. Its not yet active. Hence all
> requests from any host and any port should be allowed.
> In my Apache I've even given the server name of my free registered domain.
> ServerName www.padmahasa.ddns.net:80
>
> And Listen is only given with port 80. Hence any IP address should be
> allowed.
> Listen 80
> Finally,
> 1. There is no problem with OS and firewall.
> 2. There is no problem with web server configuration.
> 3. There is no problem with my ISP.
>
> Still not able to reach my server from internet.
> Can anyone think of any other reasons please.
>
> Thank you.
>
> On Sun, Jul 14, 2019 at 1:35 AM James Moe <ji...@sohnen-moe.com.invalid>
> wrote:
>
>> On 12/07/2019 1.01 PM, rexkogitans@gmx.at wrote:
>>
>> > In my router I've also configured the settings and successfully logged
>> in.
>> > But when I test whether my port 80 is accessible, it's not opened.
>> > This is my home system, using Ubuntu 18.04. I've not enabled any
>> > firewall by myself.
>> >
>> Many ISPs have restrictions on servers. Often a "residential" Internet
>> service does not allow website or email servers. That is, connections
>> initiated from outside your network are blocked.
>> Check with your ISP about serving websites.
>>
>> --
>> James Moe
>> moe dot james at sohnen-moe dot com
>> 520.743.3936
>> Think.
>>
>>
Re: [users@httpd] Expose my server to internet
Posted by Padmahas Bn <pa...@gmail.com>.
Hello @Bob Cochran, @James Moe
Sorry for the very late reply. I was not able to work on this until
yesterday.
@Bob Cochran, I gave right argument (my network interface name was eno1)
for tcpdump and have got very long output. Below are the first few lines.
And I got reply from my ISP that they wont block any incoming requests. And
they gave the reason, if port 80 was blocked I would not be able to use
internet at all. I thought blocking port and blocking requests are 2
different things. So I've again asked them for clarification on blocking
incoming requests.
Output of tcpdump
sudo tcpdump -i eno1 -vvvSXn port 80
tcpdump: listening on eno1, link-type EN10MB (Ethernet), capture size
262144 bytes
08:34:36.311747 IP (tos 0x0, ttl 64, id 2906, offset 0, flags [DF], proto
TCP (6), length 60)
192.168.0.106.53348 > 35.222.85.5.80: Flags [S], cksum 0x3a24
(incorrect -> 0x2c43), seq 3571338894, win 64240, options [mss
1460,sackOK,TS val 3757642427 ecr 0,nop,wscale 7], length 0
0x0000: 4500 003c 0b5a 4000 4006 f56c c0a8 006a E..<.Z@.@..l...j
0x0010: 23de 5505 d064 0050 d4de 4e8e 0000 0000 #.U..d.P..N.....
0x0020: a002 faf0 3a24 0000 0204 05b4 0402 080a ....:$..........
0x0030: dff9 12bb 0000 0000 0103 0307 ............
08:34:36.542112 IP (tos 0x0, ttl 57, id 0, offset 0, flags [DF], proto TCP
(6), length 60)
35.222.85.5.80 > 192.168.0.106.53348: Flags [S.], cksum 0x5b44
(correct), seq 2985042357, ack 3571338895, win 28160, options [mss
1420,sackOK,TS val 3577197868 ecr 3757642427,nop,wscale 7], length 0
0x0000: 4500 003c 0000 4000 3906 07c7 23de 5505 E..<..@.9...#.U.
0x0010: c0a8 006a 0050 d064 b1ec 21b5 d4de 4e8f ...j.P.d..!...N.
0x0020: a012 6e00 5b44 0000 0204 058c 0402 080a ..n.[D..........
0x0030: d537 b52c dff9 12bb 0103 0307 .7.,........
08:34:36.542189 IP (tos 0x0, ttl 64, id 2907, offset 0, flags [DF], proto
TCP (6), length 52)
192.168.0.106.53348 > 35.222.85.5.80: Flags [.], cksum 0x3a1c
(incorrect -> 0xf50b), seq 3571338895, ack 2985042358, win 502, options
[nop,nop,TS val 3757642658 ecr 3577197868], length 0
0x0000: 4500 0034 0b5b 4000 4006 f573 c0a8 006a E..4.[@.@..s...j
0x0010: 23de 5505 d064 0050 d4de 4e8f b1ec 21b6 #.U..d.P..N...!.
0x0020: 8010 01f6 3a1c 0000 0101 080a dff9 13a2 ....:...........
0x0030: d537 b52c
I checked the status of Ubuntu firewall. Its not yet active. Hence all
requests from any host and any port should be allowed.
In my Apache I've even given the server name of my free registered domain.
ServerName www.padmahasa.ddns.net:80
And Listen is only given with port 80. Hence any IP address should be
allowed.
Listen 80
Finally,
1. There is no problem with OS and firewall.
2. There is no problem with web server configuration.
3. There is no problem with my ISP.
Still not able to reach my server from internet.
Can anyone think of any other reasons please.
Thank you.
On Sun, Jul 14, 2019 at 1:35 AM James Moe <ji...@sohnen-moe.com.invalid>
wrote:
> On 12/07/2019 1.01 PM, rexkogitans@gmx.at wrote:
>
> > In my router I've also configured the settings and successfully logged
> in.
> > But when I test whether my port 80 is accessible, it's not opened.
> > This is my home system, using Ubuntu 18.04. I've not enabled any
> > firewall by myself.
> >
> Many ISPs have restrictions on servers. Often a "residential" Internet
> service does not allow website or email servers. That is, connections
> initiated from outside your network are blocked.
> Check with your ISP about serving websites.
>
> --
> James Moe
> moe dot james at sohnen-moe dot com
> 520.743.3936
> Think.
>
>
Re: [users@httpd] Expose my server to internet
Posted by James Moe <ji...@sohnen-moe.com.INVALID>.
On 12/07/2019 1.01 PM, rexkogitans@gmx.at wrote:
> In my router I've also configured the settings and successfully logged in.
> But when I test whether my port 80 is accessible, it's not opened.
> This is my home system, using Ubuntu 18.04. I've not enabled any
> firewall by myself.
>
Many ISPs have restrictions on servers. Often a "residential" Internet
service does not allow website or email servers. That is, connections
initiated from outside your network are blocked.
Check with your ISP about serving websites.
--
James Moe
moe dot james at sohnen-moe dot com
520.743.3936
Think.
Re: [users@httpd] Expose my server to internet
Posted by "rexkogitans@gmx.at" <re...@gmx.at>.
This bails down to the same thing: Either your host establishes the
tunnel, or there is no way to reach it. In fact, this is a gateway
exclusively for your host - exactly something your ISP does not have.
Am 13.07.19 um 08:48 schrieb Walter H.:
> On 12.07.2019 22:01, rexkogitans@gmx.at wrote:
>>
>> If so, there is no way to access your host from outside (from the
>> Internet zone). There is also no way to access your host from within
>> another host of your ISP's network, because the intrazone traffic is
>> usally blocked.
> not at all;
> get an HE-IPv6-Tunnel and you have IPv6-connectivity from anywhere
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Expose my server to internet
Posted by "Walter H." <Wa...@mathemainzel.info>.
On 12.07.2019 22:01, rexkogitans@gmx.at wrote:
>
> If so, there is no way to access your host from outside (from the
> Internet zone). There is also no way to access your host from within
> another host of your ISP's network, because the intrazone traffic is
> usally blocked.
not at all;
get an HE-IPv6-Tunnel and you have IPv6-connectivity from anywhere
Re: [users@httpd] Expose my server to internet
Posted by "rexkogitans@gmx.at" <re...@gmx.at>.
Could it be that you have a Provider Grade NAT?
This means that your host is within your home LAN, and this home LAN is
within a LAN of the Internet provider. If you ask for your IP address on
sites like whatismyipaddress.com, you see the IP address that your
provider's gateway has in the Internet. Thousands of other hosts which
are also customers of your provider could have the same IP address then.
If so, there is no way to access your host from outside (from the
Internet zone). There is also no way to access your host from within
another host of your ISP's network, because the intrazone traffic is
usally blocked.
kr,
rexkogitans
Am 04.07.19 um 06:16 schrieb Padmahas Bn:
> Hello,
>
> Out of curiosity, I just want to access my server over internet.
> I have forwarded port 80.
> I have got a free domain in NoIP.
> In my router I've also configured the settings and successfully logged in.
> But when I test whether my port 80 is accessible, it's not opened.
> This is my home system, using Ubuntu 18.04. I've not enabled any
> firewall by myself.
>
> So just wanted to know whether should I configure anything in Apache
> httpd to make port 80 accessible?
>
> Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Expose my server to internet
Posted by Bob Cochran <ht...@mindchasers.com>.
On 7/4/19 12:16 AM, Padmahas Bn wrote:
> Hello,
>
> Out of curiosity, I just want to access my server over internet.
> I have forwarded port 80.
> I have got a free domain in NoIP.
> In my router I've also configured the settings and successfully logged in.
> But when I test whether my port 80 is accessible, it's not opened.
> This is my home system, using Ubuntu 18.04. I've not enabled any
> firewall by myself.
I think you're saying that you can access port 80 on your local network
but not from the Internet and are wondering what's blocking it. It's
another matter if you can't access your website on your own local
network. If that's the case, yes, you need to configure your conf file
properly. Read the tutorial on the apache site for a walk through.
I'm not sure what you mean by "successfully logged in" into your router.
Your router will need to support NAT to translate your local IP address
to the one on the Internet.
If I was you, the first thing I would do is run tcpdump or wireshark on
your machine running apache and make sure you see an HTTP request coming
in and a response going back out. You can do the same thing while
testing your local network, too.
Something like:
$ sudo tcpdump -i enp2s0 -vvvSXn port 80
This should give you the clues as to what's happening on your network.
Of course, you can also see a request in your apache log. I think the
default on Ubuntu for the log is /var/log/apache2/access.log
This page on our site might help you with tcpdump:
https://mindchasers.com/dev/tools-tcpdump
Good luck,
Bob
>
> So just wanted to know whether should I configure anything in Apache
> httpd to make port 80 accessible?
>
> Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Expose my server to internet
Posted by Bob Cochran <ht...@mindchasers.com>.
On 7/4/19 1:45 PM, Padmahas Bn wrote:
> Hello Bob, Richar and Mark,
> Thank you for your response.
>
> *@**Bob Cochran*,
> Yeah, I can access port 80 form my local but not from internet. I'm
> trying to access my IP from mobile network (Not wifi, from data pack)
> Please find my comments below.
>
> I'm not sure what you mean by "successfully logged in" into your
> router.
>
> As I said, I've registered a free domain name on NoIP.com, I had to
> configure dynamic DNS in my router to synchronize my external/public
> IP (since it is dynamic in nature) with my registered domain name
> automatically. So i meant that configuration was successful.
>
> Your router will need to support NAT to translate your local IP
> address
> to the one on the Internet.
>
> I'm using TP-Link 300M Wireless N Router, Model No. TL-WR841N /
> TL-WR841ND.
> I hope this supports NAT.
It sounds like you need to open a port on your router to forward port 80
to your apache server. Be careful about which ports you open and
realize that once you do, others will discover it. On the outside, you
don't have to open 80. It might be helpful to pick a high, obscure port
number to avoid bots that scan ports searching for ways to gain entry
into private networks.
>
> sudo tcpdump -i enp2s0 -vvvSXn port 80
>
> I'm not sure which parameters I need to change here according to my
> system. I just ran the same command and got output as
> tcpdump: enp2s0: No such device exists
> (SIOCGIFHWADDR: No such device)
enp2s0 is the name of my Ethernet network interface. I can discover it
by running ifconfig.
It seems that you're somewhat new to networking. I recommend that you
install Wireshark on your Ubuntu machine and read some tutorials about it.
>
> *@Richard szajkowski*,
> It's my home network, and have dynamic IP address. But I've updated
> the IP address which I got from google search "what is my ip", while
> forwarding the port.
>
> *@Mark J Bradakis,*
> Thank you for the reference. I'll take a look.
>
> Thank you.
> **
>
> On Thu, Jul 4, 2019 at 6:16 PM Mark J Bradakis <mark@bradakis.com
> <ma...@bradakis.com>> wrote:
>
> Some of the tools here might assist in tracking down what is
> visible to
> the world and what is not.
>
> https://tools.dnsstuff.com/#
>
> mjb.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> <ma...@httpd.apache.org>
> For additional commands, e-mail: users-help@httpd.apache.org
> <ma...@httpd.apache.org>
>
RE: [users@httpd] Expose my server to internet
Posted by Flaviu Radulescu <fl...@lumminary.com.INVALID>.
Here is a link to your router configuration with all the details of how to do the port forwarding: https://www.tp-link.com/us/user-guides/tl-wr841n_v14/chapter-4-configure-the-router-in-wireless-router-mode#ug-sub-title-7
---
FLAVIU RADULESCU | Lumminary | lumminary.com<https://lumminary.com/>
PLEASE NOTE: This email and any file transmitted are confidential and/or legally privileged and intended only for the person(s) directly addressed. If you are not the intended recipient, any use, copying, transmission, distribution, or other forms of dissemination is strictly prohibited. If you have received this email in error, please notify the sender immediately and permanently delete the email and files, if any.
From: Flaviu Radulescu <fl...@lumminary.com.INVALID>
Sent: 04 July 2019 23:05
To: users@httpd.apache.org
Subject: Re: [users@httpd] Expose my server to internet
You need to do port forwarding on your router from the public ip port 80 to the internal (server) ip port 80. Also, configure your router to always give the same ip (static ip) to your server.
This way all the requests coming from outside on port 80 are forwarded to internal server ip on port 80, the server response are going to normally be routed to the source request, but you just need the outside traffic to be routed the the server ip. So, search on your router configuration for port forwarding. That’s all you need to do, nothing on the apache, just standard configuration.
Apologies for brevity and/or typos. An iPhone was involved in writing this message.
On 4 Jul 2019, at 21:52, Richard szajkowski <va...@gmail.com>> wrote:
Yes , has to be set to static make sure your IP is out side the DCHP pool , that way it won’t be given to any one else by mistake .
That’s why I start my DHCP pool at .100
Richard Szajkowski
On Jul 4, 2019, at 2:12 PM, Padmahas Bn <pa...@gmail.com>> wrote:
Hello VA3RZS,
Yes, my internal IP address is static. It's 192.168.0.106. But DHCP is set to "Automatic". Does that affect?
Thank you.
On Thu, Jul 4, 2019 at 11:27 PM VA3RZS <va...@gmail.com>> wrote:
It’s your inside address that needs to be static , yes the router will just be fine
Your box will need to be on something like 192.168.1( or 0) .50 let’s say and in the router that ip and port should point to that ip and port
I have all my static ip’s under 100 and dhcp is above 100
Hope this helps
Richard Szajkowski
On Jul 4, 2019, at 1:45 PM, Padmahas Bn <pa...@gmail.com>> wrote:
Hello Bob, Richar and Mark,
Thank you for your response.
@Bob Cochran,
Yeah, I can access port 80 form my local but not from internet. I'm trying to access my IP from mobile network (Not wifi, from data pack) Please find my comments below.
I'm not sure what you mean by "successfully logged in" into your router.
As I said, I've registered a free domain name on NoIP.com<http://NoIP.com>, I had to configure dynamic DNS in my router to synchronize my external/public IP (since it is dynamic in nature) with my registered domain name automatically. So i meant that configuration was successful.
Your router will need to support NAT to translate your local IP address
to the one on the Internet.
I'm using TP-Link 300M Wireless N Router, Model No. TL-WR841N / TL-WR841ND.
I hope this supports NAT.
sudo tcpdump -i enp2s0 -vvvSXn port 80
I'm not sure which parameters I need to change here according to my system. I just ran the same command and got output as
tcpdump: enp2s0: No such device exists
(SIOCGIFHWADDR: No such device)
@Richard szajkowski,
It's my home network, and have dynamic IP address. But I've updated the IP address which I got from google search "what is my ip", while forwarding the port.
@Mark J Bradakis,
Thank you for the reference. I'll take a look.
Thank you.
On Thu, Jul 4, 2019 at 6:16 PM Mark J Bradakis <ma...@bradakis.com>> wrote:
Some of the tools here might assist in tracking down what is visible to
the world and what is not.
https://tools.dnsstuff.com/#<https://tools.dnsstuff.com/>
mjb.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org<ma...@httpd.apache.org>
For additional commands, e-mail: users-help@httpd.apache.org<ma...@httpd.apache.org>
Re: [users@httpd] Expose my server to internet
Posted by Flaviu Radulescu <fl...@lumminary.com.INVALID>.
You need to do port forwarding on your router from the public ip port 80 to the internal (server) ip port 80. Also, configure your router to always give the same ip (static ip) to your server.
This way all the requests coming from outside on port 80 are forwarded to internal server ip on port 80, the server response are going to normally be routed to the source request, but you just need the outside traffic to be routed the the server ip. So, search on your router configuration for port forwarding. That’s all you need to do, nothing on the apache, just standard configuration.
Apologies for brevity and/or typos. An iPhone was involved in writing this message.
On 4 Jul 2019, at 21:52, Richard szajkowski <va...@gmail.com>> wrote:
Yes , has to be set to static make sure your IP is out side the DCHP pool , that way it won’t be given to any one else by mistake .
That’s why I start my DHCP pool at .100
Richard Szajkowski
On Jul 4, 2019, at 2:12 PM, Padmahas Bn <pa...@gmail.com>> wrote:
Hello VA3RZS,
Yes, my internal IP address is static. It's 192.168.0.106. But DHCP is set to "Automatic". Does that affect?
Thank you.
On Thu, Jul 4, 2019 at 11:27 PM VA3RZS <va...@gmail.com>> wrote:
It’s your inside address that needs to be static , yes the router will just be fine
Your box will need to be on something like 192.168.1( or 0) .50 let’s say and in the router that ip and port should point to that ip and port
I have all my static ip’s under 100 and dhcp is above 100
Hope this helps
Richard Szajkowski
On Jul 4, 2019, at 1:45 PM, Padmahas Bn <pa...@gmail.com>> wrote:
Hello Bob, Richar and Mark,
Thank you for your response.
@Bob Cochran,
Yeah, I can access port 80 form my local but not from internet. I'm trying to access my IP from mobile network (Not wifi, from data pack) Please find my comments below.
I'm not sure what you mean by "successfully logged in" into your router.
As I said, I've registered a free domain name on NoIP.com<http://NoIP.com>, I had to configure dynamic DNS in my router to synchronize my external/public IP (since it is dynamic in nature) with my registered domain name automatically. So i meant that configuration was successful.
Your router will need to support NAT to translate your local IP address
to the one on the Internet.
I'm using TP-Link 300M Wireless N Router, Model No. TL-WR841N / TL-WR841ND.
I hope this supports NAT.
sudo tcpdump -i enp2s0 -vvvSXn port 80
I'm not sure which parameters I need to change here according to my system. I just ran the same command and got output as
tcpdump: enp2s0: No such device exists
(SIOCGIFHWADDR: No such device)
@Richard szajkowski,
It's my home network, and have dynamic IP address. But I've updated the IP address which I got from google search "what is my ip", while forwarding the port.
@Mark J Bradakis,
Thank you for the reference. I'll take a look.
Thank you.
On Thu, Jul 4, 2019 at 6:16 PM Mark J Bradakis <ma...@bradakis.com>> wrote:
Some of the tools here might assist in tracking down what is visible to
the world and what is not.
https://tools.dnsstuff.com/#
mjb.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org<ma...@httpd.apache.org>
For additional commands, e-mail: users-help@httpd.apache.org<ma...@httpd.apache.org>
Re: [users@httpd] Expose my server to internet
Posted by Richard szajkowski <va...@gmail.com>.
Yes , has to be set to static make sure your IP is out side the DCHP pool , that way it won’t be given to any one else by mistake .
That’s why I start my DHCP pool at .100
Richard Szajkowski
> On Jul 4, 2019, at 2:12 PM, Padmahas Bn <pa...@gmail.com> wrote:
>
> Hello VA3RZS,
>
> Yes, my internal IP address is static. It's 192.168.0.106. But DHCP is set to "Automatic". Does that affect?
>
> Thank you.
>
>> On Thu, Jul 4, 2019 at 11:27 PM VA3RZS <va...@gmail.com> wrote:
>> It’s your inside address that needs to be static , yes the router will just be fine
>>
>> Your box will need to be on something like 192.168.1( or 0) .50 let’s say and in the router that ip and port should point to that ip and port
>>
>> I have all my static ip’s under 100 and dhcp is above 100
>>
>> Hope this helps
>>
>> Richard Szajkowski
>>
>>
>>> On Jul 4, 2019, at 1:45 PM, Padmahas Bn <pa...@gmail.com> wrote:
>>>
>>> Hello Bob, Richar and Mark,
>>> Thank you for your response.
>>>
>>> @Bob Cochran,
>>> Yeah, I can access port 80 form my local but not from internet. I'm trying to access my IP from mobile network (Not wifi, from data pack) Please find my comments below.
>>>> I'm not sure what you mean by "successfully logged in" into your router.
>>> As I said, I've registered a free domain name on NoIP.com, I had to configure dynamic DNS in my router to synchronize my external/public IP (since it is dynamic in nature) with my registered domain name automatically. So i meant that configuration was successful.
>>>
>>>> Your router will need to support NAT to translate your local IP address
>>>> to the one on the Internet.
>>> I'm using TP-Link 300M Wireless N Router, Model No. TL-WR841N / TL-WR841ND.
>>> I hope this supports NAT.
>>>
>>>> sudo tcpdump -i enp2s0 -vvvSXn port 80
>>> I'm not sure which parameters I need to change here according to my system. I just ran the same command and got output as
>>> tcpdump: enp2s0: No such device exists
>>> (SIOCGIFHWADDR: No such device)
>>>
>>> @Richard szajkowski,
>>> It's my home network, and have dynamic IP address. But I've updated the IP address which I got from google search "what is my ip", while forwarding the port.
>>>
>>> @Mark J Bradakis,
>>> Thank you for the reference. I'll take a look.
>>>
>>> Thank you.
>>>
>>>> On Thu, Jul 4, 2019 at 6:16 PM Mark J Bradakis <ma...@bradakis.com> wrote:
>>>> Some of the tools here might assist in tracking down what is visible to
>>>> the world and what is not.
>>>>
>>>> https://tools.dnsstuff.com/#
>>>>
>>>> mjb.
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>>>> For additional commands, e-mail: users-help@httpd.apache.org
>>>>
Re: [users@httpd] Expose my server to internet
Posted by Padmahas Bn <pa...@gmail.com>.
Hello VA3RZS,
Yes, my internal IP address is static. It's 192.168.0.106. But DHCP is set
to "Automatic". Does that affect?
Thank you.
On Thu, Jul 4, 2019 at 11:27 PM VA3RZS <va...@gmail.com> wrote:
> It’s your inside address that needs to be static , yes the router will
> just be fine
>
> Your box will need to be on something like 192.168.1( or 0) .50 let’s say
> and in the router that ip and port should point to that ip and port
>
> I have all my static ip’s under 100 and dhcp is above 100
>
> Hope this helps
>
> Richard Szajkowski
>
>
> On Jul 4, 2019, at 1:45 PM, Padmahas Bn <pa...@gmail.com> wrote:
>
> Hello Bob, Richar and Mark,
> Thank you for your response.
>
> *@**Bob Cochran*,
> Yeah, I can access port 80 form my local but not from internet. I'm
> trying to access my IP from mobile network (Not wifi, from data pack)
> Please find my comments below.
>
>> I'm not sure what you mean by "successfully logged in" into your router.
>>
> As I said, I've registered a free domain name on NoIP.com, I had to
> configure dynamic DNS in my router to synchronize my external/public IP
> (since it is dynamic in nature) with my registered domain name
> automatically. So i meant that configuration was successful.
>
> Your router will need to support NAT to translate your local IP address
>> to the one on the Internet.
>>
> I'm using TP-Link 300M Wireless N Router, Model No. TL-WR841N / TL-WR841ND.
> I hope this supports NAT.
>
> sudo tcpdump -i enp2s0 -vvvSXn port 80
>>
> I'm not sure which parameters I need to change here according to my
> system. I just ran the same command and got output as
> tcpdump: enp2s0: No such device exists
> (SIOCGIFHWADDR: No such device)
>
> *@Richard szajkowski*,
> It's my home network, and have dynamic IP address. But I've updated the IP
> address which I got from google search "what is my ip", while forwarding
> the port.
>
> *@Mark J Bradakis,*
> Thank you for the reference. I'll take a look.
>
> Thank you.
>
> On Thu, Jul 4, 2019 at 6:16 PM Mark J Bradakis <ma...@bradakis.com> wrote:
>
>> Some of the tools here might assist in tracking down what is visible to
>> the world and what is not.
>>
>> https://tools.dnsstuff.com/#
>>
>> mjb.
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>> For additional commands, e-mail: users-help@httpd.apache.org
>>
>>
Re: [users@httpd] Expose my server to internet
Posted by VA3RZS <va...@gmail.com>.
It’s your inside address that needs to be static , yes the router will just be fine
Your box will need to be on something like 192.168.1( or 0) .50 let’s say and in the router that ip and port should point to that ip and port
I have all my static ip’s under 100 and dhcp is above 100
Hope this helps
Richard Szajkowski
> On Jul 4, 2019, at 1:45 PM, Padmahas Bn <pa...@gmail.com> wrote:
>
> Hello Bob, Richar and Mark,
> Thank you for your response.
>
> @Bob Cochran,
> Yeah, I can access port 80 form my local but not from internet. I'm trying to access my IP from mobile network (Not wifi, from data pack) Please find my comments below.
>> I'm not sure what you mean by "successfully logged in" into your router.
> As I said, I've registered a free domain name on NoIP.com, I had to configure dynamic DNS in my router to synchronize my external/public IP (since it is dynamic in nature) with my registered domain name automatically. So i meant that configuration was successful.
>
>> Your router will need to support NAT to translate your local IP address
>> to the one on the Internet.
> I'm using TP-Link 300M Wireless N Router, Model No. TL-WR841N / TL-WR841ND.
> I hope this supports NAT.
>
>> sudo tcpdump -i enp2s0 -vvvSXn port 80
> I'm not sure which parameters I need to change here according to my system. I just ran the same command and got output as
> tcpdump: enp2s0: No such device exists
> (SIOCGIFHWADDR: No such device)
>
> @Richard szajkowski,
> It's my home network, and have dynamic IP address. But I've updated the IP address which I got from google search "what is my ip", while forwarding the port.
>
> @Mark J Bradakis,
> Thank you for the reference. I'll take a look.
>
> Thank you.
>
>> On Thu, Jul 4, 2019 at 6:16 PM Mark J Bradakis <ma...@bradakis.com> wrote:
>> Some of the tools here might assist in tracking down what is visible to
>> the world and what is not.
>>
>> https://tools.dnsstuff.com/#
>>
>> mjb.
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>> For additional commands, e-mail: users-help@httpd.apache.org
>>
Re: [users@httpd] Expose my server to internet
Posted by Padmahas Bn <pa...@gmail.com>.
Hello Bob, Richar and Mark,
Thank you for your response.
*@**Bob Cochran*,
Yeah, I can access port 80 form my local but not from internet. I'm trying
to access my IP from mobile network (Not wifi, from data pack) Please find
my comments below.
> I'm not sure what you mean by "successfully logged in" into your router.
>
As I said, I've registered a free domain name on NoIP.com, I had to
configure dynamic DNS in my router to synchronize my external/public IP
(since it is dynamic in nature) with my registered domain name
automatically. So i meant that configuration was successful.
Your router will need to support NAT to translate your local IP address
> to the one on the Internet.
>
I'm using TP-Link 300M Wireless N Router, Model No. TL-WR841N / TL-WR841ND.
I hope this supports NAT.
sudo tcpdump -i enp2s0 -vvvSXn port 80
>
I'm not sure which parameters I need to change here according to my system.
I just ran the same command and got output as
tcpdump: enp2s0: No such device exists
(SIOCGIFHWADDR: No such device)
*@Richard szajkowski*,
It's my home network, and have dynamic IP address. But I've updated the IP
address which I got from google search "what is my ip", while forwarding
the port.
*@Mark J Bradakis,*
Thank you for the reference. I'll take a look.
Thank you.
On Thu, Jul 4, 2019 at 6:16 PM Mark J Bradakis <ma...@bradakis.com> wrote:
> Some of the tools here might assist in tracking down what is visible to
> the world and what is not.
>
> https://tools.dnsstuff.com/#
>
> mjb.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
Re: [users@httpd] Expose my server to internet
Posted by Mark J Bradakis <ma...@bradakis.com>.
Some of the tools here might assist in tracking down what is visible to
the world and what is not.
https://tools.dnsstuff.com/#
mjb.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org