search

DanielDent / docker-nginx-ssl-proxy

SSL Front-End Proxy With Automatic Free Certificate Management
https://hub.docker.com/r/danieldent/nginx-ssl-proxy/
Other
204 stars 68 forks source link

.app domains #9

Closed shoooe closed 6 years ago

shoooe commented 6 years ago

I'm trying to use this docker image likes this:

  nginx-ssl-proxy:
    image: danieldent/nginx-ssl-proxy
    environment:
      UPSTREAM: 127.0.0.1:5000
      SERVERNAME: x.app
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - "/etc/letsencrypt"

but for my x.app domain I get:

Failed authorization procedure. x.app (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://x.app/.well-known/acme-challenge/Uutj...

I have a feeling this is because .app is one of the first TLDs domains with HTTPs "baked in".

Is this true? If so, what can I do to make it work?

DanielDent commented 6 years ago

I don't think HTTPS preload for the TLD has anything to do with the issue you are having - the ACME protocol used to issue the certificate does not involve a web browser.

I'd look elsewhere, e.g. checking that your DNS entry is in fact pointing at the server where you are operating this docker image.

shoooe commented 6 years ago

The DNS A record was pointing correctly to the server, but the AAAA record (IPv6) was not and that was the issue, for some reason.

I just enabled IPv6 on my droplet and linked it correctly with 1and1.

Sorry for bothering you.