Troubleshooting firewalls


#1

My domain is:
wedpics.mooo.com

I ran this command:
certbot --authenticator webroot --webroot-path=/var/www/letsencrypt --installer nginx --email xxxxx@yyyyyy.zzz --non-interactive --domain wedpics.mooo.com --agree-tos

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer nginx
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for wedpics.mooo.com
Using the webroot path /var/www/letsencrypt for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. wedpics.mooo.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://wedpics.mooo.com/.well-known/acme-challenge/5CC5HIR22xzyRqZzUnqKJodDNFsy6R9x9VssVoew3Pk: Timeout during connect (likely firewall problem)

IMPORTANT NOTES:
 - The following errors were reported by the server:

   Domain: wedpics.mooo.com
   Type:   connection
   Detail: Fetching
   http://wedpics.mooo.com/.well-known/acme-challenge/5CC5HIR22xzyRqZzUnqKJodDNFsy6R9x9VssVoew3Pk:
   Timeout during connect (likely firewall problem)

   To fix these errors, please make sure that your domain name was
   entered correctly and the DNS A/AAAA record(s) for that domain
   contain(s) the right IP address. Additionally, please check that
   your computer has a publicly routable IP address and that no
   firewalls are preventing the server from communicating with the
   client. If you're using the webroot plugin, you should also verify
   that you are serving files from the webroot path you provided.

My web server is (include version):
nginx/1.14.0

The operating system my web server runs on is (include version):
debian stretch (9)

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know):
yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
no

I am starting to consider networking a form of voodoo.
I ran:

$ nmap wedpics.mooo.com

Starting Nmap 7.40 ( https://nmap.org ) at 2018-05-17 21:53 CEST
Nmap scan report for wedpics.mooo.com (80.219.237.67)
Host is up (0.0051s latency).
rDNS record for 80.219.237.67: 80-219-237-67.dclient.hispeed.ch
Not shown: 997 filtered ports
PORT    STATE SERVICE
22/tcp  open  ssh
80/tcp  open  http
443/tcp open  https

And then logged in via ssh. When visiting the webpage, I am forced to use https and there is a tls handshake failure (of course). I seem to be running in circles. Any help would be greatly appreciated.

Cheers,
Brian


#2

Hi @oneyb,

I can’t access your site at all in HTTP or HTTPS, which makes me think that the error message is probably right—there may be a firewall preventing the general public from reaching your site. Have you tried accessing it from somewhere other than the local network?


#3

Hi Seth,

thanks for the quick reply.

/org.kost.nmap.android.networkmapper/bin/nmap wedpics.mooo.com -Pn

Starting Nmap 7.31 ( https://nmap.org ) at 2018-05-18 01:12 CEST

mass_dns: warning: Unable to open /etc/resolv.conf. Try using --system-dns or specify valid servers with --dns-servers

mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns-servers

Nmap scan report for wedpics.mooo.com (80.219.237.67)

Host is up (0.063s latency).

Not shown: 998 filtered ports

PORT STATE SERVICE

80/tcp open http

443/tcp open https

Nmap done: 1 IP address (1 host up) scanned in 113.76 seconds

Strangely, it missed the open ssh port…voodoo.

I have port forwarding enabled.

HTTP from a browser doesnt work. The error is correct of course, but I’m stuck correcting it.


#4

I see something different:

PORT    STATE    SERVICE
80/tcp  filtered http
443/tcp filtered https

So, what kind of connection are you running your nmap scan from?


#5

That one was from a broadband mobile connection.


#6

Well, I think there must be a firewall of some sort somewhere, as I’ve tried from two different ISPs and gotten “filtered” as seen from both of them!


#7

Yes, of course. Do you have any ideas how to identify where the filtering is happening?

What further confuses me is (edited for security):

$ ssh eweser@wedpics.mooo.com
Linux box 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu May 17 22:01:47 2018 from
~ $

So ssh is not a problem. My ISP says to do port forwarding in the router, which I have done for both 80 and 443.


#8

Are you somehow using the same ISP that’s hosting this server?


#9

The subdomain is registered with afraid.org. I am hosting it here at home. So, no, I am not. Well… yes technically, I am.


#10

Is that ISP also the broadband ISP that you used for port scanning, or a different one?


#11

I am pretty sure that’s not the case. The broadband mobile is provided by a different company, I think. Why do you ask? You are wondering why you see a different internet that I do?


#12

Yes, exactly. I imagine that the Let’s Encrypt CA is ending up with effectively the same view of your server that I have (in which these ports appear as filtered and don’t respond to the TCP connection), so I wonder why that’s true for some Internet users but not from your perspective on the Internet.


#13

True…

His server IP 80.219.237.67 and all IPs in that range have port 80 blocked.

@oneyb Can you try hook your server on to your home broadband and try if that work? Cause the ISP you use now has port 80 blocked.

Thank you


#14

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.