Python JIRA library connection issues when retrieving issue information

Other Questions Jira
1

I need help connecting to JIRA using the Python JIRA library to get issue details. My code keeps failing with SSL errors.

from jira import JIRA
import ssl

server_config = {
    'server': 'https://company-jira.domain.com:8443/', 
    'verify': '/path/to/certificate.pem'
}
jira_client = JIRA(server_config, basic_auth=('my_user', 'my_password'))

When I run this I get SSL certificate errors like _ssl.c:2747 and connection timeouts. The script tries to retry 3 times but always fails on the serverInfo endpoint.

If I set 'verify': False in the config, I get urllib3 warnings about unverified HTTPS requests but no actual connection.

Has anyone dealt with similar certificate issues when connecting to JIRA? What am I doing wrong with the SSL setup?

2

This usually means your cert file isn’t in PEM format or you’ve got the wrong path. First, convert your certificate to PEM format with openssl if you need to. You might also be missing intermediate certificates - make sure your PEM file has the complete certificate chain. I’ve seen this break when the server URL doesn’t exactly match the certificate’s common name too. Check that they match up. Corporate firewalls can also mess with this by intercepting the connection and breaking the SSL handshake, even when your certs are correct.

3

had the same prob a while ago with our jira too. i added options={'verify': False} to the jira init instead of that server config. also check for any proxy settings ur company might use, that helped me. u might also wanna update ur ssl context.

4

Had the same SSL headaches with JIRA. Usually it’s Python’s SSL context, not the cert itself. Import ssl and create a context with ssl.create_default_context(), then set check_hostname=False if your internal domains don’t match the certificate. Also check if your JIRA server needs specific TLS versions - some corporate setups disable certain protocols, so you might need to specify the TLS version in your SSL context. Make sure your cert file has the full chain with intermediate certificates, not just the server cert.