Do the URLs of the mentioned resources inside the page actually begin with “https”? Any resource loaded with an “http” URL will be considered mixed content.
One hack/bandaid you can use is to include the following header in the offending page:
<meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests">
That will “encourage” the mixed resources to be loaded over “https” while you find the root causes.