---
title: "Skip SSL certificate validation set per instance"
canonical: "https://support.appfire.com/space/JENK/1971290116/Skip%20SSL%20certificate%20validation%20set%20per%20instance"
format: markdown
---
Overview To provide more flexibility and control, the configuration settings for skipping SSL certificate validation have been moved from the  General Settings  of the hook configuration to Jenkins instances settings. With this change, the option is now configurable per individual instance, allowing for more precise security settings. Each Jenkins instance can now have its own SSL validation configuration. This provides better security management by allowing selective SSL validation bypassing instead of applying on each hook.  You might want to use this option if you receive webhooks at an HTTPS endpoint that's using a self-signed SSL certificate. However, because self-signed certificates are inherently not secure,  don't skip certificate validation unless: You can't install a valid SSL certificate that a public certificate authority has signed You're not concerned about the security of your webhooks. Instructions  Log into your Bitbucket instance as an Administrator. Navigate to the location of the appropriate settings: Global settings:  Administration  icon( ) >  Jenkins Servers . Project level: Select a project >  Projects  >  Settings  >  Webhook to Jenkins for Bitbucket .  Repository level: Select a repository >  Repositories  >  Settings  >  Webhook to Jenkins for Bitbucket . Click the  Edit  icon ( ) next to the Jenkins instance you want to modify. Tick the  Skip SSL Certificate Validation  option.  Sometimes, self-signed certificates cause the client (Bitbucket) to deny all Jenkins requests. When selected, this option allows all certificates to be accepted, including self-signed certificates. Typically, you would use it in test environments. Click  Save .  Impact on existing configurations If you previously had  Skip SSL Certificate Validation  enabled in  General Settings , it will still apply to all hooks. We recommend disabling it in general settings and enable on the Jenkins instance level. All new Jenkins instances have SSL certificate validation enabled by default unless explicitly changed.