Watchdog: 401 Not Authorized.

I'm getting this and a 404 Not found every cron run... just updated to 2.6, so it's still a bug :-/

umm... I'm still having this problem...

subscribing

Same problem

Check the accounts that are causing the 401s and 404s. Do they exist? Are they protected? are there illegal characters in the username?

Subscribing.

Since updating to D6.16 & Twitter 6.x-2.6 I get the "401 Not Authorized" every cron run and no updates of tweets displayed in my site's twitter block. I reset the twitter account password and even tried changing to a new password without success.

Everything was working fine for me until I changed my Twitter account from public to private. I then deleted all settings and re-entered everything with password. The module, however, does not want to pull new tweets anymore. I receive the same "401 Not Authorized" error that I can look up in watchdog. Checked even what is saved in DB and everything seems to be fine. I can even see the passwords are properly saved.

As for the suggestions above, my username does not contain any specific and unusual characters and the user that triggers the pulling is superadmin with all the rights (me).

I have come up with something that might do the trick. In the file twitter.module on the line 184 there is this IF condition:

if (empty($account['protected']) || empty($account['password'])) {

It basically means that if an account is protected (not visible tweets to others on the site) OR the password is left empty, do not use the login info for your Twitter account. What is more, I don't think the empty on the protected value may work because it is either 0 or 1, not empty. In general, it seems wrong to me because I can have a protected account and still need to use the login to grab new tweets. The condition is, however, true if either one of those subconditions validates. Therefore I edited the line to this

if (empty($account['password'])) {

which would mean that if I don't enter the password, drupal should not use on the cron run the login info to log into the Twitter account.

I ran the cron and suddenly got no 401 error.

You may also need to change accordingly the file twitter.inc. There is a function for saving new twitter accounts that uses the same condition.

Those condition might need to be reworked a little bit but I need someone to explain to me what is the logic of the "protected" value assigned with Twitter accounts in Drupal.

I am getting the 401 Not Authorized error as well. I have only been seeing this since upgrading to Drupal 7 a few weeks ago. Only admin level accounts have access to the global Twitter account and I use only admin level accounts. It appears that the password is not being saved in the Twitter setup; no mask bullets are displayed (just blank field) after postback. I suppose this might be normal. But there should be some indication that something has been saved there to avoid confusion. This may be another issue completely but I mention it here because it may be related: the delete old statuses does not get saved. Whenever I select a value, it always returns to NEVER after the postback.