Onlyoffice LXC not connecting with Nextcloud

[weav797]

I don't know if the problem lies with my implementation of the LXC, or if there's some other misconfiguration on my end or elsewhere. Basically, I cannot get OnlyOffice to talk to Nextcloud at all. I have tried configuring Nextcloud settings as much as I can to no avail. I am now wondering if there's something else going on and I would like to ask someone to investigate potential issues I may or may not be having. Down below is the exact command I used and the settings I used to deploy the LXC.

Exact command to deploy script:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/onlyoffice.sh)"

Settings applied when running script:
🧩 Using Advanced Settings on node nodename
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
🔐 Root Password: ********
🆔 Container ID: 205
🏠 Hostname: onlyoffice
💾 Disk Size: 20 GB
🧠 CPU Cores: 4
🛠️ RAM Size: 4096 MiB
🌉 Bridge: vmbr0
📡 IPv4: DHCP
📡 IPv6: SLAAC/AUTO
📡 APT-Cacher IP Address: Default
⚙️ Interface MTU Size: Default
🔍 DNS Search Domain: Host
📡 DNS Server IP Address: Host
🏷️ Vlan: Default
📡 Tags: community-script;word;excel;powerpoint;pdf
🔑 Root SSH Access: yes
🗂️ Enable FUSE Support: yes
🔍 Verbose Mode: no
🚀 Creating a ONLYOFFICE LXC using the above advanced settings
💡 Configuration file already exists at /opt/community-scripts/onlyoffice.conf
💡 Writing configuration to /opt/community-scripts/onlyoffice.conf
✔️ Valid Storage Found
✔️ Validated Storage | Container: local-lvm (Free: 610.7GB Used: 164.5GB)

Exact issue:
When deploying this LXC, it appears to be successful. I can access the IP in a browser to the welcome page. Can also put it behind a reverse proxy like Nginx Proxy Manager and still access it no problem. The issue lies when I connect the container to my nextcloud instance. If I tell it to connect to my reverse proxy https url without a secret key, it tries to generate one in Nextcloud and then errors out saying "invalid token." So I try investigating adding a secret key, which can be found at: /etc/onlyoffice/documentserver/local.json

The problem is that there is no option to add said key under here, which I am told should be under the services.CoAuthoring.secret.browser.string parameter. It does not exist. Per their documentation here listed on the welcome page, I try manually adding the parameter and generating a secret key elsewhere using another method. Although their documentation assumes you are deploying a bare metal linux instance or in docker, I just used their documentation regardless. Once I do that, I paste it into the json file, regenerate the config per their documentation by running systemctl restart ds-*. This method does not work either, and I still get the same "invalid token" error.

Summary:
Basically, I am not sure if my issue lies in a misconfig somewhere on my end or if there's something else going on with the script. Nextcloud just refuses to talk to the onlyoffice LXC I deployed, and I am hoping to ask for someone's help. Please let me know if you need more information for troubleshooting. I cannot find any other discussions for this LXC.

Edit: If it matters, I'll paste what I added into my local.json:

root@onlyoffice:~# cat /etc/onlyoffice/documentserver/local.json
{
  "services": {
    "CoAuthoring": {
      "token": {
        "enable": {
          "request": {
            "inbox": true,
            "outbox": true
          },
          "browser": true
        },
        "inbox": {
          "header": "Authorization"
        },
        "outbox": {
          "header": "Authorization"
        }
      },
      "secret": {
        "inbox": {
          "string": "anonymous"
        },
        "outbox": {
          "string": "anonymous
        },
        "session": {
          "string": "anonymous"
        },
        "browser": {
          "string": "anonymous"
        }
      }
    }

I added the "browser" var up above.