Deploy with custom port - 502 bad Gateway

[whowantsmybigdata]

Deploying without docker was working but since there is no offical builder for the arm anymore I wanted to switch and now I get an 502 Bad Gateway and in seahub-error.log

[error] 69#69: *44 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.1, server: [my domain], request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:8000/", host: "[my domain]:8001"

System:

• arm64 Raspbian Bookworm
• Seafile-version as in docker-compose.yml is seafile-mc:latest so by the time of writing 11.0.2

I have another service using ports 80 and 443, so I need to use a different one (undockerized I used 8003). Unfortunately there is no manual for that and I don't get the solution mentioned here because I have no idea what is the bootstrap.conf is and didn't manage to get it working while trying to figure it out.

• I copied the conf, ccnet (as it was asking for it) and seahub-data folders and updated the conf-files to my local-ip.
• For mariadb I use the bind-method as mentioned in the manual to bind it to that same local-ip.
• I use ufw with port 8001/tcp open but also tried it with ufw disabled and I have portforwarding set in my router to forward port 8001/tcp.

I tried the following:
in docker-compose.yml under ports: "8001:8001" (502 error from nginx but no log?!) or "443:443" (port already allocated error from docker) or "8001:443" (connection failed)
and SEAFILE_SERVER_HOSTNAME=[my domain]:8001 (as in ccnet.conf) or SEAFILE_SERVER_HOSTNAME=[my domain]

under nginx.conf listen 8001 http2 ssl and proxy_set_header Host $http_host; or proxy_set_header Host $host:8001 (which I was using without docker).

I don't know what to try next. Switching back to the unofficial non-docker arm64 build for Seafile 10, with the same nginx.conf, same data and same database is working normally.

Thanks for your help