TVDB CAPTCHA PRoblem

I’m aware of the move to TVDB and my install is up-to-date, but the TVDB is causing another problem.

My Sonarr is installed on a headless linux box, and if I try to add a new series I get an error like:

HTTP Error - Res: [GET] http://thetvdb.com/api/GetSeries.php?seriesname=frasier : 403.Forbidden

this is also in the log:

<div class="cf-section cf-highlight cf-captcha-container"> 

This box is on a VPN, and so is my desktop machine. When I tried to access http://thetvdb.com/ from my desktop machine it asked me to enter a CAPTCHA. I did so with no problem.

But how to solve this CAPTCHA problem on my server?

captcha is from cloudflare right?

have a look at #1 here

@dan is correct, its coming from CloudFlare, I’m not entirely surprised that this is happening on a VPN, since people often use them to hide who they are and may abuse services in the process.

Thanks guys. I know it’s from cloudfare, but how to get around this? Putting a captcha on an api is mental! Also, I wouldn’t use Sonarr or any similar software without protecting my identity, and nor should anyone else. Basically, Sonarr is broken for me now, but it’s the tvdb’s fault, not Sonarr.

I’ll try using a different VPN server, seems like my only hope

you “attempt” to get around it by attempting to do what in the #1 in the page i linked above and requesting a whitelist, but been a VPN service you might not get far.

theres really no need to be using a VPN for thetvdb, it is not illegal in any fashion, its just a database of shows and episode info

It’s not about the tvdb, it’s about what sonarr downloads, as well as couchpotato and transmission which are on the same machine.

Whitelisting the site didn’t make any difference. If I could only enter the captcha in a way that would unblock sonarr…

i dont know how your VPN is setup, if it was me using that setup i would just route traffic to tvdb ip’s over your normal connection, and the rest over the vpn

Thanks, I guess that’s what I needed to know. My VPN is set up on my router, running dd-wrt. If this happens again I’ll look into setting up that IP routing.

Having said that, maybe it was the result of me requesting the IP to be whitelisted, but everything’s back to normal now :smile:

Thanks for your help!