I keep getting Base URL invalid when try to connect Gravity forms app (Auth 2.0)
Best answer by nicksimard 2 August 2021, 19:27
Also having this issue, need this fixed as soon as possible.
In case you’re using CloudFlare and you are experiencing this issue, disable “Super Bot Fight Mode” and everything will work.
Hey @Anne, hope you are well!
I’ve just went in and made sure you were added to the report so that we can be sure to alert you ASAP once there is a resolution.
In the meantime, if you need access to the IP address range for Zapier, that would be all of US-East-1 from Amazon: https://zapier.com/help/troubleshoot/behavior/cant-access-or-use-zapier-with-other-apps
The issue would not be explicitly related to CloudFlare firewall, but any firewall that may be configured to block our IP address range. Sometimes hosts of a domain may automatically have blacklisted IPs from Amazon and this can cause issues as well.
That said, this particular bug is a top priority right now and we are actively working with Gravity Forms to help find a resolution for all of our users. Also, it can be beneficial to reach out to Gravity Forms directly as they are also collecting relevant Gravity Forms user information from their side as well.
This works for me thanks!
Hi, Please add me to the list and let me know when the issue is resolved. Thanks!
Hi I am having the same issue.
authentication failed: Invalid Base URL.
I cannot connect the two.
So at the moment is it not possible to use Gravity Forms and Zapier?
Thanks for your message, I’ve added you to the list of affected users, which means that you’ll get an email when the issue is resolved.
Hi, I’d also like updates on this issue. I’m looking to add a new form as soon as possible. Thank you!
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.
Hi Danvers thank you for your response. Can you make a recommendation of a stopgap work around for us? I see there are suggestions of allowing the previous version of the integration to work in tandem until the bugs are resolved but maybe this isn’t a practical solution for your programming team. Please suggest another approach as I know these site responses to customers are a critical matter for many, including myself.
I am experiencing the same error.I am using CloudFlare on the website where Gravity Forms is installed.Disabling Super Bot Fight Mode in Cloudflare did not fix the error for us.If disabling Super Bot Fight Mode is fixing it for some users, I believe Zapier needs to look into whether or not this is a CloudFlare firewall related issue. If it is, users will need instructions as to what IP addresses or user agents should be whitelisted.
I am having the same problem and would like to receive an update on when and how the issue is resolved.
Gravity Forms responded to me and said that they have NOT received communication on some of these issues. This makes it very confusing and hard to discern. They’ve done some tests on their end, which passed, and told me that some of these problems are on Zapier’s end. However, Zapier is not providing any details, test results, etc.
By the way, Zapier said “no refund” while this doesn’t work. I’m not too happy about that.
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.
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.
Disabling Bot Fight Mode in CloudFlare fixed it for us.
Obviously this isn’t the ideal solution as we’d like to maintain that CF functionality. Is there an official response to keeping Bot Fight Mode turned on?
@U.S. Energy Recovery You've been added to the report! Once we have an update you’ll be notified directly!
I think as far as Bot Fight Mode is concerned, your best bet would be to reach out to the Gravity Forms support team to see if they can confirm that for you. They also have their own Community, where you might be able to find help with that :)
I’m not aware of an ‘official’ workaround that I can suggest. It looks like @hdav had some luck with this:
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.
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 availableI 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.
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:
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.
@Airdev, @Home Painters and @jgamez I’ve added you all as affected users on the issue and you’ll get an email from us when it’s resolved. Thanks!
1+ month of this issue its unacceptable.
Use addon webooks like workaround not works for me. this is frustrating with a Premium subscription with Zapier and Gravity Form. 1350$ plus 250$ year…
please add me to the list.
I can see that you’ve commented on both to this post and another one about the same issue
I replied to your comments on the other post and I’ll post part of my reply here, in case anyone would like more information:
The Gravity Forms Zapier integration is owned and maintained by them, which means that the Gravity Forms team will need to address this issue with their Zapier integration. We’re unable to give an estimate of when it will be fixed though I can see that the Gravity Forms team is working hard to find a solution to this issue.
I am having the same issue. My site is private (requires login to view) and it says invalid URL. I have a .co URL (not .com). I sent support an email with screenshots. What happened to being able to add the webhook in the Gravity Forms Zapier plugin? May have to move to automate.io if unable to connect.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.