"Invalid origin" upon login

CMS Bridge
1

Screenshot 2026-05-13 at 3.38.00 PM
Screenshot 2026-05-13 at 3.38.00 PM642×250 9.27 KB

Hi. I had previously used NoBull to sync a couple sites from Airtable to Webflow and just transitioned to CMS Bridge finally. When I tried to install the extension and login via the Airtable macOS app, I kept getting an “Invalid origin” message and it wouldn’t let me login. When I tried in Safari (my primary browser), I received the same error. Finally, I tried it in Chrome and it was able to login correctly and I got my sync going.

While I was able to do this workaround to get it working, I wanted to try and get it working in at least one, if not both of these other places. Grok tells me this is a common OAuth issue, but I don’t see any other forum topics about this. I also tried turning off “prevent cross-site tracking” and “hide IP address” in Safari and neither seemed to work. I also switched my default browser to Chrome to see if I could get the Airtable macOS app to login and it opens Chrome, but gives that same “Invalid origin” error, even though I’m logged in just fine in another tab.

I think I’ve exhausted everything I can think of. Airtable is at 1.6.6 (latest) and macOS is on Tahoe 26.5 (latest). Any settings I’ve got wrong? Or do I have to live with this workaround to work with CMS Bridge? Thanks everyone!

2

Hey @aaronkaiser, “invalid origin” during CMS Bridge login is definitely an unusual one — not something we see documented on our end, so we want to make sure the right people dig into this rather than just guessing at a fix.

Before we loop in the team, a few quick questions to help narrow things down:

  1. When you say “Airtable macOS app” — are you logging into your Finsweet account from inside the Airtable Extension within the desktop app, or launching the login from a separate browser tab?
  2. Has the login via Chrome worked consistently every time, or was that a one-time success?
  3. Are you on a VPN or corporate network when this happens in Safari or the Airtable app?

One thing worth trying in the meantime — if you haven’t already, give incognito/private mode in Safari a shot. It rules out cached state or extension interference that could be affecting the OAuth flow.

That said, we’re flagging this to the team regardless. An “invalid origin” error in the Finsweet login flow may need a look on the backend side. :folded_hands: