Hi
I released the newest Episode of my Podcast this morning and the Episode Shows up in all the podcasting apps (Overcast, iCatcher, Apple Podcast App), but I can’t download this or even any of the older episodes anymore. If you go to the Website and use the webplayer, the episodes play just fine:
https://unfunnyfritz.com/feed/podcast
Any help would be appreciated
Now it appears that my feed is not working anymore. While Podba.se and http://castfeedvalidator.com/?url=https://unfunnyfritz.com/feed/podcast say that everything is fine, https://validator.w3.org says now that “This feed does not validate.”
line 29, column 1: href must be a full URL: https://unfunnyfritz.com/wp-content/cache/podlove/57/ad3cae085cd43a066ff2f13fae2194/worst-comic-ever-with-unfunny-fritz_original.jpg [help]
<itunes:image href="https://unfunnyfritz.com/wp-content/cache/podlove/57/ad ...
^
line 41, column 0: url must be a full URL: https://unfunnyfritz.com/podlove/file/42/s/feed/c/podcast/WCE-EP005.mp3 (6 occurrences) [help]
<enclosure url="https://unfunnyfritz.com/podlove/file/42/s/feed/c/podcast/WC …
Website https://unfunnyfritz.com
PHP Version 7.0.14
WordPress Version 4.7
WordPress Theme Catch Box Pro v4.7.1
Publisher Version 2.4.1
Web Player Version no web player found
Twig Version 1.30.0
open_basedir ok
curl Version 7.38.0
iconv available
simplexml ok
max_execution_time 300
upload_max_filesize 67108864
memory_limit 268435456
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!
It’s a bug in the validator because it can’t handle https. The URL is absolutely ok.
I also checked the latest feed entry, it links to https://unfunnyfritz.com/podlove/file/42/s/feed/c/podcast/WCE-EP005.mp3 which can be downloaded and played.
Thanks for the reply.
But I still have the issue of not being able to access the episodes via Overcast or whatever podcasting app I try. Last night suddenly the download worked, but this morning every download or stream from podcasting apps fail again, while I can Access everythig easily via the website
Looks like your site has an incorrect TLS setup.
thanks for the reply
I did some checks and not really any further in solving my Problem:
according to SSL Labs the site is rated with an A
https://www.ssllabs.com/ssltest/analyze.html?d=unfunnyfritz.com
according to LinkSpy: The SSL setup for this website is absolutely flawless and does not negatively affect rankings
https://www.linksspy.com/seo-tools/free-seo-ssl-scan/unfunnyfritz-com
according to the Really Simple SSL Wordpress Plugin:
Detected setup
success SSL is enabled on your site.
success Mixed content fixer was successfully detected on the front-end
success An SSL certificate was detected on your site.
success https redirect set in .htaccess
success HTTP Strict Transport Security was set in the .htaccess
= Your site is not yet configured for the HSTS preload list. Read the documentation carefully before you do! Enable the preload list
= The mixed content fixer is not active on the admin panel. Enable this feature only when you have mixed content on the admin panel.
success The native Wordpress function is_ssl() returned true
success Great! Your scan last completed without errors.
Well
tim@eris % wget https://unfunnyfritz.com/podlove/file/42/s/feed/c/podcast/WCE-EP005.mp3 ~
--2017-01-10 12:43:30-- https://unfunnyfritz.com/podlove/file/42/s/feed/c/podcast/WCE-EP005.mp3
Resolving unfunnyfritz.com... 2001:8d8:1001:f9:7624:3e97:386:f82a, 217.160.0.212
Connecting to unfunnyfritz.com|2001:8d8:1001:f9:7624:3e97:386:f82a|:443... connected.
OpenSSL: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
Unable to establish SSL connection.
Here is the problem: you have set up https for IPv4 but not for IPv6. But your domain resolves to v6 also. When connecting via v6 you get the error.
This might or might not be the cause of the general problem but you should fix that asap as it won’t work with any host using IPv6.
thanks for the help
it appears that the IPv6 DNS setup was a bit sketchy. after changing that and switching the certificate it appears to be working properly now 