signal:// notifications - Can ssl verification of apprise be disabled (CERTIFICATE_VERIFY_FAILED for self-hosted servers)

[smaktacular]

Title says it all I think. Can I disable SSL Verification, so I can send notifications to my self hosted signal api? If yes, how can I configure that?

Edit: Now that I have some spare time I'll add a few details here:

I'm trying to send a notification to my signal api from a docker container and get the following error:

2023-01-21 10:15:36,316 - DEBUG - Socket Exception: HTTPSConnectionPool(host='***', port=443): 
Max retries exceeded with url: /v2/send 
(Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: 
self signed certificate (_ssl.c:997)')))

[smaktacular]

Another way could be, instead of disabling ssl verification, adding my own CertificateAuthority to the docker image

ADD roots.pem /usr/local/share/ca-certificates/roots.crt
RUN chmod 644 /usr/local/share/ca-certificates/roots.crt && update-ca-certificates

and building it myself

edit: did not help, seems like python is using it's own ca store

[dgtlmoon]

does adding ?verify=no or &verify=no work? let me know and I'll add that tip to the UI

[smaktacular]

?verify=no
works.

Thanks!

[dgtlmoon]

@smaktacular super cool, help us out by spreading the word about changedetection.io :)

[Chiller2019]

Where to put this ?verify=no?

[smaktacular]

At the end of the apprise url for the notification. e.g. signals://signalApi/senderNo/targetNo?verify=no