Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements


  • Give kudos
  • My kudos


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

REST api using token ow gives SSL error

I am using


When I first ran it, after generating a JIRA API Token, it worked fine.  However, now I am getting an error like this:

  • urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='', port=443): Max retries exceeded with url: /rest/api/3/worklog/updated?since=1601801936618 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1076)')))


I even tried generating a brand new token, and it doesn't work with that either.


Any ideas?



2 answers

1 accepted

2 votes
Answer accepted

Hi @Larry Weisberg ,

If I understand correctly you are trying to call a Jira Cloud REST API endpoint using and this is now returning an SSL error, while it was working fine before.

If this is correct, can you please check the following:

  1. In the script you have only entered your email address as the username and the API Token associated to it. You left all the other values set to "none"
  2. You are able to call the same endpoint successfully using Curl. If this does not work please add the -D- argument and paste the response in here (replace : <EMAIL-ADDRESS>, <API-TOKEN>, <NAME> and <TIMESTAMP> with the appropriate values):
    curl -u <EMAIL-ADDRESS>:<API-TOKEN> -D- -X GET "http://<NAME><TIMESTAMP>"



Thanks @Dario B 

  1. Correct - I just call:
    client = JiraClient("", "TOKEN_XYXYXYXYX")
    If I add verify=False in the call to
    self._session.get(url) ...
    then it works.
  2. If I just do the http portion from Browser:

    then it works fine; but doing curl:

    curl -u -D- -X GET ""

    fails with:

    curl: (60) SSL certificate problem: self signed certificate in certificate chain
    More details here:

    curl failed to verify the legitimacy of the server and therefore could not
    establish a secure connection to it. To learn more about this situation and
    how to fix it, please visit the web page mentioned above.

    I guess not so surprising that curl behaves same way that Python does; what is most surprising is that when I ran it the first few times, I did not get errors..



Dario B Atlassian Team Oct 22, 2020

Hi @Larry Weisberg

This is super weird and a bit concerning at the same time, since we don't have any self-signed certificate in the certificate chain for Atlassian Cloud products.

You can double check this by using the SSLShopper Certificate Checker or any other tool to check certificates:

  • SSLShopper:

  • OpenSSL:
    openssl s_client -showcerts -servername -connect

    depth=2 C = US, O = DigiCert Inc, OU =, CN = DigiCert High Assurance EV Root CA
    verify return:1
    depth=1 C = US, O = DigiCert Inc, OU =, CN = DigiCert SHA2 High Assurance Server CA
    verify return:1
    depth=0 C = US, ST = California, L = San Francisco, O = "Atlassian Network Services, Inc.", CN = *
    verify return:1
    Certificate chain
    0 s:C = US, ST = California, L = San Francisco, O = "Atlassian Network Services, Inc.", CN = *
    i:C = US, O = DigiCert Inc, OU =, CN = DigiCert SHA2 High Assurance Server CA


Now, if this error is only happening from the command line but not from the browser, there are chances your OS is using some old/outdated CA store (maybe an old version of openssl was installed recently).

In order to doble-check this, please do the following:

  • Compare the certificate you get from the browser with the one you get from command line (you can use the openssl command in above example) in order to  make sure that's the same one and exclude there is anything weird going on.
  • Once verified the certificate is correct/the same, you should update the CA store used by your OS (or by python, if it's not the same).


For further details, you might want to see below links:



Thanks @Dario B - that sounds promising... Might not get to it till next week but I'll take a look, (assuming instructions on the links are clear enough :-), or maybe my IT guy can help out).



Hi @Larry Weisberg ,

The links are a bit random since I don't know which Operating System you use and which version of python. If you provide those details I will try to provide a more specific link.

Have a nice weekend!


Thanks @Dario B - I am using Python 3.7 on Windows 10.  As far as the certificates:

I had a few minutes today to run the openssl command above and got this:

Certificate chain
0 s:C = US, ST = California, L = San Francisco, O = "Atlassian Network Services, Inc.", CN = *
i:C = US, O = DigiCert Inc, OU =, CN = DigiCert SHA2 High Assurance Server CA
1 s:C = US, O = DigiCert Inc, OU =, CN = DigiCert SHA2 High Assurance Server CA
i:C = US, O = DigiCert Inc, OU =, CN = DigiCert High Assurance EV Root CA
Server certificate
subject=C = US, ST = California, L = San Francisco, O = "Atlassian Network Services, Inc.", CN = *

issuer=C = US, O = DigiCert Inc, OU =, CN = DigiCert SHA2 High Assurance Server CA

No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: ECDSA
Server Temp Key: ECDH, P-256, 256 bits
SSL handshake has read 3289 bytes and written 761 bytes
Verification: OK
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 256 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)


.. I got back 2 different certificates.  But it is not clear how to check what the certificate(s) is/are from the browser, so I wasn't able to compare...



Hi @Larry Weisberg ,

In order to get the certificate from the browser you can click on the padlock icon next to the url in the address bar:



Also, as already outlined, there is no self-signed certificate anywhere and therefore if this was working fine before and it is not working now then either the CA store used by Windows changed, or something is hijacking the connection.

 So, since you are able to reproduce the issue with CURL, can you double check the CA store used and the certificate returned by replacing the -D- switch with -vvv?

Please run the command and paste the output in your reply removing the sensitive content like in below example:

curl -vvv -u ""

* Trying
* Connected to ( port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs


* Server certificate:
* subject: C=US; ST=California; L=San Francisco; O=Atlassian Network Services, Inc.; CN=*
* start date: Nov 28 00:00:00 2019 GMT
* expire date: Jan 18 12:00:00 2022 GMT
* subjectAltName: host "" matched cert's "*"
* issuer: C=US; O=DigiCert Inc;; CN=DigiCert SHA2 High Assurance Server CA
* SSL certificate verify ok.


{"values":[],"since":1601798047737,"until":1601798047737..... [REMOVED] ...


Lastly, not sure if this helps, I can see that there is a python package named certifi that includes the Mozilla CA bundle. For details see:


Have a nice weekend.


Thanks - but something fascinating - I just tried to Python script again and it worked!!!  Apparently because this time I "forgot" to get onto the corporate VPN, which I am normally on..

@Dario B - 

  1. does this make sense/explain what my issue?
  2. Would it still be beneficial would for me to re-run the curl/openssl commands twice - once on VPN and once not?



Dario B Atlassian Team Oct 23, 2020

Hi @Larry Weisberg ,

Yes, that makes sense and I'd say that the mystery is solved (second scenario: 
something is hijacking the connection). :) 

Also, it can still make sense to compare the certificates you get when you use curl with and without the VPN, so that you can bring this issue to the attention of your IT department.



Thanks so much @Dario B - I'll follow up with my local IT.

Thanks everyone for their advice.  In the end, I just needed to copy the (Base 64) certificate for our VPN into "...\Python\Python37\Lib\site-packages\certifi\cacert.pem" and the REST API from Python worked like a charm.

Like # people like this
Dario B Atlassian Team Oct 27, 2020

Thanks for updating this thread with the final solution @Larry Weisberg ! 

Like Larry Weisberg likes this
1 vote

The SSL certificate your call is presenting to the server is not valid.  You will need to change to a valid certificate.

Thanks Nic!

I am using JiraClient from and basically my code does this:

    client = JiraClient("", "XYXYXYX") # Token value
recent_worklogs = client.retrieve_worklogs_updated_since( - timedelta(days=14))


JiraClient constructor does this:

class JiraClient:
def __init__(
username: str = None,
api_token: str = None,
access_token: str = None,
access_token_secret: str = None,
consumer_key: str = None,
key_cert: str = None,
self._user_url = os.getenv("JIRA_SERVER", "").rstrip("/")
self._base_url = f"{self._user_url}/rest/api/3"

if username and api_token:
self._session = requests.Session()
self._session.auth = (username, api_token)


And retrieve worklogs : 

   response = self._session.get(url) 


This is where failure occurs, where URL is just a REST api that does work from Browser; Also it used to work from this script.

Basically - where is the ssl Cert created, used in the code?  Why/How would it have changed?

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you