Unexpected http response when trying to access remote media file

Podlove Publisher
1

Hi there;

I am just trying to create my first episode. The MP3 File I have uploaded is there, I can render it on the server, and the asset is linking in the list of Assets, but it will not verify. In the Podlove support error list I get :

Unexpected http response when trying to access remote media file.
Details =
Media_file_id = 3
http:0

Can someone advise how to fix this?

Thanks

2

You could give us some URLs of your website, your audio file and the printout from Podlove > Support menu.

3

Hi Eric

Thanks for offering to help:

The site URL is

http://dev.rootsofempathy.org/podcast
The MP3 File is here:

SPECS:

Website http://dev.rootsofempathy.org
PHP Version 5.4.16
WordPress Version 4.7.7
WordPress Theme Roots of Empathy v1.0
WordPress Database Charset utf8
WordPress Database Collate
Publisher Version 2.6.2
Web Player Version 2.1.1
Twig Version 1.33.0
open_basedir ok
curl Version 7.29.0
iconv available
simplexml ok
max_execution_time 30
upload_max_filesize 2M
memory_limit 256M
disable_classes
disable_functions
permalinks ok (/%postname%/)
podlove_permalinks ok
podcast_settings ok
web_player ok
podlove_cache on
assets

0 errors
0 notices
Nice, Everything looks fine!

ERRORS:

2017-11-22 20:41:22 All assets for this episode are invalid! Episode 1
2017-11-22 20:42:15 Curl Error: Connection timed out after 3002 milliseconds episode-1/MP3 Audio toggle details
2017-11-22 20:42:15 Unexpected http response when trying to access remote media file. episode-1/MP3 Audio HTTP Status: 0 toggle details
2017-11-22 20:42:18 Curl Error: Connection timed out after 3001 milliseconds episode-1/MP3 Audio toggle details
2017-11-22 20:42:18 Unexpected http response when trying to access remote media file. episode-1/MP3 Audio HTTP Status: 0 toggle details
2017-11-22 20:42:18 Can’t reach http://dev.rootsofempathy.org/wp-content/uploads/feed/episode-1.mp3

=========

Let me know if you need any other details.

Thanks,
David

4

Looking good from here. The enclosure in the feed can be reached an played. Maybe a DNS issue on you host that your server cannot resolve its own URL. You could try asking your hoster/admin about it if the issue does not go away.