search

captn3m0 / ifttt-webhook

:recycle: A webhook middleware for the ifttt.com service
https://github.com/captn3m0/ifttt-webhook
306 stars 67 forks source link

Live channel fields value is not a valid Wordpress URL? #3

Open mahodder opened 11 years ago

mahodder commented 11 years ago

I'm getting this error when trying to connect the WP channel.

Tried ifttt.captnemo.in and my own clone but both give the same result:

"Live channel fields value is not a valid Wordpress url Unable to verify Wordpress credentials. Please try again."

Anyone else still having success with this?

captn3m0 commented 11 years ago

This seems weird. I can't seem to be able to connect ifttt.captnemo.in, while connecting my debug deployment (whispering-anchorage-5317.herokuapp.com) works fine. Figuring out the difference, so I can track this down.

captn3m0 commented 11 years ago

Ok. This just got weirder. ifttt is accepting ifttt-webhook.herokuapp.com as a valid wordpress channel, while it rejects ifttt.captnemo.in, even though they are both the same thing. So either ifttt is blacklisting the site, or it is some weird heroku/dns/CNAME issue.

Can I know where you are hosting your clone? And does it involve a CNAME entry?

mahodder commented 11 years ago

I tried with a cname and just linking to the folder itself www.site.com/ifttt/ but both give the same result.

Linking to the real WordPress install on the same server does work.

They are hosted over at linode.com

captn3m0 commented 11 years ago

I just cloned it to a new VM, and it works perfectly fine there. (http://captn3m0.kd.io/ifttt.captnemo.in/). I have only seen the issue on ifttt.captnemo.in so far and still have no clue why it is happening.

mahodder commented 11 years ago

Yes very weird.

I don't think it's a DNS thing on my end, as I even tried putting it in the root directory and it didn't work.

I then tried it on an almost identical server at linode.com and it worked.

The biggest difference between my servers are:

captn3m0 commented 11 years ago

Just tried ifttt.captnemo.in and it started working again. Can you please check again if the issue is resolved? It seems like an ifttt-sided issue to me.

mahodder commented 11 years ago

Still no go for me, but I'll just throw it on my other server that is working anyway - must be some fringe server config issue.

justin-pierce commented 10 years ago

I'm getting the same error both on my own server and on ifttt.captnemo.in

captn3m0 commented 10 years ago

I'll look into it as soon as I can after my exams.

maddox commented 10 years ago

I just ran into this. It looks like it's because IFTTT expects to hit the server via https.

andig commented 10 years ago

Similar problem here. In my case IFTTT connects to ifttt.captnemo.in but refuses my- existing- clone.

It looks like it's because IFTTT expects to hit the server via https.

ifttt.captnemo.in does support https from what I've seen. I'll check if enabling my site to do so will fix the IFTTT error.

jonasschnelli commented 9 years ago

just stepped over the same problem. It seams that IFTTT only supports non-https. I tried with a proper valid https (valid cert) host. Was not working. Enabled non-https and it worked. Shame IFTTT :-1:

Blogthetech commented 7 years ago

Can someone help me out, my site https://www.blogthetech.com won't connect, I have tried all the means online but it doesn't work. What am I missing?.

BetterVisionBG commented 7 years ago

Hello,

I have the same problem as BlogTheTech:

I tried - https://ifttt.com/channels/wordpress/activate_create

put my URL with https. without https, put the complete url ..../wp-admin and the ..../wp-login.php

created a new user for the IFTTT login authentication, the user is administrator in the wordpress site

and this the IFTTT gives me these errors:

Live channel fields value is not a valid Wordpress url
Unable to verify Wordpress credentials. Please try again.

The site is https://bettervision.bg/

Any suggestions?

Best Regards, Itso

captn3m0 commented 7 years ago

I haven't had time to verify the errors, I'm guessing ifttt has a wordpress version expectation and I'm still on an older XMLRPC version of sorts, but not sure.

Blogthetech commented 7 years ago

I have seen the solution. It seems by default, most web hosting company disable a file in the root folder, seems to be for some security reasons and related. you will need to contact them and tell them to activate it.

Blogthetech commented 7 years ago

The file is the XMLRPC

BetterVisionBG commented 7 years ago

Hey,

I fixed the issue by stopping the mod_security from the control panel of my hosting account. The firewall blocked the access from the IP`s of the IFTTT network.

Does anyone know how to contact these guys to whitelist all their IP`s on my servers? I found 5-6 but most probably they have many more.

captn3m0 commented 7 years ago

@BetterVisionBG There are some forms at https://ifttt.com/support that you can try.