watch fails with ERROR: Please verify your Tumblr credentials...

[cacophobe]

Thank you for all your effort, I have been waiting for something like this for ages. Have been trying to get it to work probably since it was published, but have always given up, because I could never get it to work, because of one or another issue. This is the latest roadblock I am facing:

$ peak watch
peak
version 0.4.3

fetching xyz.tumblr.com...
ERROR: Please verify your Tumblr credentials. If your credentials are correct, your account may be locked. To unlock your account, visit tumblr.com and sign in.

don't know if it's optional to add the email and password in config but, i am getting the same error with or without those parameters. I am definitely logged in at tumblr.com.

[nporteschaikin]

Hi @cacophobe! Thanks for the kind words. I'm sorry peak hasn't worked out for you yet. Tumblr continually changes their authentication wall, so sometimes it's hard for me to keep up. However, I just used my test blog and it worked out okay. Are you adding the credentials either via the CLI or in your .peakconfig.yml file?

output_path: .peak
port: 1111
index: index.jade
blog: xyz
email: [email protected]
password: abc123

[cacophobe]

Previously, I had tried adding both via the CLI and .peakconfig.yml, the results were the same. I guess that should be expected, as the CLI options end up in the config file, I guess? and I was cross-checking the file to be sure.

In case it helps you, these are my recent progress reports:

From your previous comment and from this comment I realised that the blog: should be written as xyz instead of xyz.tumblr.com.

Tried that without the email: and password: (I thought they were optional), didn't work.

Added the email and password, it worked!! but... only for a few initial attempts.

As soon as it started working, I began editing the index.jade file to see if I could display some content. But after a few compiles and edits, when I restarted the server, the same error showed up again. Despite the fact that I hadn't touched the config since.

So, I thought maybe it's a Tumblr authentication issue, whereby they are blocking more than a few requests. I changed the blog to another one I have on Tumblr. The same thing happened. It worked for exactly 2 or 3 requests, and after that I started getting the same error.

Hope it's something you can figure out.

[andismith]

I'm also having this problem. It used to work, but now I can't log in at all. I get the same error.