Multiple urls for one container

My traefik is splitted into 4 entrypoints: http, https, http-external and https-external.

Some services are only accessible locally, other are also accessible externally.

For the local services I access them using myservice.home.
For the services accessible externally, url is myservice.mydomain.com.

For the services that are accessible both locally and externally, is it possible to have both urls? So that I can access them locally but also externally when needed.

Here are my labels for a service I'm accessing externally:

      - traefik.enable=true
      - traefik.http.routers.myservice.entrypoints=http-external
      - traefik.http.routers.myservice.rule=Host(`myservice.mydomain.com`)
      - traefik.http.middlewares.myservice-https-redirect.redirectscheme.scheme=https
      - traefik.http.routers.myservice.middlewares=myservice-https-redirect
      - traefik.http.routers.myservice-secure.entrypoints=https-external
      - traefik.http.routers.myservice-secure.rule=Host(`myservice.mydomain.com`)
      - traefik.http.routers.myservice-secure.tls=true
      - traefik.http.routers.myservice-secure.service=myservice
      - traefik.http.services.myservice.loadbalancer.server.port=1234
      - traefik.docker.network=external_proxy

I need to add my http entrypoint and also needs to add the myservice.home host but not sure how to do it and if it's possible.

You can use multiple Host() in one rule:

.rule=Host() || Host()

You can define multiple pairs of routers/services on a Docker service (which is the way to go if you require different middlewares).

Note that by default all entrypoints are used by a router, you can then select/limit which ones you really want to use.

Further note that not all web GUI targets like to be available on any domain, some will always redirect to the original configured one.

ususally it makes no sense to expose an application using different internal and external fqdn. As bluepuma77 stated already some applications might redirect to a "default" URL other might reject access on a "wrong" domain.

Other issues arise as well - if your "internal" domain is not accessible from the internet yu can not issue public TLS certificates for this domain. I'm under impression traefik will request TLS certs for all exposed FQDNs so the request may fail completely. I would recommend to access publicly available server using public FQDN only and use "split brain DNS/split horizon DNS" for internal access. and only use "internal"entrypoint for application not exposed to the public.