This repository has been archived by the owner on Jun 9, 2021. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 75
Cannot send notifications to internal https server that uses a self-signed certificate #353
Comments
Thanks for getting back to me. I was not aware of that setting. After checking the 'Accept any certificate' box in the configuration, we are now seeing a different error:
|
Yes, I googled that. Unfortunately, that didn't do me much good. I didn't find much (if any) helpful information, at least none that I could interpret. I'm not any kind of an SSL expert, so it wasn't clear to me if I need to do something on my Bitbucket server or not, or if the user needs to configure something on the server receiving the notification. |
Perhaps a change is needed in the plugin. Found this: https://stackoverflow.com/questions/39762760/javax-net-ssl-sslexception-certificate-doesnt-match-any-of-the-subject-alterna |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We are trying to use PR Notifier to send a notification to an internal https server that uses a self-signed certificate, but we are receiving this error in the Bitbucket log:
Is it possible to use a self-signed certificate on the destination server?
We are using PR Notifier version 4.1 with Bitbucket 5.16.2
Thanks.
-Kent
The text was updated successfully, but these errors were encountered: