Skip to main content

Hello,

I keep getting Base URL invalid when try to connect Gravity forms app (Auth 2.0)

Same issue here


Hi @SunsetSpas!

I’ve gone ahead and added you to the list of affected users.

 


Hi, 

We are also being affected by this issue.

We’ve followed the suggested solutions on this thread (removed htaccess entirely, disabled cloudlfare) but none of them worked so far.

This is the log we get: 

2021-07-12 11:25:52.334181 - DEBUG --> GF_REST_Authentication::authenticate(): Running. 
2021-07-12 11:25:52.334913 - DEBUG --> GF_REST_Authentication::perform_basic_authentication(): Running. 
2021-07-12 11:25:52.334978 - ERROR --> GF_REST_Authentication::perform_basic_authentication(): Aborting; credentials not found. 
2021-07-12 11:25:52.335010 - DEBUG --> GF_REST_Authentication::perform_application_password_authentication(): Running. 
2021-07-12 11:25:52.335042 - ERROR --> GF_REST_Authentication::perform_application_password_authentication(): Aborting; user not found. 
2021-07-12 11:25:52.335067 - DEBUG --> GF_REST_Authentication::perform_oauth_authentication(): Running. 
2021-07-12 11:25:52.335108 - ERROR --> GF_REST_Authentication::perform_oauth_authentication(): Aborting; OAuth parameters not found. 
2021-07-12 11:25:52.335973 - DEBUG --> GF_REST_Controller::current_user_can_any(): method: GET; route: /gf/v2/zapier-requirements; capability: "gravityforms_edit_forms"; result: false. 
2021-07-12 11:25:53.388849 - DEBUG --> GF_REST_Authentication::authenticate(): Running. 
2021-07-12 11:25:53.388952 - DEBUG --> GF_REST_Authentication::perform_basic_authentication(): Running. 
2021-07-12 11:25:53.388988 - ERROR --> GF_REST_Authentication::perform_basic_authentication(): Aborting; credentials not found. 
2021-07-12 11:25:53.389014 - DEBUG --> GF_REST_Authentication::perform_application_password_authentication(): Running. 
2021-07-12 11:25:53.389041 - ERROR --> GF_REST_Authentication::perform_application_password_authentication(): Aborting; user not found. 
2021-07-12 11:25:53.389065 - DEBUG --> GF_REST_Authentication::perform_oauth_authentication(): Running. 
2021-07-12 11:25:53.389101 - ERROR --> GF_REST_Authentication::perform_oauth_authentication(): Aborting; OAuth parameters not found. 
2021-07-12 11:25:53.390002 - DEBUG --> GF_REST_Controller::current_user_can_any(): method: GET; route: /gf/v2/zapier-requirements; capability: "gravityforms_edit_forms"; result: false. 

I’d like to be added to the issue to get notifications on it. 

Thanks.


Hey @Frontpor, I hope you’re doing well!

Thanks for the the comment and the great info, I’ve just added you to the affected users list and we’ll be sure to alert you ASAP once there is a fix. 


@Jillian Can you add me as well. I am using CloudFlare and we are unable to connect Gravity Forms.


Hi @Jon Korn, I’ve added you to the list of affected users - thanks!


@Danvers can you add me to, i have the same issue. Running GF 2.5, openlitespeed and cloudflare. thanks!


Hi @MEMT!

I've gone ahead and added you to the list of affected users. We'll let you know via email when that's been resolved!


Hey everybody! I wanted to post a quick update here that this issue has been closed. If you’re still running into problems, your best bet is to contact the Gravity Forms support team. They can troubleshoot the problem, including to see if you’re running the correct versions of WordPress, Gravity Forms and the Zapier Add-On.


In case you’re using CloudFlare and you are experiencing this issue, disable “Super Bot Fight Mode” and everything will work. 

This one works!!


That’s great news, @ARI!

Thanks for letting us know that disabling that setting worked for you! :)


Also, in my interactions, Zapier says there is no timeline for a solution. This has me concerned, since my business largely depends on Zapier functionality.


Yes, on other sites is work well.


Hi @Eyal!

Happy to see that you’ve reached out to our Support team and they’ve helped you out with this. 

For anyone else who finds this thread, here’s what Support had to say:

Invalid Base URL error looks to be a bug with this app. The good news is you're not the first user to report this problem and it's on our radar. I’ve added your name to this issue which does the following:

  • Re-raises the request with the dev team
  • Gives us a place to track users affected
  • Reminds us to notify you once this become available


I don’t have an ETA of when or if this will happen, but we will definitely email you when this is fixed! Keep an eye out for our Zapier Updates in your inbox.

It may be best to reach out to them if you run into this error, since it may not always be the case that it’s related to this bug.


Hello.

I seem to be hitting the same issue with the authentication failed: Invalid Base URL.

I was able to connect gravity forms to automate.io without issue so I suspect the issue is with zapier specifically.


Hey @hdav and @Hottest DOg!

I’ve added you both to this bug report so when it gets resolved you’ll be notified via email. I see comments from the Gravity Forms teams saying that they’re looking into this. I suspect (and hope) it won’t be too much longer before this one’s fixed :)


Hello, 

I seemed to have fixed my issue. It turned out that I was getting invalid URL notifications because my wordpress site was pointing to a CDN used by Sitelock, who we use for extra security, and Sitelock were blocking the API. It was a bit of a mess for Sitelock whitelist the Zapier IPs as they use AWS and there’s hundreds of them, and could change in the future, and it let me set up the Zap, but wasn’t pulling the data through. In the end the actual fix was easy: get Sitelock to whitelist the ‘user agent’ for the API, which is literally just “Zapier”. Not sure if that will work for others, but it worked for me. 

Cheers


I posted a reply about how I fixed mine - it was to do with my site using Sitelock CDN that was blocking the API, but not sure where the reply has gone


This might not work for you, because in my case my wordpress site is using Sitelock, which is pointing the domain to their CDN, and their firewall was blocking the connection. I went onto Sitelock’s support chat, and got them to whitelist the user agent name, which is literally ‘Zapier’ - and now it’s working. So the firewall will scan all API requests with the user agent name Zapier and let those ones through.

Not sure if that’s your case scenario - but worked for me


I’m encountering this issue as well. How do I sign up for updates?  @nicksimard 


Hi @ibro and @ryan_blip!

I’ve added you to the issue as well, so you’ll be updated when it’s resolved.


Hi, I’d also like updates on this issue. I’m looking to add a new form as soon as possible. Thank you!


Hi @BarVision - I’ve added you to this issue. You’ll be contacted via email if we have an update to share. Thanks!


Hi I have one Zap connected and running to one gravity form, I tried to connect a second one but now I am getting the “Invalid base URL” error message. It’s very important and urgent for us to fix this and connect both forms. Please let me know what can I do to fix it. Thank you in advance. 


Hello,

I am having the same problem and would like to receive an update on when and how the issue is resolved.

Thank you!