Is this a wider issue? Images not displaying due to invalid certificate
Asked by Chris Rymer:

Over ther last few weeks I havbe noticed that images are not loading inside jira tickets. I have seen this before and figured it was some rules in F5 which were flagging up the conenctions as insecure.

Lately the issue has come back and I am seeting the placeholder icon where images should be, as below.

![jira-placeholder.png](https://community.atlassian.com/t5/image/serverpage/image-id/336672iCB9452D0EF8269FA/image-size/large?v=v2&px=999 "jira-placeholder.png")

The domain and path for the resource is:

<https://media-cdn.atlassian.com/us-west-1/v1/cdn/file>

I can see in the network tab that there is a cert error being reported

![cert error.png](https://community.atlassian.com/t5/image/serverpage/image-id/336673i5B76D78CA94644F8/image-size/large?v=v2&px=999 "cert error.png")

And if I go directly to the URL there it seems the cert is about to expire but I wouldn't have thought that would be a particular issue.

![cert-detail.png](https://community.atlassian.com/t5/image/serverpage/image-id/336676i173B4CC07C3EF3B8/image-size/large?v=v2&px=999 "cert-detail.png")  

The error seems to be prevalent in Firefox and Chrome latest versions.  

Anyone have experience of this, and how was it resolved if on an enterprise network where tinkering with security policies is restricted?

I have done some investigation and the problem is not limited to me just being on our corporate VPN, in fact the issue can manifest on either business or home networks and it is not consistent. Additionally I have ruled out any browser extensions which modify headers etc.

Interestingly perhaps is that when I use sslchecker to verify the cert it reports a different fate to the one in chrome.

![expire-chrome.png](https://community.atlassian.com/t5/image/serverpage/image-id/337282i7D2CDFB7BFDBF6EE/image-size/large?v=v2&px=999 "expire-chrome.png")

![expiry.png](https://community.atlassian.com/t5/image/serverpage/image-id/337280iF961D628B3F36E54/image-size/large?v=v2&px=999 "expiry.png")  

Also there is no organisation Unit. I am not sure if that is even important at this point, it seems to not be mandatory.   

*"Further, what constitutes a valid OU has been vague and arbitrarily defined by different Certificate Authorities (CAs). It has also been the only **non-mandatory** standard input field in Certificate Signing Requests."*

The main observation here is the date which seems odd it should be the same, in which case how can it be different. And it is still a valid date so the CERT should be fine.

It seems that those of us with the issue are being sent to media-cdn.atlassian.com whereas others are going to api.media.atlassian.com, so perhaps we are missing an update in our browsers from the PWA? I have tried to clear all caches and thought that was successful.


Answers:
author: Jonathan Rhodes
body: I am also experiencing the same issue. But it does not appear to be reported elsewhere in my organization.

comments: author: Chris Rymer
body: Welcome to the club! What OS?

Everyone I have spoke to with the same issue is on Mac. We use JAMF for locking down the machines also.

Windows machines seem to be fine. Even my windows VM works. So it is not my network or browser extensions as I use the same profile.


author: Chris Rymer
body: Odd that both dates from the Cert info in chrome have different dates. Cert expiry should be fixed and not move unless the cert is updated with a new expiry.


Tags: cloud

jira-cloud