Bugzilla – Bug 14425
Radiotime Error - Problems Connecting Forbidden 403 Error on Squeezebox Controller
Last modified: 2009-10-05 16:42:30 UTC
Ticket 090930-002298 Squeezebox Controller r7790 Receiver fw 65 Mysqueezebox.com Customer is getting the following error when trying to access Radiotime from the Squeezebox Controller (connected to receiver): Problems Connecting 403 Forbidden Tried Factory resetting Power cycling router Removing Radiotime account Recreating Mysqueezebox.com account Still will not work. Per Andy, filing bug. ********************** Below is the information captured: GET /Index.aspx?username=meyerparty HTTP/1.1 Connection: close Cache-Control: no-cache Accept: */* Accept-Language: en Host: opml.radiotime.com User-Agent: Mozilla/5.0 (Unix; N; linux; x86_64-linux; EN; iso-8859-1) mysqueezebox.com/7.4.1-sn/TRUNK Icy-Metadata: X-Forwarded-For: 173.26.21.94 ] [09-09-29 19:35:35.5950] Slim::Networking::Async::HTTP::_http_read (323) Headers read. code: 403 status: Forbidden [09-09-29 19:35:35.5955] Slim::Networking::Async::HTTP::_http_read (324) bless({ "cache-control" => "private", connection => "close", "content-length" => 0, date => "Wed, 30 Sep 2009 02:35:35 GMT", server => "Microsoft-IIS/6.0", "x-aspnet-version" => "2.0.50727", }, "HTTP::Headers") # telnet opml.radiotime.com 80 Trying 69.12.18.166... Connected to opml.radiotime.com. Escape character is '^]'. GET /Index.aspx?username=meyerparty HTTP/1.1 Connection: close Cache-Control: no-cache Accept: */* Accept-Language: en Host: opml.radiotime.com User-Agent: Mozilla/5.0 (Unix; N; linux; x86_64-linux; EN; iso-8859-1) mysqueezebox.com/7.4.1-sn/TRUNK Icy-Metadata: X-Forwarded-For: 173.26.21.94 HTTP/1.1 403 Forbidden ... **************** Andy's comment from campfire however, when I run it from my house, it works oh, if I change mysqueezebox.com to SqueezeNetwork, it works I think they are matching on our User-Agent Thanks, LaRon
Can you confirm if this is fixed?
Thanks Andy, I am pinging the customer to have try. Thanks, LaRon
This bug has been fixed in the latest release of MySqueezebox.com (formally known as SqueezeNetwork)! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.