Always says it’s down if site uses self-signed certificate / (and also mismatching hostname) #57
-
It always says it’s down when site cert is not trusted. |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments
-
Can you share a link to your site? Let me see why it doesn't like your certificate. :) |
Beta Was this translation helpful? Give feedback.
-
This is now fixed, you can use the sites:
method: GET
url: https://desktop.sjang.dev:2364
__dangerous__insecure: true Setting the |
Beta Was this translation helpful? Give feedback.
-
Hi @AnandChowdhary and sorry for reviving this issue. Can you maybe check if this flag also makes upptime ignore certificate name mismatches? I have a special case where I can't change the certificate but still would like to test availability and the check endpoint step in the uptime action is giving me |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Thanks, @SJang1! Let me add an option for that as well. 😄 |
Beta Was this translation helpful? Give feedback.
-
@wtfpeter, you can now add the sites:
method: GET
url: https://desktop.sjang.dev:2364
__dangerous__disable_verify_host: true |
Beta Was this translation helpful? Give feedback.
-
Hmm.. it is an also insecure option, how about changing to VERIFYPEER and VERIFYHOST both into __dangerous__insecure option? (curl --insecure command on linux works like that too) |
Beta Was this translation helpful? Give feedback.
-
Ok, I've added an update that works like this:
|
Beta Was this translation helpful? Give feedback.
-
Thanks a lot for the quick reaction, I can confirm both |
Beta Was this translation helpful? Give feedback.
This is now fixed, you can use the
__dangerous__insecure
configuration key in your sites:Setting the
__dangerous__insecure
option setsSSL_VERIFYPEER
asfalse
. I've added the__dangerous__
prefix to this key to remind people that they should only be setting this astrue
if they're sure about it!