CORS Error When Using Cato VPN

If you’re seeing a CORS (Cross-Origin Resource Sharing) error when connected to your company’s VPN, it’s likely caused by Cato VPN’s Remote Browser Isolation (RBI) intercepting your network traffic. This isn’t a Bitwave configuration issue it’s a security filter blocking certain web requests.

What does the “CORS” error mean?

A CORS error appears when your browser blocks a request Bitwave is trying to make behind the scenes.
It’s a browser-level security feature, not an issue with your account or setup.

Why does this happen on Cato VPN?

Cato VPN’s RBI (Remote Browser Isolation) inspects and reroutes secure (HTTPS) traffic through
rbi.catonetwork.com.
When it does this, Bitwave’s payment or API requests get interrupted, and your browser throws a CORS error.

How can I confirm this is the issue?

You can confirm it’s VPN-related if:

• Bitwave works fine when disconnected from the VPN

• The browser console shows redirects to rbi.catonetwork.com

• Other users on the same network report the same problem

If any of these apply, the VPN is the cause.

How to fix or work around the issue

You or your IT team can:

•Whitelist Bitwave domains (app.bitwave.io, api.bitwave.io) in Cato.

• Disable RBI inspection for trusted financial tools.

• Temporarily disconnect from VPN and retry (if company policy allows).

• Switch to mobile or home Wi-Fi as a short-term workaround.

Is this a Bitwave issue?

No. Bitwave’s configuration is correct the CORS block is triggered by your network’s security layer. Your data is safe; it’s just being overprotected by the VPN.

Who should I contact for help?

Start with your IT or network administrator to adjust VPN/RBI settings. If you’ve already tested outside the VPN and the issue continues, contact Bitwave Support for help confirming next steps.