Solved- Timeout - Possible NOOB errors

Help
#1

I am not sure where I am going wrong. I think it might be access to port 443 but I had it open on my router (natted), OSMC doesn’t have a firewall as far as I am aware.

My domain is: nchanga.com

I ran this command: sudo certbot-auto certonly -a webroot --webroot-path=/usr/share/nginx/html -d nchanga.com -d www.nchanga.com

It produced this output: Failed authorization procedure. nchanga.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://nchanga.com/.well-known/acme-challenge/b1wtQzhpBopD6sHYdTPA5xLEXMylU9YBUn2uSiSyhR0: Timeout, www.nchanga.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://www.nchanga.com/.well-known/acme-challenge/6H_t73-DtJg2Mngfz4DLPlSN1ajzSSm7SxJMGdPbHRI: Timeout

My web server is (include version): nginx

The operating system my web server runs on is (include version): OSMC

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

#2

nchanga.com resolves to the address 196.215.72.199. This does not answer connections to port 80.
You need to forward port 80, too.

#3

Strange this is I have forwarded port 80 and 443. My ISP claims it does not block these ports. My other non std natting seems to work.
I am not sure if telnet is a failed test but I can't telnet to 80 or 443.

#4

Well, there is a little difference: telnet to port 80 results in a timeout, telnet to port 443 results in "connection refused". Connection refused can be the result of a packet filter (firewall) or no service listening on that port.
Are you sure, your media center is listening on these ports?

#5

I have nginx running so at a minimum the default page to launch, it does on the LAN.

#6

http://downforeveryoneorjustme.com/nchanga.com
shows you down too.

#7

It turns out it is my shitty Tenda router that isn’t port forwarding correctly, I tried my old router and I was able to generate the certs. Many thanks for everyone’s help.

#8

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