I have enabled the checkbox on the Domain/Email tab of my Bubble App as expected. However when I try to load a page that requires geolocation I get the “Origin does not have permission to use Geolocation service” which is, as far as I can tell, due to the fact that my SSL is not being used.
Any hints on what I might be doing wrong? Is there anything I am missing beyond getting the certificate from my domain registrar and selecting the checkbox in my App settings?
Hello @emmanuel thanks for your prompt reply. My question is because I have checked the checkbox and two things are happening:
(1) My App is trying to launch a normal http (as opposed to https) site and it is not being displayed at all, instead I get a generic website from my hosting see below:
It looks like your problems are upstream with your domain registrar. It appears that 1&1 is pointing to a 1&1 landing page, not your Bubble application.
So, Bubble may very well be applying the SSL certificate setting correctly, but 1&1 is still pointing to the landing page, not your Bubble app.
It’s possible that you have some conflicting records within your 1&1 setup or it hasn’t propagated. (Note: I don’t claim to fully understand time to live of DNS changes, but this should provide context).
Thanks @dan1 but this has been going on now for a few days (more than 3) so I suspect it is something else.
For some reason my app is not loading in https://. I have checked the SSL checkbox but when I click preview (in my App) it tries to open an http:// location.
Furhtermore, if I open the https:// version it opens a blank page with a valid certificate:
I am more than happy to reach out to my domain registrar if there is something that needs to happen on their end, it is just that I do not even know what I need to ask for. I have checked that the IP address for Type A and Type A WWW are as given by the App. As shown above I have checked that a SSL certificate is available for my domain.
Should I write a help request for Bubble? Could this be some sort of corner case and be a bug?
I am really at my wits end and I really do not know where to go from there. Any other help, hints, pointers would be much appreciated.
When I tried your domain (https) it gives me the good news. Have you another conflict app? I know you show the detail of Bubble acceptance, maybe time for a small bug report? I feel is something we missed
Thank you @JohnMark for your help. To be honest I gave up on 1&1.
Not sure what the issue was but (1) I Started my transfer to Google Domains as it seems like it is the recommended hosting for bubble, and (2) Got a “secondary” domain while the domain transfers occurs.
With the “sencodary” domain in Google I got it up and running in less than an hour.
