[Bug]: We had an unknown problem opening “My-Finances-XXXXX”.

[ghost]

Verified issue does not already exist?

• I have searched and found no existing issue

What happened?

Hello,
I just pulled and run the latest docker image :

docker pull ghcr.io/actualbudget/actual-server:latest
docker run --pull=always --restart=unless-stopped -d -p 8083:5006 -e PUID=1000 -e PGID=1000 -v /var/lib/docker/volumes/actualbudget/data:/data --name actualbudget ghcr.io/actualbudget/actual-server:latest

I published my application through a WAF rules of a Sophos XG appliance.
I'm able to run the application with HTTPS, to sign in but when i select the default file or a new created one, i alway get an error :
We had an unknown problem opening “My-Finances-XXXX”.

I check my docker volume (/data) and i can see it has created 2 folders "server-files" and "user-files". So my docker configuration seems OK. To be shure i added the PUID and GUID of the root user to avoid any write issue.

In the console of my browser, i can see an error in the migrations.ts file :
The content of the "db" parameter of the "applySQL" function is :

<title>403 Forbidden</title>

Forbidden

You don't have permission to access this resource.

I found a similar issue, but the solution is to clear cookies and cache. It does not works for me.
I removed and deployed again the application but without more success.

Am i missing something ?

Thank you for your help.

What error did you receive?

We had an unknown problem opening “My-Finances-XXXX

Output of the browser console :

Reading meta...
Got meta for documents-Actual-My-Finances-d2f6bb0-db.sqlite: [object Object]
sql-wasm.js:119 Opened!
migrations.ts:112 Error applying sql:

<title>403 Forbidden</title>

Forbidden

You don't have permission to access this resource.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox, Chrome

Operating System

Linux

[ghost]

I tried with another reverse proxy and it works fine.
This issue is due to the reverse proxy function of the Sophos XG firewall.

Have you any idea what can cause this behavior ?

[ghost]

I found the reason. The WAF (Sophos) block some request detected as a potential attack ... if i disable all security it works fine.

[ghost]

Ticket close