Error 34 on one of 4 servers


Using Twython, trying to get “lists/statuses” is returning a 404 (twitter error 34) on just one of our 4 servers. Unfortunately, it’s the production server it’s not working on. Even after resetting our consumer/secret keys, still the 404 on the one server.

Here are the relevant lines from the traceback. This is really baffling us here.

File “/root/.virtualenvs/tce/local/lib/python2.7/site-packages/twython/” in get_list_statuses
544. return self.get(‘lists/statuses’, params=params)
File “/root/.virtualenvs/tce/local/lib/python2.7/site-packages/twython/” in get
230. return self.request(endpoint, params=params, version=version)
File “/root/.virtualenvs/tce/local/lib/python2.7/site-packages/twython/” in request
224. content = self._request(url, method=method, params=params, api_call=url)
File “/root/.virtualenvs/tce/local/lib/python2.7/site-packages/twython/” in _request
194. retry_after=response.headers.get(‘retry-after’))

Exception Type: TwythonError at /api/twitter/curated_feed
Exception Value: Twitter API returned a 404 (Not Found), Sorry, that page does not exist


I wouldn’t recommending resetting your consumer keys and secrets when you encounter a 404.

I would look in more detail about what’s actually happening. When you’re getting this 404 on this one server, what is the exact URL it’s executing? What happens if you execute that URL in another environment? What happens when you try to find that list on the Twitter website?

Are there any software version differences in this other environment? Are there any run time settings or proxy settings that might be interfering?


There’s no real discrepancies between library versions and the machines, all that is managed by pip. We did notice however that even trying to view the members of the list on the actual Twitter site gives “Sorry, that page could not be found.”, as would trying to view the list.

Now it seems they’ve outright deleted the list, so we are just going to build a new one tomorrow. Appreciate the help.