Hello AndyOlly,
What is the exact url you insert on the url field. Could you try inserting your website’s url like these:
http://www.regsw.org.uk
http://www.regsw.org.uk
I also got the same error you had but after prefixing with “www” it is now activated.
Let me know if it works for you. 🙂
Best Regards,
Calvin
Hi Calvin,
I have the same issue here.
Nothing I try gets IFTTT activated.
I used both with “www” and without, nothing there.
I even made a user called “IFTTT” and used this for a logon (administrator rights).
Every other IFTTT channel seems to activate quickly, so not WordPress. Is this a WordPress issue?
Any ideas?
Regards, Hendrik
Hi guys,
I’m having a similar issue. When trying to activate wordpress on IFTTT, I am getting an error “Live channel fields value is not a valid WordPress url”. I have read the couple of other posts here in relation to this and have tried all the suggestions:
– Trying with and without www and http://
– Making sure that the wordpress address is the same as the site address
– Disabled any recent plugins
I have another wordpress site that activates no problem, however nothing I do on this one seems to work.
Appreciate any help or input.
Very best,
Ross
I’m also having the same problem – I’ve tried every combination of URL I can think of, have tried setting up a new IFTTT account, changed my WordPress password so it had no symbols in it, you name it, but no joy. If anyone can help, I’d be really grateful – my website is http://www.kiwiearthmother.com
I have a problem with my IFTTT for wordpress…it says
Unable to verify WordPress credentials. Please try again.
Please how will i do that?
Hi, was having this issue just now, i fixed it by going into worpress hitting ‘Get Shortlink’ button on the blog page then use this address for the IFTT form
Sam, your post encouraged me to give connecting WordPress another go. I tried to get a shortlink, but found that this option had disappeared! I did some digging and found an article indicating that WordPress are phasing out shortlinks. Anyway, I did manage to get a shortlink for a specific post I had published, and tried that, to no avail.
But I followed Calvin’s advice (again) and added the http://www. in front of the website url, and hey presto, it worked! I am certain I tried this originally, but for some reason this time, it worked! Hope you get it figured out too. Best of luck,
Sharon 🙂
I’m having a similar problem. I suspect that it may have something to do with the fact that I’m using a custom log-in URL that is different from the typical example.com/wp-admin Entering my custom login URL into my IFTTT recipe doesn’t work.
What’s weird it that it had been working until just today, when I got notified by IFTTT that my recipe could not authenticate with my WordPress.
