Stuck at loading screen after fresh install

OS: Proxmox LXC Ubuntu 24
Browser version: Safari Version 26.3.1 (21623.2.7.11.7)
Additional information:

Output of docker exec -it onlyoffice-community-server service monoserve status

docker exec -it onlyoffice-community-server service monoserve status
● monoserve.service - FastCGI Mono server
     Loaded: loaded (/lib/systemd/system/monoserve.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2026-03-18 13:38:10 UTC; 4s ago
    Process: 26913 ExecStartPre=/bin/bash -c test -e /var/run/onlyoffice || install -m 755 -o onlyoffice -g nginx -d /var/run/onlyoffice; rm -f /var/run/onlyoffice/onlyoffice.socket /var/www/onlyoffice/WebStudio/mono_crash* /var/www/onlyoffice/WebStudio/core.*; (code=exited, status=0/SUCCESS)
   Main PID: 26915 (mono)
      Tasks: 4 (limit: 23091)
     Memory: 20.1M
        CPU: 1.047s
     CGroup: /system.slice/docker-7e26acee2a81433259e5a4ab5a0f6ba41715ab4753926c27ac5a788ecae30074.scope/system.slice/monoserve.service
             └─26915 /usr/bin/mono /usr/lib/hyperfastcgi/4.0/HyperFastCgi.exe /config=/etc/hyperfastcgi/onlyoffice /logfile=/var/log/onlyoffice/onlyoffice.log /loglevels=Error

Mar 18 13:38:10 7e26acee2a81 systemd[1]: Starting FastCGI Mono server...
Mar 18 13:38:10 7e26acee2a81 systemd[1]: Started FastCGI Mono server.
Mar 18 13:38:11 7e26acee2a81 hyperfastcgi4[26915]: WebConfigurationManager's LRUcache Size overriden to: 2000 (via MONO_ASPNET_WEBCONFIG_CACHESIZE)

Output of docker ps -a

docker ps -a
CONTAINER ID   IMAGE                                    COMMAND                  CREATED          STATUS          PORTS                                                                                                                                                                                        NAMES
94f623bf47e4   portainer/portainer-ce:sts               "/portainer"             29 minutes ago   Up 20 minutes   0.0.0.0:8000->8000/tcp, [::]:8000->8000/tcp, 0.0.0.0:9443->9443/tcp, [::]:9443->9443/tcp, 9000/tcp                                                                                           portainer
7e26acee2a81   onlyoffice/communityserver:12.7.1.1942   "/app/run-community-…"   42 minutes ago   Up 20 minutes   0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp, 3306/tcp, 5280/tcp, 9865-9866/tcp, 9871/tcp, 9882/tcp, 0.0.0.0:5222->5222/tcp, [::]:5222->5222/tcp, 9888/tcp   onlyoffice-community-server
6833a4363c06   onlyoffice/controlpanel:3.5.4.541        "/var/www/onlyoffice…"   46 minutes ago   Up 20 minutes   80/tcp, 443/tcp                                                                                                                                                                              onlyoffice-control-panel
8d2386fa786a   onlyoffice/documentserver:9.3.1.2        "/app/ds/run-documen…"   47 minutes ago   Up 20 minutes   80/tcp, 443/tcp                                                                                                                                                                              onlyoffice-document-server
cc0f9cf22a03   onlyoffice/elasticsearch:7.16.3          "/bin/tini -- /usr/l…"   49 minutes ago   Up 20 minutes   9200/tcp, 9300/tcp                                                                                                                                                                           onlyoffice-elasticsearch
4aa94f5fe721   mysql:8.0.29                             "docker-entrypoint.s…"   50 minutes ago   Up 19 minutes   3306/tcp, 33060/tcp                                                                                                                                                                          onlyoffice-mysql-server

Docker install with script from Installing ONLYOFFICE Workspace Community using the provided script

bash workspace-install.sh -ims false

Additional information:
After the fresh install the website is showing the loading screen, resulting in an Error 502. App Crash site. All containers are running.

Hello, thank you for the details.

We need a few additional checks from the Community Server side to understand what is failing during startup.

Please send us the following:

  • The full Community Server logs folder from inside the container: /var/log/onlyoffice/communityserver.
  • The output of these commands from the Community Server container: docker exec -it onlyoffice-community-server service monoserve status, docker exec -it onlyoffice-community-server service --status-all, and docker logs onlyoffice-community-server --tail 200.
  • Screenshots from the browser developer tools when the page is stuck, specifically the Console and Network tabs.

After we have these logs and checks, we will be able to see whether the issue is related to Community Server startup, Mono, or another internal service.