Cant connect to my domain

#1

Hi, im trying to setup a reverse proxy with Caddy but when trying to connect to my domain to test it I keep getting:

“Activating privacy features… 2019/01/20 13:46:10 [INFO] [carltronix.com] acme: Obtaining bundled SAN certificate
2019/01/20 13:46:11 [INFO] [carltronix.com] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/piB72alrMP7lGIxlw63UT6Nb19PGYp3s9fHr1rvk5Tw
2019/01/20 13:46:11 [INFO] [carltronix.com] acme: use tls-alpn-01 solver
2019/01/20 13:46:11 [INFO] [carltronix.com] acme: Trying to solve TLS-ALPN-01
2019/01/20 13:46:17 [carltronix.com] failed to obtain certificate: acme: Error -> One or more domains had a problem:
[carltronix.com] acme: error: 403 :: urn:ietf:params:acme:error:unauthorized :: Cannot negotiate ALPN protocol “acme-tls/1” for tls-alpn-01 challenge, url:”

I have added all the required records on cloudflare, I have forwarded ports 80 and 443 to my domain IP, I dont know what the problem is. any help would be greatly appreciated cheers.

#2

Any IP blockings in place?

Allow this networks:

#3

no mate. i turned off firewall. This is how Ive set up my CloudFlare DNS records and I have saved the cloudflare nameservers to my Domain registrar. Im at a loss

#4

I am not quite sure about what the actual problem is.

The domain is properly set up and does point to Cloudflare’s proxy, however when Cloudflare attempts to connect to your server it times out as it doesnt get a response.

So far so good, the output you posted refers to the issuance of a LetsEncrypt certificate and is not necessarily linked to the problem at hand. I am not familiar with Caddy but it appears you dont want Cloudflare to connect straight to your webserver, but to that reverse proxy, which then in turn connects to the webserver. Is that right?

If it is, you should check if maybe Cloudflare can connect to your reverse proxy, but that proxy cant connect to the webserver. Generally speaking, do you really need that reverse proxy setup? It simply complicates things.

Maybe Community Tip - Fixing Error 522: Connection timed out can give you some ideas.

#5

I’m currently having the exact same issue using the same same stack.

Using Caddy and getting the same error.

EDIT: Looks like it fixed itself after I gave the domain some time (24h). It was a newly registered domain.

closed #6

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