Hi @caeroa and @andy1,
I’m also in NC, and have been experiencing same issue. If you’re using the Zapier plugin and the “Trigger a Zap” action in a workflow, try deleting that action. Not ideal, but it fixed this problem for me yesterday.
It seems when the Zapier action is enabled, a script gets inserted into the bubble.is head element to enable Bubble to receive inputs from your Zap. Problem is, the script has its cross-origin header set to “anonymous”, and most browsers prevent content from loading w/o an Access-Control-Allow-Origin header defined. You can tell if this is your issue by opening the Chrome dev console when loading the page. Look for an error like the screenshot attached.
This also explains why you may be able to load the site on your phone, which uses a mobile browser, but not in Chrome/Firefox/Safari on a laptop/desktop.