请教下，webhook有没日志可排查问题呢
我遇到的问题如下：
webhook的地址使用http的就正常接收
webhook的地址使用https就失效，地址刚更新，一动表格就失效
查了很久也找到了问题了，公司的网络增加了自签名证书，服务器需要信任自签名证书后才可以上网，已经在系统里update了，在docker里也关联了证书了
下面是从docker里curl 443的webhook地址，一切都正常，但是在界面里设置的同样地址就不行，我想着webhook是反向API，也需要ssl校验，但是设置了都不起作用
不知道seatable工程师能帮忙解释下不，提供下排查思路，谢谢。
docker exec -it seatable curl -v -X POST -H "Content-Type: application/json" -d '{"key":"value"}' https://********.com/webhook
Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying **.**.**.**:443...
* TCP_NODELAY set
* Connected to ********.com (**.**.**.**) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /usr/local/share/ca-certificates
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: CN=********.com
* start date: Feb 18 05:41:50 2025 GMT
* expire date: May 19 05:41:49 2025 GMT
* subjectAltName: host "********.com" matched cert's "********.com"
* issuer: C=CN; ST=****; L=****; O=*****; OU=****; emailAddress=****
* SSL certificate verify ok.
> POST /webhook HTTP/1.1
> Host: ********.com
> User-Agent: curl/7.68.0
> Accept: */*
> Content-Type: application/json
> Content-Length: 15
>
* upload completely sent off: 15 out of 15 bytes
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: openresty
< Date: Tue, 18 Feb 2025 09:36:29 GMT
< Content-Type: application/json
< Content-Length: 18
< X-Served-By: ********.com
< Age: 0
< Connection: keep-alive
< Via: https/1.1 ASWG ("SKG-UCSG")
<
{"success":'验证通过'}
* Connection #0 to host ********.com left intact