# Configure a HTTPS Service

**URL:** <https://community.traefik.io/t/configure-a-https-service/17755>\
**Category:** Traefik v2\
**Tags:** file\
**Created:** [March 2, 2023, 11:15pm UTC](https://community.traefik.io/t/configure-a-https-service/17755 "2023-03-02T23:15:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![9Mad-Max5](https://sea2.discourse-cdn.com/flex020/user_avatar/community.traefik.io/9mad-max5/32/1181_2.png) [@9Mad-Max5](https://community.traefik.io/u/9Mad-Max5)\
**Post date:** [March 2, 2023, 11:15pm UTC](https://community.traefik.io/t/configure-a-https-service/17755/1 "2023-03-02T23:15:57Z")

</div>

Hi together,

I searched like everywhere but didn't find any information.  
Even in the GitHub from traefik, but didn't find an answer how to configure a HTTPS service.  
The reason is that proxmox web browser is usually on HTTPS.  
I have no idea how to make a route there.

---

<div class="post-metadata">

**Author:** ![bluepuma77](https://avatars.discourse-cdn.com/v4/letter/b/a9adbd/32.png) [@bluepuma77](https://community.traefik.io/u/bluepuma77)\
**Post date:** [March 3, 2023, 10:03am UTC](https://community.traefik.io/t/configure-a-https-service/17755/2 "2023-03-03T10:03:08Z")

</div>

Complicated topic, as there are multiple options.

Simple solution is to use Traefik to terminate TLS and forward plain-text. Some services require TLS/SSL, but they are happy when you send a special header telling them that originally TLS was used.

If you service really wants to use a certificate and you have a static cert (configured for Traefik and the service), then Traefik can just forward encrypted requests, use `tls.passthrough`.

If your service creates its own custom cert, you need to let Traefik [trust them](https://doc.traefik.io/traefik/routing/services/#certificates). Or set a global `serversTransport.insecureSkipVerify: true` or a [dynamic serverstransport](https://doc.traefik.io/traefik/routing/services/#insecureskipverify) and assign it to the service.

If the service wants to create its own LetsEncrypt, then your service should use httpChallenge or dnsChallenge, as tlsChallenge will probably not be forwarded by Traefik. But with httpChallenge you probably have a chicken-and-egg problem and need to enable `insecureSkipVerify` at least for the initial validation of the first cert.