So I’ve been dealing with Bubble support and it is beyond frustrating. I start my journey at 9:09AM on December 3rd talking to a chat bot because it won’t just get you to a representative. So I finally get it to send a message to Bubble for a person to respond to. I get a response fairly quick (12/3/2024 @ 9:33AM) asking some additional information which I respond back with (12/3/2024 @ 9:50AM - they asked multiple questions I responded with the stuff I could immediately after their first message and this was answering the final question). So they say they are going to have to forward my request to another department and I was like okay. Remember at this point in time the website has been down all morning. Fast forward to December 4th @ 10:36AM (yes it has been over 24 hours even though during the waiting time I’m asking them over and over to respond to me) and the agent asks me a question that was already previous answered and I went ahead and answered it again anyways (12/4/2024 @ 10:37AM). So the representative asks me to delete the domain inside of the editor and re-add it so I did. So now they say I need to wait 48 hours for all the changes to propagate throughout the system. So they are basically saying to sit on my hands and wait while we can’t do any business processes since 12/3/2024 effectively making it over three days that the website will be down. No DNS records were changed on our end and looking at DNSChecker website I can see all the IP addresses that show inside of the Bubble dashboard are correct and properly setup as A records.
So I just want to give a word of caution that if you have anything this is critical to your business, maybe Bubble isn’t the best option because they clearly don’t care for how long you’re down. Also they did alert me that the team they sent to only works from 9AM - 6PM ET Monday - Friday. So basically if you have something happen/go down and it is outside of those hours you’re basically SOL.
I had once arund 10 days of me every day around 2 times explaining the problem with different story or examples for them to get it, yeah Bubble support not that good, it has become a meme now
You can disconnect the domain and visit yourappid.bubbleapps.io if it’s an internal app. That works instantly. Just re-add the domain after 48 hours and that’ll also connect basically instantly.
I do like this idea but we have systems like N8N, Power Automate, and other systems that feed data into our Bubble app and it would be difficult to make sure everything points to the mybubbleappid.bubbleapps.io domain and then switch it back after putting the domain back into place. I’m just afraid of breaking more things by trying to point them to a temporary place and then attempt to switch everything back once the domain stuff is sorted out. There are some URLs that we point to from our main website that are part of this Bubble app and are customer facing.
For this reason, it always makes sense to make external APIs point to yourapp.bubbleapps.io.
This will still work when a domain is connected. In other words, yourapp.bubbleapps.io is the permanent, immutable home of your app, and no matter when and where you change your domain, things like webhooks will still work.
Additionally, if you check the ‘redirect requests to domain’ checkbox, then anyone that does visit yourapp.bubbleapps.io will be redirected using a server-side redirect to yourdomain.com.
I am extremely grateful for what I have been able to do for myself and my business thanks to Bubble. But I always worry to have any problem and need to contact support, which is known to be horrible.
That’s good information to have and will definitely implement. So on the option “ redirect requests to domain’ checkbox” does that option only appear on the domain/email tab in settings. Because right now I don’t have that option and I will probably uncheck it if it is checked so that if this would happen again we could bypass until a resolution is found.
Immutable domain until you switch to dedicated @georgecollier and at this point you will spend a looooot of time rewriting / re intializing ALL the api calls+ running after all the external services pointing to you bubbleapp.io domain…
I think those days was thanksgiving in the USA that s why the team was probably reduced.
I didn’t know we didn’t need to re initialize when changing url. Re initialize is when adding parameter I imagine or of the result payload have to change ?
And for the switch to dedicated, yes Bubble team ask to change all url calls that will fail after migrating because the server url is not anymore the same, so I don’t think it will redirect on dedicated (server is bubble.is instead of io)
Hey Sarah! While George is correct, the domain will redirect, it is a 301 redirect and only works for GET requests. Any POST requests that get redirected are turned into GET requests and this causes any API call using the POST method to fail after migration. Reach out if you have any other questions!
You know what should be great and about I’m thinking of since a moment ?
Allow us to suggest edit in bubble documentation ! Because there’s so much hidden knowledge, and we could help complete the documentation with all that findings found by discussing in the forum or between dev, suggestions only, to moderate indeed !
and at this point you will spend a looooot of time rewriting / re intializing ALL the api calls+ running after all the external services pointing to you