/var/log/matrix-deploy.log on LXC 106 shows the last matrix-deploy run on 2026-05-15, and /opt/matrix-config there is still at d3ee2e2. The webhook service is active and hooks.json has the matrix-deploy hook, but pushes to main never trigger it. So cinny/config.json and cinny/nginx.conf changes merged since May have not been deployed automatically.
Found while rolling out cinny #43 (2026-09-27): the call-origin nginx.conf and the elementCallUrl config change had to be installed by hand.
config.json: edited in place, because the live file carries the injected gifApiKey; backup is in /root/config-backups/.
The live files now match main.
To check:
whether the Gitea repo webhook for LXC 106 exists, is enabled and points at the right URL/port (README: :9000 is bound to 127.0.0.1, :9001 is webhook-lotus)
whether MATRIX_DEPLOY_SECRET matches the webhook's secret (the signature check)
the Gitea webhook delivery log for recent pushes.
Note: when it does fire again, lxc106-cinny.sh would cp cinny/config.json over the live file and blank the injected gifApiKey. The script should re-inject it, or merge keys like the in-place edit did.
`/var/log/matrix-deploy.log` on LXC 106 shows the last `matrix-deploy` run on **2026-05-15**, and `/opt/matrix-config` there is still at `d3ee2e2`. The webhook service is `active` and `hooks.json` has the `matrix-deploy` hook, but pushes to `main` never trigger it. So `cinny/config.json` and `cinny/nginx.conf` changes merged since May have **not** been deployed automatically.
Found while rolling out cinny #43 (2026-09-27): the call-origin `nginx.conf` and the `elementCallUrl` config change had to be installed by hand.
- `nginx.conf`: backup `sites-available/cinny.bak-20260927110949`, installed behind `nginx -t`.
- `config.json`: edited in place, because the live file carries the injected `gifApiKey`; backup is in `/root/config-backups/`.
The live files now match `main`.
To check:
- whether the Gitea repo webhook for LXC 106 exists, is enabled and points at the right URL/port (README: `:9000` is bound to 127.0.0.1, `:9001` is `webhook-lotus`)
- whether `MATRIX_DEPLOY_SECRET` matches the webhook's secret (the signature check)
- the Gitea webhook delivery log for recent pushes.
Note: when it does fire again, `lxc106-cinny.sh` would `cp cinny/config.json` over the live file and **blank the injected `gifApiKey`**. The script should re-inject it, or merge keys like the in-place edit did.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
/var/log/matrix-deploy.logon LXC 106 shows the lastmatrix-deployrun on 2026-05-15, and/opt/matrix-configthere is still atd3ee2e2. The webhook service isactiveandhooks.jsonhas thematrix-deployhook, but pushes tomainnever trigger it. Socinny/config.jsonandcinny/nginx.confchanges merged since May have not been deployed automatically.Found while rolling out cinny #43 (2026-09-27): the call-origin
nginx.confand theelementCallUrlconfig change had to be installed by hand.nginx.conf: backupsites-available/cinny.bak-20260927110949, installed behindnginx -t.config.json: edited in place, because the live file carries the injectedgifApiKey; backup is in/root/config-backups/.The live files now match
main.To check:
:9000is bound to 127.0.0.1,:9001iswebhook-lotus)MATRIX_DEPLOY_SECRETmatches the webhook's secret (the signature check)Note: when it does fire again,
lxc106-cinny.shwouldcp cinny/config.jsonover the live file and blank the injectedgifApiKey. The script should re-inject it, or merge keys like the in-place edit did.