This reroutes to my podcast.sidegigging.com/{filename} via cname.
But it doesnt work in Podlove.
Weird thing is if I type the url with http in the browser, it redirects to the podcast home page as set in podlove.
If I type it without the http it opens the mp3!!??
[2015-05-22 10:58:48] Unexpected http response when trying to access remote media file. new-fontiers/MP3 Audio HTTP Status: 404
[2015-05-22 10:58:48] Curl Error: The requested URL returned error: 404 Not Found new-fontiers/MP3 Audio
[2015-05-22 10:58:48] Unexpected http response when trying to access remote media file. new-fontiers/MP3 Audio HTTP Status: 404
[2015-05-22 10:58:48] --- # Can't reach http://podcast.sidegigging.com/new-fontiers.mp3 --- # Please include this output when you report a bug url: http://podcast.sidegigging.com/new-fontiers.mp3 content_type: http_code: 404 header_size: 0 request_size: 214 filetime: -1 ssl_verify_result: 0 redirect_count: 0 total_time: 0.110379 namelookup_time: 0.014002 connect_time: 0.014682 pretransfer_time: 0.014707 size_upload: 0 size_download: 0 speed_download: 0 speed_upload: 0 download_content_length: -1 upload_content_length: 0 starttransfer_time: 0.11036 redirect_time: 0 certinfo: Array ( ) primary_ip: 54.231.16.68 primary_port: 80 local_ip: 10.167.171.35 local_port: 58073 redirect_url: php_open_basedir: php_safe_mode: php_curl: 1 curl_exec: 1
Can you explain what exactly you mean by “but it does not work in Podlove”?
I can’t reproduce the redirect behavior: the URL always delivers the MP3. There is no redirecting to podcast.sidegigging.com in place how I see it.
Please tell us how your media file base URL is set in Podlove Publisher. It should probably be https://s3.amazonaws.com/podcast.sidegigging.com/ but is probably set to http://podcast.sidegigging.com/new-fontiers.mp3.
Hey Tim, you’re a legend!
I see now that I attached the file using the http I copied in and it actually resolved to a different url than I was expecting. Weird.
Anyway, I updated the settings/media URL to https://s3… as above and it didn’t resolve the issue.
Currently I only get a database error. If you are seeing the player twice you are probably using a template twice or have it included twice in the template.
So aweseome! That’s what it was, I read in a comment on the forum to add the shortcode to the page, but the template had already added it.
The last thing and everything is perfect: http://sidegigging.com/podcast/
I am getting some components of the player on this page. Its the “episodes” page and the podcast landing page in the Expert settings.
It has the first episode listed, then underneath it says: “MP3 Audio [8 MB]DownloadShow URL” in plain text.
Sorry, dass ich den alten Thread aufmache aber ich habe ein ähnliches Problem bzw die selbe Fehlermeldung.
Vor ein paar Tagen lief alles noch reibungslos. Letzten Dienstag wollte ich eine neue Episode online stellen und trotz vorhandener Datei und entsprechendem Media File Slug findet er die Dateien nicht.
im nginx error log steht nur immer: "2015/09/13 20:54:52 [alert] 5669#0: worker process 5708 exited on signal 11 (core dumped)"
Dateirechte sind auch unverändert: Owner ist www-data:www-data und hat Lese-Rechte
Wäre sehr froh wenn mir jemand einen Tipp in die richtige Richtung geben könnte.
Danke im Voraus.
Gruß Dawit
(habe in den FAQ und Community Guidelines nichts gefunden, falls ich besser in Englisch fragen soll würde ich es nochmal umformulieren.)
Danke, hat sich erledigt.
war ein Bug im nginx.
musste in der sites-available Datei beim 443 server folgende Zeile hinzufügen:
ssl_session_cache shared:SSL:10m;
