Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
The 9/14/15 Update to fix error 500
#1
Upon calling the kickass torrent channel, we are presented with an extended wait period to load the titles, and finally faced with a server side error:500 message. With further inspection it seems as though there was a minor change to the blissflixx.proxy that affects us with an error. By updating & restarting the server through the settings segment in the ugi of Blissflixx we can load the titles but are still presented with the server side error:500 message telling us that there is some kind of internal server side error.

Code:
Traceback (most recent call last):
  File "./blissflixx.py", line 93, in default
    ret = call(**datadict)
  File "/home/pi/blissflixx/lib/api/channels.py", line 176, in feed
    return installed.getChannel(chid).getFeed(idx)
  File "/home/pi/blissflixx/lib/api/channels.py", line 61, in getFeed
    return self.getPlayItems(self.module.feed(idx))
  File "/home/pi/blissflixx/plugins/bfch_kickass_torrents/__init__.py", line 31, in feed
    doc = get_doc(_FEEDLIST[idx]['url'], proxy=True)
  File "/home/pi/blissflixx/lib/chanutils/chanutils.py", line 71, in get_doc
    r = get(url, params=params, **kwargs)
  File "/home/pi/blissflixx/lib/chanutils/chanutils.py", line 42, in get
    raise Exception("Request : '" + url + "' returned: " + str(r.status_code))
Exception: Request : 'http://blissflixx-proxy1.appspot.com' returned: 500

Has anyone found a solution to this problem as it hinders development of the kickass channel as well as decrease the quality of the user experience when using blissflixx. Seeing that the last commit only affected the ythelper.py file I don't see how this error could have arose, also no DMCA takedown of kat so that has been ruled out, plus the videos load sometimes just the error message is still present on the ugi. 

 Any thoughts are appreciated, Thanks.
Lexo
Reply
#2
Sorry about the problems with KAT - the site was somehow not responding to the proxy. This should be fixed now.
Reply
#3
Problem Solved√ Thanks!
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)