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!

O problema aponta para a linha 252 de executor/http.go onde os campos TLS aparecem vazios. Comece examinando como a UI envia os dados do certificado mTLS e como eles são armazenados e recuperados. Verifique o esquema do banco de dados e o fluxo de configuração da solicitação HTTP para ver onde os valores são perdidos. Verifique configurando um teste local com um serviço que requer mTLS e rastreando os dados da UI até a solicitação.

Escrita pelo modelo de indexação a partir do texto da issue.