I created my twilio account today and followed the steps on your demo page. In twilio, I got a test phone number, then encoded the SID and Token with a colon “:” between the two numbers and no space. I also included “Basic” for the authorization field in the plugin. But I’m still getting the error below. I also tried it on your demo page and got the same error. Is there something I’m missing?
Hi @manuelmaccou,
Thanks for reaching out. Perhaps the encoded Account SID and Authtoken is not correct on your side.
Could you please confirm whether or not it has been encoded in base64 this way:
AccountSID:Authtoken (generates a key)
And then pasted into Plugins tab this way:
Basic Generated_key
Also, make sure that your numbers are actually verified in Twillio dashboard, here:
Let me know how it goes.
Best,
Alex
Hi @alexandru thanks for getting back to me. I entered the SID and Authtoken in that format. Just to clarify, there should be a colon between the two numbers, correct? That’s how I’ve been doing it.
There are a lot of settings on base64. This is how I have it configured. Is this correct?
The screen shot from my original post shows “Basic” in front of the generated key so that should be right. And I put my personal phone number where the test messages should be sent as a verified number in my Twilio account. So I’m not sure what else I could be missing.
Hi. Following up on this. Any ideas?
Hi @manuelmaccou,
Thanks for details! Let’s assume that the Account SID and Authtoken part is ok, because based on screenshots everything is fine.
Just make sure when you enter it in the Plugins tab, it contains all the generated key including the ‘==’ characters at the end.
Also, when testing the plugin, use the full number but without the ‘+’ character. Meaning, in your case the sender phone number should be 1607..
instead of 607..
For example, this is our trial number that starts with:
And this is how you should enter it when testing via Bubble:
And for the recipient number, this is our Twilio verified number:
And how you should enter it via Bubble:
Hope it helps.
Best,
Alex
I’ve checked all these things and I’m still getting the same error. Have you tried it again on your end? Is it working with your IDs and numbers?
Well I never fully resolved the issue with the test numbers, but once I upgraded to a paid account it worked. So I guess this will work for now.
Hi @manuelmaccou,
Thanks a lot for confirming. Yes, everything is working fine on our side. This is the reason for sure regarding paid account. It should be all up-and-running now.
If you like this plugin so far, could you please rate it by going to Plugins tab within Bubble editor? You can find the plugin by name and give it as many stars as it deserves. The more feedback we get, the more motivated we are to build great plugins!
Hey @alexandru, I’m facing the exact same error as Manuel, but for me the error started after I paid and upgraded. I’ve checked all the authorization parameters, and followed all the steps recommended in this thread, but still getting the same error, both in my Bubble environment and when I use your Live Demo. Any ideas why this is happening?
Hello, @hellosoundsurge
Thanks for reaching out.
Thanks for reaching out. Perhaps the encoded Account SID and Auth token are not correct on your side.
Could you please confirm whether or not it has been encoded in base64 this way:
AccountSID: Authtoken (generates a key)
And then pasted into Plugins tab this way:
Basic Generated_key
Also, make sure that your numbers are verified in the Twilio dashboard.
Just make sure when you enter it in the Plugins tab, it contains all the generated keys including the ‘==’ characters at the end.
Firstly, please make sure that you reviewed this documentation for correct connecting of the Twilio: Sending Messages | Twilio
I’m afraid that we can not reproduce or investigate this issue without more info. Can you please describe this case in more detail? Please attach all the necessary info like:
-
screenshots of your current settings for this plugin;
-
the description of Twilio settings;
Looking to hear you soon.
Best regards,