# (Potential) problems by letting Traefik handle https and using http to the backend

**URL:** <https://community.traefik.io/t/potential-problems-by-letting-traefik-handle-https-and-using-http-to-the-backend/16532>\
**Category:** Traefik v2\
**Tags:** letsencrypt-acme, docker\
**Created:** [November 21, 2022, 7:23pm UTC](https://community.traefik.io/t/potential-problems-by-letting-traefik-handle-https-and-using-http-to-the-backend/16532 "2022-11-21T19:23:58Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [November 21, 2022, 7:55pm UTC](https://community.traefik.io/t/potential-problems-by-letting-traefik-handle-https-and-using-http-to-the-backend/16532/2 "2022-11-21T19:55:13Z")

</div>

You are looking for solutions in Traefik for problems caused by nginx and PHP? 🤨

I would rather work on the root causes and let PHP accept plain http and make nginx not change the path. Maybe switch to Apache?

But it’s an interesting question about http2 if that only works over https/TLS. You could use a custom certificate for the internal connection and try `insecureSkipVerify`, see [post](https://community.traefik.io/t/confusion-over-basic-configuration/16497/4) how to use it.

---

_[View the full topic](https://community.traefik.io/t/potential-problems-by-letting-traefik-handle-https-and-using-http-to-the-backend/16532)._