mTLS fails to persist.

I’ve been trying to use mTLS with peekaping to monitor some internal services that require client certificates. I filled in the certificate, key, and ca fields within the UI with tested, valid data, but the monitor keeps failing with a “tls certificate required” error. After checking the logs, it looks like the app isn’t actually using any of the mTLS values I provided and all the cert fields show up as empty in the request.

`DEBUG executor/http.go:252 execute http cfg: &{Url:https:// Method:GET ... TlsCert: TlsKey: TlsCa:}`

`HTTP request failed: Commafeed, Get "https://sub.domain.com": remote error: tls: certificate required`

I have mtls terminating through traefik and do not use the included nginx block, but may try it for shits and giggles if it is believed to be user error.

Lastly, it seems like peekaping is either not saving the data from the UI, or just not passing it to the backend at all. With respect to not saving data, I also noticed that when going back to edit any of the services, all the settings I used are gone except for the URL and the monitor type. Tthe user is ultimately left with no idea what was set, especially if some time goes by. mTLS support was one of the reasons I was excited to try this out. Any help is appreciated. Thanks for your hard work!

The issue points to executor/http.go line 252 where TLS fields appear empty. Start by examining how the UI submits mTLS certificate data and how it's stored and retrieved. Check the database schema and the HTTP request configuration flow to see where the values are dropped. Verify by setting up a local test with a service requiring mTLS and tracing the data from UI to request.

Escrito por el modelo de indexación a partir del texto del issue.