Karakeep browser extension gets blocked by CORS when self-hosting the Karakeep app

[maestro-pkt]

Describe the Bug

Hello, the Karakeep browser extension can talk to https://cloud.karakeep.app fine; but when I host karakeep at my own domain there are CORS errors in the extension

Steps to Reproduce

1. Enter a self-hosted url when the browser extension opens
2. Then click configure
3. Right-click on the extension window and choose Inspect. The chromium devtools opens.
4. Choose either the console tab or the network tab in the devtools.
5. Back in the Karakeep extension, enter either the username/password or the API for your self-hosted instance.
6. Click login or Login with API key

In the devtools, there will be a CORS error.

Expected Behaviour

The extension should authenticate with the self-hosted Karakeep.

Screenshots or Additional Context

Device Details

No response

Exact Karakeep Version

1.2.7 (extension)

Have you checked the troubleshooting guide?

• I have checked the troubleshooting guide and I haven't found a solution to my problem

[m3ktek]

I had this issue when I only opened port 3022 locally, once I opened port 3000 as well the browser app then authenticated.
Hope this helps.

[MohamedBassem]

Karakeep's default CORS policy is very permissive. Historically, the cors problems have been caused by the reverse proxies in front of karakeep (e.g CasaOS has been a constant source of pain for this issue).

The only other issue I'm aware of for CORS is if you're using custom headers, but it doesn't seem like you are in this case.

[maestro-pkt]

Thank you! It was the reverse proxy (Traefik in my case). When I set it to the IP/port combo it worked fine. I can get by using the IP/port combo so I consider this solved.