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 <padmahas@xxxxxxxxx>
> To: users <users@xxxxxxxxxxxxxxxx>
> Subject: Re: 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
> <otis.dewitt@xxxxxxxx.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@xxxxxxxxxxxxxx> 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 <padmahas@xxxxxxxxx>
>>> >>
>>> >> 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
>>> >> <monahbaki@xxxxxxxxx> wrote:
>>> >>
>>> >>> Check firewall
>>> >>>
>>> >>> On Tue, Jan 14, 2020 at 10:43 AM Richard <
>>> >>> lists-apache@xxxxxxxxxxxxxxxxxxxxx> 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 <padmahas@xxxxxxxxx>
>>> >>>>>
>>> >>>>> 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@xxxxxxxxxxxxxxxx For additional commands,
>>> >>>> e-mail: users-help@xxxxxxxxxxxxxxxx
>>> >>>>
>>> >>>>
>>> > ------------ End Original Message ------------
>>> >
>>> >
>>> >
>>> > ---------------------------------------------------------------
>>> > ------ To unsubscribe, e-mail:
>>> > users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands,
>>> > e-mail: users-help@xxxxxxxxxxxxxxxx
>>> >
>>>
>>>
>>> -----------------------------------------------------------------
>>> ---- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
>>> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
>>>
>>>
------------ End Original Message ------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|