If I try to fetch this resource (CSS file) with my browser(s):
I get this error:
This Connection is Untrusted
You have asked Firefox to connect securely to secure.skypeassets.com, but we can't confirm that your connection is secure.
Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified. What Should I Do?
If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue.
However, if I connect my ethernet cable directly to my cable modem, instead of going through my router, I can access this resource without any problem.
So it seems to me that the problem is a router setting, not network settings for the computer itself.
The router is a D-Link DIR-632 Wireless N 8-Port Router. The problem is seen on computers connected via ethernet cable and computers connected via wireless. The router says that the firmware is up-to-date.
I see this problem with all pages at skype.com (no CSS files are getting fetched, and so all pages look pretty ugly). Other HTTPS traffic is fine. It has been happening for as long as I can remember, but I'm not sure if it has always happened with this router.
Selecting "ADVANCED" shows me this:
This server could not prove that it is secure.skypeassets.com; its security certificate is not trusted by your computer's operating system. This may be caused by a misconfiguration or an attacker intercepting your connection.
Proceed to secure.skypeassets.com (unsafe)
I have been asked to provide the certificate. There were lots of options when I went to save it, and I'm not sure I've done it correctly, but it is zipped up here. (I think it was saved when visiting
www.skype.com, which was badly-formatted because it couldn't access the CSS files from
secure.skypeassets.com. But I gather now that I did that wrong ... I should have saved the certificate when I was at the "Your connection is not private" page. Oops. I could go and get the other certificate now if it might help, but I'm not sure now if that was a red herring, in light of the problem being fixed by changing my DNS servers.)