Can't get podcasts

I’m joining the “can’t download” club. I tried Pocket Casts and Overcast apps , and also tried different networks.

I’m a network engineer so I want a bit further and tried downloading an episode from the command line

curl -Lvs 'https://www.podtrac.com/pts/redirect.mp3/pdst.fm/e/verifi.podscribe.com/rss/p/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365' | tee output.txt

* Host www.podtrac.com:443 was resolved.
* IPv6: (none)
* IPv4: 35.167.178.99, 35.80.142.180, 34.217.0.6
*   Trying 35.167.178.99:443...
* Connected to www.podtrac.com (35.167.178.99) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
} [320 bytes data]
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (IN), TLS handshake, Server hello (2):
{ [100 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [3797 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [333 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256 / [blank] / UNDEF
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=*.podtrac.com
*  start date: Jul 24 00:00:00 2025 GMT
*  expire date: Aug 21 23:59:59 2026 GMT
*  subjectAltName: host "www.podtrac.com" matched cert's "*.podtrac.com"
*  issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M04
*  SSL certificate verify ok.
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://www.podtrac.com/pts/redirect.mp3/pdst.fm/e/verifi.podscribe.com/rss/p/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: www.podtrac.com]
* [HTTP/2] [1] [:path: /pts/redirect.mp3/pdst.fm/e/verifi.podscribe.com/rss/p/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365]
* [HTTP/2] [1] [user-agent: curl/8.7.1]
* [HTTP/2] [1] [accept: */*]
> GET /pts/redirect.mp3/pdst.fm/e/verifi.podscribe.com/rss/p/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365 HTTP/2
> Host: www.podtrac.com
> User-Agent: curl/8.7.1
> Accept: */*
> 
* Request completely sent off
< HTTP/2 302 
< date: Wed, 15 Oct 2025 13:52:24 GMT
< location: https://pdst.fm/e/verifi.podscribe.com/rss/p/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365
< cache-control: no-cache, no-store, must-revalidate
< pragma: no-cache
< expires: -1
< 
* Ignoring the response-body
* Connection #0 to host www.podtrac.com left intact
* Issue another request to this URL: 'https://pdst.fm/e/verifi.podscribe.com/rss/p/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365'
* Host pdst.fm:443 was resolved.
* IPv6: 2001:4860:4802:34::15, 2001:4860:4802:32::15, 2001:4860:4802:36::15, 2001:4860:4802:38::15
* IPv4: 216.239.38.21, 216.239.32.21, 216.239.34.21, 216.239.36.21
*   Trying [2001:4860:4802:34::15]:443...
* Connected to pdst.fm (2001:4860:4802:34::15) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
} [312 bytes data]
* (304) (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* (304) (IN), TLS handshake, Unknown (8):
{ [15 bytes data]
* (304) (IN), TLS handshake, Certificate (11):
{ [4009 bytes data]
* (304) (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* (304) (IN), TLS handshake, Finished (20):
{ [36 bytes data]
* (304) (OUT), TLS handshake, Finished (20):
} [36 bytes data]
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / [blank] / UNDEF
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=pdst.fm
*  start date: Oct 14 02:31:56 2025 GMT
*  expire date: Jan 12 03:21:06 2026 GMT
*  subjectAltName: host "pdst.fm" matched cert's "pdst.fm"
*  issuer: C=US; O=Google Trust Services; CN=WR3
*  SSL certificate verify ok.
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://pdst.fm/e/verifi.podscribe.com/rss/p/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: pdst.fm]
* [HTTP/2] [1] [:path: /e/verifi.podscribe.com/rss/p/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365]
* [HTTP/2] [1] [user-agent: curl/8.7.1]
* [HTTP/2] [1] [accept: */*]
> GET /e/verifi.podscribe.com/rss/p/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365 HTTP/2
> Host: pdst.fm
> User-Agent: curl/8.7.1
> Accept: */*
> 
* Request completely sent off
< HTTP/2 302 
< date: Wed, 15 Oct 2025 13:52:24 GMT
< content-type: text/html; charset=utf-8
< content-length: 128
< access-control-allow-origin: *
< location: https://verifi.podscribe.com/rss/p/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365
< via: 1.1 google
< 
* Ignoring the response-body
* Connection #1 to host pdst.fm left intact
* Issue another request to this URL: 'https://verifi.podscribe.com/rss/p/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365'
* Host verifi.podscribe.com:443 was resolved.
* IPv6: 2600:1f10:4c2d:4711:d9b5:1815:6cd4:84ae, 2600:1f10:4c2d:4712:99e9:4798:7274:3210, 2600:1f10:4c2d:4712:3211:4776:7bfc:861, 2600:1f10:4c2d:4711:b7de:bb7d:9633:242f
* IPv4: 3.213.238.40, 52.2.20.172, 34.228.126.24, 3.89.0.232
*   Trying [2600:1f10:4c2d:4711:d9b5:1815:6cd4:84ae]:443...
* Connected to verifi.podscribe.com (2600:1f10:4c2d:4711:d9b5:1815:6cd4:84ae) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
} [325 bytes data]
* (304) (IN), TLS handshake, Server hello (2):
{ [100 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [3797 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [333 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256 / [blank] / UNDEF
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=*.podscribe.com
*  start date: Apr 26 00:00:00 2025 GMT
*  expire date: May 26 23:59:59 2026 GMT
*  subjectAltName: host "verifi.podscribe.com" matched cert's "*.podscribe.com"
*  issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M03
*  SSL certificate verify ok.
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://verifi.podscribe.com/rss/p/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: verifi.podscribe.com]
* [HTTP/2] [1] [:path: /rss/p/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365]
* [HTTP/2] [1] [user-agent: curl/8.7.1]
* [HTTP/2] [1] [accept: */*]
> GET /rss/p/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365 HTTP/2
> Host: verifi.podscribe.com
> User-Agent: curl/8.7.1
> Accept: */*
> 
* Request completely sent off
< HTTP/2 302 
< server: awselb/2.0
< date: Wed, 15 Oct 2025 13:52:25 GMT
< content-type: audio/mpeg
< content-length: 0
< location: https://prefix-v4.pscrb.fm/shadow/ipv4/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365&pscrb_ip=2601:283:4f01:eee1:846b:9d29:1ce9:3261
< access-control-allow-origin: *
< 
* Ignoring the response-body
* Connection #2 to host verifi.podscribe.com left intact
* Issue another request to this URL: 'https://prefix-v4.pscrb.fm/shadow/ipv4/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365&pscrb_ip=2601:283:4f01:eee1:846b:9d29:1ce9:3261'
* Host prefix-v4.pscrb.fm:443 was resolved.
* IPv6: (none)
* IPv4: 3.209.76.207, 52.71.47.139
*   Trying 3.209.76.207:443...
* Connected to prefix-v4.pscrb.fm (3.209.76.207) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
} [323 bytes data]
* (304) (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* (304) (IN), TLS handshake, Unknown (8):
{ [19 bytes data]
* (304) (IN), TLS handshake, Certificate (11):
{ [3786 bytes data]
* (304) (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* (304) (IN), TLS handshake, Finished (20):
{ [36 bytes data]
* (304) (OUT), TLS handshake, Finished (20):
} [36 bytes data]
* SSL connection using TLSv1.3 / AEAD-AES128-GCM-SHA256 / [blank] / UNDEF
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=*.pscrb.fm
*  start date: Jun 21 00:00:00 2025 GMT
*  expire date: Jul 20 23:59:59 2026 GMT
*  subjectAltName: host "prefix-v4.pscrb.fm" matched cert's "*.pscrb.fm"
*  issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M03
*  SSL certificate verify ok.
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://prefix-v4.pscrb.fm/shadow/ipv4/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365&pscrb_ip=2601:283:4f01:eee1:846b:9d29:1ce9:3261
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: prefix-v4.pscrb.fm]
* [HTTP/2] [1] [:path: /shadow/ipv4/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365&pscrb_ip=2601:283:4f01:eee1:846b:9d29:1ce9:3261]
* [HTTP/2] [1] [user-agent: curl/8.7.1]
* [HTTP/2] [1] [accept: */*]
> GET /shadow/ipv4/track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?updated=1760116365&pscrb_ip=2601:283:4f01:eee1:846b:9d29:1ce9:3261 HTTP/2
> Host: prefix-v4.pscrb.fm
> User-Agent: curl/8.7.1
> Accept: */*
> 
* Request completely sent off
< HTTP/2 302 
< server: awselb/2.0
< date: Wed, 15 Oct 2025 13:52:25 GMT
< content-type: audio/mpeg
< content-length: 0
< location: https://track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?pscrb_ip=2601:283:4f01:eee1:846b:9d29:1ce9:3261&updated=1760116365
< access-control-allow-origin: *
< 
* Ignoring the response-body
* Connection #3 to host prefix-v4.pscrb.fm left intact
* Issue another request to this URL: 'https://track/28D492/traffic.megaphone.fm/SLT3761842917.mp3?pscrb_ip=2601:283:4f01:eee1:846b:9d29:1ce9:3261&updated=1760116365'
* Could not resolve host: track
* Closing connection

So it’s trying to resolve “track” as a hostname, which isn’t going to work.

So I had access to 10/7, and now can’t get the 10/14 or 10/15 episodes.

1 Like

Any update on a resolution yet from the Clark team? Like the others on here, haven’t been able to listen for 2 weeks now on iHeart. Tried Apple Podcasts and got one episode to download, now nothing.

1 Like

I’m having problems with Clarks podcast only in Pocket Casts since 10/14. All other podcasts work fine. Very weird issue.

1 Like

Same here.. similar timeframe as shared by others. Usually used IHeart. Spotify had the same issue. It would load but didn’t play.

2 Likes

The podtrac.com links to the mp3 in the RSS feed are busted for the latest 2 podcasts.

2 Likes

We know this is so frustrating! But we really appreciate your detailed posts. We are sharing the information with our podcast host so they can better help troubleshoot. No update or fix, yet, but we are actively working on it!

4 Likes

Just had this same situation happen the past 2 days. Have been playing Clark’s podcast through Amazon Echo Dot and Echo Auto for years. Connection starts as normal and I hear “Getting the Clark Howard Podcast from Apple Podcasts. Here’s the latest episode, the 15th of October 2025 update. Holiday flights and travel credit cards, Medicare Open Enrollment”. But then I hear “Sorry, something went wrong with playback. Try again in a bit”. Been trying several times “in a little bit” and still no connection. Ended up having to watch/listen on YouTube, but miss being able to listen while in the car. If anyone has any ideas why this is happening, please share.

I have an Amazon account and it is still not working for me.

I even tried to change my Amazon preference for Podcasts to Amazon Music and still no luck.

I can no longer get the podcast on my iPhone or iPad Podcast app. Tried downloading my Amazon Music app and can’t get it there either. I get the following message “This episode is temporarily unavailable. Try again later.” Can anyone help or offer suggestions?

2 Likes

I’m suffering from Clark withdrawal symptoms. I might go buy a time share or an Indexed Universal Annuity. I was really close to signing up for Zelle today.

I hope that the Clark podcast comes back online before I do anything stupid!

2 Likes

Please read the previous posts in this thread. It is a widespread problem across many podcast providers - but Clark’s episodes only. See also a couple of replies by a Team Clark rep who says, “sorry, we’re working on it”. Doesn’t seem like rocket science.

1 Like

I usually listen to Clark Howard on Apple Podcasts, but this week (Oct 13-17, 2025) I get an error message that says “This episode is temporarily unavailable.” But it’s all the episodes, even the ones that I have listened to previously. I have tried removing and redownloading, unfollowing and refollowing. Nothing seems to work. Googling the issue led to this thread. Hope you guys find a fix!!!

1 Like

Look at my post (#12). I just downloaded the 10-15-25 episode, I’ll listen to it today while you all are still trying to figure this out!

There is nothing to figure out. The links in the RSS feed are broken so most apps/services that pull from that will be broken. Yes, you can manually download it from the website or sit down and watch on youtube, but that is not how most of us consume podcasts.

Clark clearly doesn’t have any nerds on staff because from what I can see it could probably be fixed in minutes :slight_smile:

2 Likes

I’m having the same problem… I have Spotify and tried in Apple and can’t play any episodes.

2 Likes

I am having the same problem as everyone else. I have tried multiple podcast apps Clark’s won’t play on any of them. I listen to many different podcasts and his is the only one I am having a problem with.

2 Likes

It would be nice if someone from Clark’s team could give us a status update on the issue. Do they even acknowledge there is a problem? Are they working on it? Any help would be appreciated.

1 Like

Sally_TeamClark has responded twice if you look at all the replies above.

1 Like