Use Traefik with Lets Encrypt and Docker ?

no particular reason I just followed the tutorial because I spent a lot of time before it worked and I ended up following the tutorial to the letter (before I tested with version 2.1 of traefik and I could not achieve what I wanted.)

But by changing in the traefik.toml you can probably reset the HttpChallenge I have not tested.

tinh_x7 during the setup/testing stage you should change the letsencrypt caserver to increase the rate limit:

settings for traefik v1.7 and traefik v2.1 and the letsencrypt info site

Zitat von tinh_x7

I’m currently using NoIp...

If you mean noip.com then you are out of luck.. according to there website you cant get a ssl certificate for a no-ip hostname

If you did change the letsencrypt caServer than this is expected behaviour. The Staging Environment is meant for setup and testing, please see the documantation

considering the signing of the certificate I think you switched to using the LE test environment which explains your certificate

I use grafana but not through Traefik

I misspoke, i use grafana only with my local network or through the VPN

tinh_x7 i have no idea what you are doing... please show your traefik configs static and dynamic.

Edit: and your traefik log file during startup i would like to see how you got your certificate issued.

both your servies point to "media.abcxyz.com" how should traefik know which one you want?

why did you activate the docker provider if your setup is provided from the file provider? ... or did you setup yout traefik via docker labels?

no it is not wrong but maybe unnecessary:

with the following yml block you activated the docker provider:

  docker:

an with

exposedByDefault: false

you told traefik to not automatically add all active docker containers.

if your emby and or plex services are docker containers you could add them via traefik labels like so (assuming you use a compose file):

(personally i would use labels if possible)

    labels:
        - "traefik.enable=true"
       # - "traefik.docker.network=proxy_web"
        - "traefik.http.routers.plex.rule=Host(`plex.abczyz.com`)"
        - "traefik.http.routers.plex.tls=true"
        - "traefik.http.routers.plex.tls.certresolver=le"
        - "traefik.http.routers.plex.entrypoints=https"
       # - "traefik.http.routers.plex.middlewares=logins@file"
        - "traefik.http.services.plex.loadbalancer.server.port=32400"

since you are using traefik v2.2 i would also add the newly added default redirectionfor http => https:

this goes in your static configuration

entryPoints:
  http:
    address: :80
    http:
      redirections:
        entryPoint:
          to: https
          scheme: https

  https:
    address: :443

you should also set you log level to DEBUG i may reveal some insight and remove the whole metrics block until your services work.

EDIT:

my bad to active the docker provider via static file config you need: docs.traefik.io

  docker:
  endpoint: "unix:///var/run/docker.sock"

Zitat von tinh_x7

I got the LE cert valid for Traefik site, but the dashboard only load if it's in private mode Chrome.

I have my external services (Plex, Emby) green status in Traefik dashboard, but they can't be access externally.

Code

Your connection isn't private
Attackers might be trying to steal your information from media.abctest.com (for example, passwords, messages, or credit cards).
NET::ERR_CERT_REVOKED

Just in case you have opened ports 80 and 443 to your traefik container ?

Zitat von coffinbearer

if your emby and or plex services are docker containers you could add them via traefik labels like so (assuming you use a compose file):

(personally i would use labels if possible)

Code

    labels:
        - "traefik.enable=true"
       # - "traefik.docker.network=proxy_web"
        - "traefik.http.routers.plex.rule=Host(`plex.abczyz.com`)"
        - "traefik.http.routers.plex.tls=true"
        - "traefik.http.routers.plex.tls.certresolver=le"
        - "traefik.http.routers.plex.entrypoints=https"
       # - "traefik.http.routers.plex.middlewares=logins@file"
        - "traefik.http.services.plex.loadbalancer.server.port=32400"

since you are using traefik v2.2 i would also add the newly added default redirectionfor http => https:

this goes in your static configuration

Code

entryPoints:
  http:
    address: :80
    http:
      redirections:
        entryPoint:
          to: https
          scheme: https

  https:
    address: :443

Alles anzeigen

you should also set you log level to DEBUG i may reveal some insight and remove the whole metrics block until your services work.

Alles anzeigen

in traefik version 2.x redirection http to https works easily ?

you no longer have to go through middleware as indicated here https://github.com/containous/traefik/issues/4863

Methy yes with traefik v2.2 a default entrypoint got added for it. traefik.docs and github commit

tinh_x7 as far as i can see you only changes schemes i'm talking about "HTTPS redirection (80 to 443)"