Docker image fails on ARM64 (Raspberry Pi) with 'unknown user www' error

[CPloscaru]

• Your Hardware: "I am running this on a Raspberry Pi (ARM64)."

• The Error: "The core-billionmail container logs show the error user: unknown user www."

• The Logs:

chown: unknown user/group root:crontab
2025-09-06 17:16:27,028 fail2ban                [16]: ERROR   Could not find server
2025-09-06 17:16:27,225 fail2ban                [17]: ERROR   Could not find server
2025-09-06 17:16:32,445 INFO Set uid to user 0 succeeded
2025-09-06 17:16:32,445 INFO Set uid to user 0 succeeded
2025-09-06 17:16:32,451 INFO RPC interface 'supervisor' initialized
2025-09-06 17:16:32,451 INFO RPC interface 'supervisor' initialized
2025-09-06 17:16:32,451 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2025-09-06 17:16:32,451 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2025-09-06 17:16:32,451 INFO supervisord started with pid 1
2025-09-06 17:16:32,451 INFO supervisord started with pid 1
2025-09-06 17:16:33,454 INFO spawned: 'processes' with pid 21
2025-09-06 17:16:33,454 INFO spawned: 'processes' with pid 21
2025-09-06 17:16:33,456 INFO spawned: 'core' with pid 22
2025-09-06 17:16:33,456 INFO spawned: 'core' with pid 22
2025-09-06 17:16:33,459 INFO spawned: 'fail2ban' with pid 23
2025-09-06 17:16:33,459 INFO spawned: 'fail2ban' with pid 23
2025-09-06 17:16:33,461 INFO spawned: 'crond' with pid 24
2025-09-06 17:16:33,461 INFO spawned: 'crond' with pid 24
2025-09-06 17:16:33,463 WARN processes: has entered the UNKNOWN state and will no longer receive events, this usually indicates the process violated the eventlistener protocol
2025-09-06 17:16:33,463 WARN processes: has entered the UNKNOWN state and will no longer receive events, this usually indicates the process violated the eventlistener protocol
Server ready
2025-09-06T17:16:33 [ERRO] Failed to rename old table bm_relay: Table bm_relay_old already exists, skipping rename operation
Stack:
1.  billionmail-core/internal/service/database_initialization.init.9.func1
    /opt/core/internal/service/database_initialization/smtp_relay.go:84
2.  billionmail-core/internal/service/database_initialization.InitDatabase
    /opt/core/internal/service/database_initialization/database_initialization.go:67
3.  billionmail-core/internal/cmd.init.func1
    /opt/core/internal/cmd/cmd.go:62
4.  main.main
    /opt/core/main.go:13

2025-09-06T17:16:33.854+02:00 [DEBU] SetServerRoot path: /opt/billionmail/core/public/dist
2025-09-06T17:16:33.869+02:00 [INFO] pid[22]: http server started listening on [:5678]
2025-09-06T17:16:33.869+02:00 [INFO] pid[22]: https server started listening on [:5679]
2025-09-06T17:16:33.869+02:00 [INFO] openapi specification is disabled
2025-09-06 17:16:34,871 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-09-06 17:16:34,871 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-09-06 17:16:34,871 INFO success: crond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-09-06 17:16:34,871 INFO success: crond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Error reading project config directory: open ../conf/askai: no such file or directory
Error reading project config directory: open ../conf/askai: no such file or directory
2025-09-06 17:16:43,775 INFO success: core entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
2025-09-06 17:16:43,775 INFO success: core entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
2025-09-06 17:16:43,775 INFO success: fail2ban entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
2025-09-06 17:16:43,775 INFO success: fail2ban entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
Error reading project config directory: open ../conf/askai: no such file or directory
Error reading project config directory: open ../conf/askai: no such file or directory

• The Consequence: "This seems to cause the web service to fail, leading to 503 errors and preventing SSL certificate generation."

I receive:
`
Failed to apply for SSL certificate: error: one or more domains had a problem: [mail.mydomain.com] invalid authorization: acme: error: 403 :: urn:ietf:params:acme:error:unauthorized :: [MY_PUBLIC_IP]: Invalid response from http://mail.[MY_DOMAIN].com/.well-known/acme-challenge/tCeINxT5eDcOoyNN5nbZU2Qn6-ZuvGuq88vlFSWd2lQ: 503

[lotkmm]

You mentioned an "unknown user www" error — could you please clarify which log file this appeared in? It does not show up in the logs provided.

The SSL certificate failure (503/403) occurs because BillionMail serves HTTP on port 5678 by default, but ACME challenges require responses on port 80. The validation request cannot be processed under this setup.

Please note: SSL certificate application requires port 80 or a reverse proxy for ACME challenges.