Troubleshooting
QR login, passwords, ports, injection, and image pulls
noVNC never connects / spins forever
- Confirm port
6081is published. Official templates do not publish5900. - There is no shared default remote-desktop password. The first start generates a random one and prints it once; later restarts will not print it again — use the value you saved.
- High CPU and no handshake: pass
--ulimit nofile=65536:1048576(already in official compose).
docker logs snowluma 2>&1 | grep -E "远程桌面密码:|remote desktop password:" | tail -n 1Cannot find the WebUI password
The bootstrap password is printed only on the first start of a fresh data volume. Reusing a volume will not print a new one.
docker logs snowluma 2>&1 | grep -E "临时密码|initial credentials" | tail -n 1A bot cannot reach 3000 / 3001
- In Docker, OneBot should listen on
0.0.0.0. Upgrading the image rewrites a leftover loopback default; a host you set yourself is left alone. - On the compose network use the service name
snowluma, not127.0.0.1. - Send the access token.
Injection fails / QQ runs but never comes online
- You still need
SYS_PTRACEandseccomp=unconfined. - Do not start a second QQ as root inside the container.
ptrace_scope=3refuses ptrace outright.- Do not delete the
qq-gateway-data,qq-client-config, orqq-client-datavolumes.
Image pull hangs in China
That hop is Docker Hub. The installer retries with prefixes. Manually:
docker pull docker.1ms.run/motricseven7/snowluma:latest
docker tag docker.1ms.run/motricseven7/snowluma:latest motricseven7/snowluma:latestOn 1Panel / Baota, set a registry mirror in the panel. The installer will not rewrite daemon.json.
Upgrade asks you to scan again
Recreating the container can look like a new device. Keep the volumes. If you still must log in again, scan via noVNC.
Was this page helpful?
Last updated on