I saw this same issue with the Overthinking It Podcast at http://feeds.overthinkingit.com/otipodcast , which is hosted on the Feedpress network. Exact same error code and message.

My theory is that, about a month ago, this URL responded with an HSTS header, meaning that all traffic was required to be forwarded to HTTPS. This HSTS header is no longer present in the server response headers, but both MediaMonkey and Firefox remembered the HSTS setting. Unfortunately, the server does not have a valid SSL certificate for that server name, and so we get an SSL error.

In Firefox, this HSTS preference survived even after wiping out site cookies, storage, preferences, and permissions. Only after clearing out the Firefox profile file SiteSecurityServiceState.txt then restarting Firefox did this behavior fix itself.

I can't find a similar fix for MediaMonkey. I can't actually confirm if MM is caching this HSTS header or not. I couldn't find much in mm.db or in the profile directory that might store this setting. I'm only guessing that, based on the timing of seeing the HSTS issue in Firefox, MediaMonkey is somehow affected with the same behavior.

I'm running MediaMonkey v4.1.10.1778 on Windows 7 64-bit w/SP1.

http://www.ventismedia.com/mantis/view.php?id=13071

Bump: I am having this exact same issue.

Hello all,

Since the latest MediaMonkey update, I've started getting a consistent error from the Penny Arcade podcast feed. The feed URL is:

[url]https://www.penny-arcade.com/feed/podcasts[/url]

I am able to get a 200 OK response back, both from Chrome and from the Postman REST analyzer plugin, but Media Monkey consistently gives me the following error dialog:

[quote]https://www.penny-arcade.com/feed/podcasts - Error connecting with SSL.
Error connecting with SSL.
error:14094438:SSL routines:SSL3_READ_BYTES:tlsv1 alert internal error[/quote]

It is unclear to me whether this is an error returned by the server, or an internal error produced by the MediaMonkey client. I am using Standard Edition 4.1.10.1778. Looking at the response header fields in Postman, the only thing that jumps out at me is that Penny Arcade's response "expires" field is showing "Wed, 30 Dec 2015 09:01:00 GMT", but I thought I'd mention anyway in case this issue has been popping up elsewhere.