Episode not released: Curl Error: The requested URL returned error: 403 Forbidden

Podlove Publisher
1

Hello Community,
I’m having trouble with getting my latest podcast episode to the various streaming/publisher services: apple podcast, spotify, etc.

Here’s what I know:

  • wordpress.org site www.speakthescience.com hosted by dreamhost.com

  • I use Podlove to create episodes, and Media Cloud to take my mp3 files and store them to the storage provider S3 Amazon.

  • I was able to find the podcast mp3 in my s3 amazon “bucket”. The bucket is named mbjc and is set to public. The podcast episode’s or “object”'s S3 URI is s3://mbjc/2022/06/MBJC044.mp3 and Object URL is https://mbjc.s3.us-west-2.amazonaws.com/2022/06/MBJC044.mp3

  • Media Cloud has the storage provider set to Amazon S3, the correct bucket “mbjc” name and access key.

  • Podlove has my podcast feed listed as https://speakthescience.com/feed/mbjc/ . The podcast feed slug is mbjc. I recently messed with my RSS by redirecting it using the RSS Redirect feedburner / foundit plugin(red herring?). In the Podlove feed basic settings for the MBJC feed, I have the Feed Proxy Redirect Method set to “Don’t redirect” . I did this because of my feedburner experience. Should I change it to the recommended “Temporary Redirect” setting?

  • Since my previous episode and after my feedburner plugin, I have not been able to release a new episode. I have created an episode, “published” it, see it on my website and can even play the audio on my webpage. Web page: [Miss Behavior Journal Club Podcast – Speak the Science]; Episode in question: [https://speakthescience.com/ep-44-what-the-kids-are-listening-to-abrams-et-al-2022/879/]

  • Podlove dashboard says my episode has been published. Episode “2022/06/MBJ044” is the numbering system used by amazon’s aw s3

  • Podlove Support Debug Logging reports a number of errors at the time I attempted to release my episode. This and the Bug Report can be found below. One error message reads "Can’t reach https://mbjc.s3.amazonaws.com/2022/06/MBJC04.mp3 " as if it’s attempting to access MBJC04 not MBJC044. I can not find where 04 is entered anywhere regarding this episode.

I am very inexperienced with jargon and would love your help fixing this issue. Let me know if you need any more details.

Here is that read out:

2022-06-21 02:22:55 Curl Error: The requested URL returned error: 403 Forbidden 2022/06/MBJC044/MP3 Audio toggle details
2022-06-21 02:22:55 Unexpected http response when trying to access remote media file. 2022/06/MBJC044/MP3 Audio HTTP Status: 403 toggle details `—

media_file_id: “65”
http_code: 403| |2022-06-21 02:22:55|Curl Error: The requested URL returned error: 403 Forbidden [2022/06/MBJC044/MP3 Audio](https://speakthescience.com/wp-admin/post.php?post=879&action=edit) [toggle details](https://speakthescience.com/wp-admin/admin.php?page=podlove_Support_settings_handle#)| |2022-06-21 02:22:55|Unexpected http response when trying to access remote media file. [2022/06/MBJC044/MP3 Audio](https://speakthescience.com/wp-admin/post.php?post=879&action=edit) HTTP Status: 403 [toggle details](https://speakthescience.com/wp-admin/admin.php?page=podlove_Support_settings_handle#)| |2022-06-21 02:22:55|Can\'t reach https://mbjc.s3.amazonaws.com/ep-44-what-the-kids-are-listening-to-abrams-et-al-2022.mp3 HTTP Status: 403 [toggle details](https://speakthescience.com/wp-admin/admin.php?page=podlove_Support_settings_handle#) —
url: >
https://mbjc.s3.amazonaws.com/ep-44-what-the-kids-are-listening-to-abrams-et-al-2022.mp3
content_type: null
http_code: 403
header_size: 0
request_size: 252
filetime: -1
ssl_verify_result: 0
redirect_count: 0
total_time: 0.367054
namelookup_time: 4.8E-5
connect_time: 0.082301
pretransfer_time: 0.264539
size_upload: 0
size_download: 0
speed_download: 0
speed_upload: 0
download_content_length: -1
upload_content_length: -1
starttransfer_time: 0.367025
redirect_time: 0
redirect_url: “”
primary_ip: 52.218.182.217
certinfo: |
Array
(
)
primary_port: 443
local_ip: 67.205.10.104
local_port: 39326
http_version: 2
protocol: 2
ssl_verifyresult: 0
scheme: HTTPS
php_open_basedir: “”
php_curl: true
curl_exec: true| |2022-06-21 02:24:40|Curl Error: The requested URL returned error: 403 Forbidden [2022/06/MBJC044/MP3 Audio](https://speakthescience.com/wp-admin/post.php?post=879&action=edit) [toggle details](https://speakthescience.com/wp-admin/admin.php?page=podlove_Support_settings_handle#)| |2022-06-21 02:24:40|Unexpected http response when trying to access remote media file. [2022/06/MBJC044/MP3 Audio](https://speakthescience.com/wp-admin/post.php?post=879&action=edit) HTTP Status: 403 [toggle details](https://speakthescience.com/wp-admin/admin.php?page=podlove_Support_settings_handle#) —
media_file_id: “65”
http_code: 403| |2022-06-21 02:24:40|Curl Error: The requested URL returned error: 403 Forbidden [2022/06/MBJC044/MP3 Audio](https://speakthescience.com/wp-admin/post.php?post=879&action=edit) [toggle details](https://speakthescience.com/wp-admin/admin.php?page=podlove_Support_settings_handle#)| |2022-06-21 02:24:40|Unexpected http response when trying to access remote media file. [2022/06/MBJC044/MP3 Audio](https://speakthescience.com/wp-admin/post.php?post=879&action=edit) HTTP Status: 403 [toggle details](https://speakthescience.com/wp-admin/admin.php?page=podlove_Support_settings_handle#)| |2022-06-21 02:24:40|Can\'t reach https://mbjc.s3.amazonaws.com/2022/06/MBJC04.mp3 HTTP Status: 403 [toggle details](https://speakthescience.com/wp-admin/admin.php?page=podlove_Support_settings_handle#) —
url: >
https://mbjc.s3.amazonaws.com/2022/06/MBJC04.mp3
content_type: null
http_code: 403
header_size: 0
request_size: 212
filetime: -1
ssl_verify_result: 0
redirect_count: 0
total_time: 0.366357
namelookup_time: 5.1E-5
connect_time: 0.083156
pretransfer_time: 0.263547
size_upload: 0
size_download: 0
speed_download: 0
speed_upload: 0
download_content_length: -1
upload_content_length: -1
starttransfer_time: 0.366332
redirect_time: 0
redirect_url: “”
primary_ip: 52.218.185.91
certinfo: |
Array
(
)
primary_port: 443
local_ip: 67.205.10.104
local_port: 40784
http_version: 2
protocol: 2
ssl_verifyresult: 0
scheme: HTTPS
php_open_basedir: “”
php_curl: true
curl_exec: true`|

Bug Report:
Website https://speakthescience.com
PHP Version 7.4.15
WordPress Version 6.0
WordPress Theme Argent v1.1.5
Active Plugins
- Total Upkeep v1.15.2
- DreamHost Panel Login v1.0.0
- Duplicate Page v4.4.8
- Feedburner Alternative and RSS Redirect Plugin v3.5
- Media Cloud v4.4.0
- Jetpack v10.9.1
- PDFjs Viewer - Embed PDFs v2.1.7
- Podcast Subscribe Buttons v1.4.5
- Podlove Podcast Publisher v3.8.1
- Podlove Web Player v5.5.1
- Post and Page Builder v1.19.1
- Redirection v5.2.3
- Shortcodes Ultimate v5.12.0
- Social Icons Widget & Block by WPZOOM v4.2.6
- Orbit Fox Companion v2.10.12
- WP Super Cache v1.7.9
- WPForms Lite v1.7.4.2
WordPress Database Charset utf8
WordPress Database Collate
Publisher Version 3.8.1
Publisher Database Version 153
Web Player Version player_v5
Monolog Version 1
open_basedir ok
curl Version 7.58.0
iconv available
simplexml ok
max_execution_time 120
upload_max_filesize 512M
memory_limit 500M
disable_classes
disable_functions
permalinks ok (/%postname%/%post_id%/)
podlove_permalinks ok
podcast_settings ok
web_player ok
podlove_cache on
assets

0 errors
0 notices
Nice, Everything looks fine!

2

I wish someone in the community had been willing to reach out. In case anyone else has a similar problem, I’ll try to explain what happen, though I’m such a novice, I will probably misspeak.

When I reset the RSS feed name with a feedburner redirect plugin “Follow it”, it was changed and remained changed even after I “deactivated” the forwarding of the feed. The person previously in charge of my podcast distribution still owned my Feedburner URLs for my podcast and I didn’t even know. “Oh, do you want me to transfer ownership?” he says. I didn’t even know it was a thing or that it was the place a fix needed to be made to solve my problem. He updated the Feedburner to point to the new RSS and everything began posting again. All the other inconsistencies I found with close examination of my episode posting process were red herrings. Hope this helps someone or that no one needs this help to begin with. -A-