[GH-ISSUE #11782] Element Synapse install still broken #2478

Closed
opened 2026-02-26 12:52:35 +03:00 by kerem · 3 comments
Owner

Originally created by @summoningpixels on GitHub (Feb 11, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11782

Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

Element Synapse

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/elementsynapse.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.1.5/80cf92a64bef6889 (running kernel: 6.17.9-1-pve)

📝 Provide a clear and concise description of the issue.

Coming off 11755 I tried reinstalling the script again, but it fails still:

in line 44: exit code 1 (General error / Operation not permitted): while executing command systemctl enable -q --now matrix-synapse
--- Last 20 lines of silent log ---
Get:3 https://packages.matrix.org/debian trixie/main amd64 matrix-org-archive-keyring all 1.4 [3,360 B]
Preconfiguring packages ...
Fetched 51.4 MB in 1s (40.3 MB/s)
Selecting previously unselected package matrix-synapse-py3.
(Reading database ... 26487 files and directories currently installed.)
Preparing to unpack .../matrix-synapse-py3_1.147.0+trixie1_amd64.deb ...
Unpacking matrix-synapse-py3 (1.147.0+trixie1) ...
Selecting previously unselected package libpq5:amd64.
Preparing to unpack .../libpq5_17.7-0+deb13u1_amd64.deb ...
Unpacking libpq5:amd64 (17.7-0+deb13u1) ...
Selecting previously unselected package matrix-org-archive-keyring.
Preparing to unpack .../matrix-org-archive-keyring_1.4_all.deb ...
Unpacking matrix-org-archive-keyring (1.4) ...
Setting up matrix-org-archive-keyring (1.4) ...
Setting up libpq5:amd64 (17.7-0+deb13u1) ...
Setting up matrix-synapse-py3 (1.147.0+trixie1) ...
Created symlink '/etc/systemd/system/multi-user.target.wants/matrix-synapse.service' → '/usr/lib/systemd/system/matrix-synapse.service'.
/usr/sbin/policy-rc.d returned 101, not running 'start matrix-synapse.service'
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for libc-bin (2.41-12+deb13u1) ...

 📋 Log saved to: /root/.install-b5765111.log
  ✖️   Installation failed in container 117 (exit code: 1)

✔ Installation log: /tmp/install-lxc-117-b5765111.log

Log file (too big to paste here): https://paste.centos.org/view/78ae344f

🔄 Steps to reproduce the issue.

Run the script, type the name of the server and get the error above.

Paste the full error output (if available).

🖼️ Additional context (optional).

No response

Originally created by @summoningpixels on GitHub (Feb 11, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11782 ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? Element Synapse ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/elementsynapse.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.1.5/80cf92a64bef6889 (running kernel: 6.17.9-1-pve) ### 📝 Provide a clear and concise description of the issue. Coming off [11755](https://github.com/community-scripts/ProxmoxVE/issues/11755) I tried reinstalling the script again, but it fails still: ``` in line 44: exit code 1 (General error / Operation not permitted): while executing command systemctl enable -q --now matrix-synapse --- Last 20 lines of silent log --- Get:3 https://packages.matrix.org/debian trixie/main amd64 matrix-org-archive-keyring all 1.4 [3,360 B] Preconfiguring packages ... Fetched 51.4 MB in 1s (40.3 MB/s) Selecting previously unselected package matrix-synapse-py3. (Reading database ... 26487 files and directories currently installed.) Preparing to unpack .../matrix-synapse-py3_1.147.0+trixie1_amd64.deb ... Unpacking matrix-synapse-py3 (1.147.0+trixie1) ... Selecting previously unselected package libpq5:amd64. Preparing to unpack .../libpq5_17.7-0+deb13u1_amd64.deb ... Unpacking libpq5:amd64 (17.7-0+deb13u1) ... Selecting previously unselected package matrix-org-archive-keyring. Preparing to unpack .../matrix-org-archive-keyring_1.4_all.deb ... Unpacking matrix-org-archive-keyring (1.4) ... Setting up matrix-org-archive-keyring (1.4) ... Setting up libpq5:amd64 (17.7-0+deb13u1) ... Setting up matrix-synapse-py3 (1.147.0+trixie1) ... Created symlink '/etc/systemd/system/multi-user.target.wants/matrix-synapse.service' → '/usr/lib/systemd/system/matrix-synapse.service'. /usr/sbin/policy-rc.d returned 101, not running 'start matrix-synapse.service' Processing triggers for man-db (2.13.1-1) ... Processing triggers for libc-bin (2.41-12+deb13u1) ... 📋 Log saved to: /root/.install-b5765111.log ✖️ Installation failed in container 117 (exit code: 1) ✔ Installation log: /tmp/install-lxc-117-b5765111.log ``` Log file (too big to paste here): https://paste.centos.org/view/78ae344f ### 🔄 Steps to reproduce the issue. Run the script, type the name of the server and get the error above. ### ❌ Paste the full error output (if available). - ### 🖼️ Additional context (optional). _No response_
kerem 2026-02-26 12:52:35 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@MickLesk commented on GitHub (Feb 11, 2026):

Image
<!-- gh-comment-id:3882817360 --> @MickLesk commented on GitHub (Feb 11, 2026): <img width="928" height="777" alt="Image" src="https://github.com/user-attachments/assets/e5780b75-5dfa-49d8-aef4-5bf668a64c7e" />
Author
Owner

@summoningpixels commented on GitHub (Feb 11, 2026):

Weird, second attempt worked for me too without a hitch. Thanks and closed!

<!-- gh-comment-id:3882864000 --> @summoningpixels commented on GitHub (Feb 11, 2026): Weird, second attempt worked for me too without a hitch. Thanks and closed!
Author
Owner

@jlucero2 commented on GitHub (Feb 14, 2026):

Hi there, I just got the same error "[2026-02-14 16:03:12] [ERROR] in line 44: exit code 1 (General error / Operation not permitted): while executing command systemctl enable -q --now matrix-synapse"

I'm running:
proxmox-ve: 9.1.0 (running kernel: 6.17.2-1-pve)
pve-manager: 9.1.5 (running version: 9.1.5/80cf92a64bef6889)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.17.9-1-pve-signed: 6.17.9-1
proxmox-kernel-6.17: 6.17.9-1
proxmox-kernel-6.17.2-1-pve-signed: 6.17.2-1

I used the following command to install:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/elementsynapse.sh)"

And I selected default install, and named the server. I ran the script several times after seeing that it worked on the second try for summoningpixels. And it did not work three or four times in a row for me.

But then on about the fifth try, I used the server name "test" and it worked. Every other time, I had used a server name with spaces or under scores. I deleted the successful attempt, reran with my original server name variations, all failed (all had spaces or underscores). Then I tried the server name I wanted as all one word with no spaces and no special characters. And it worked.

Hope that helps someone else! Also not sure if it's worth reopening this as an issue.

(For clarity, what I'm saying is that, for example, the server name "bonk town" doesn't work, "bonk_town" doesn't work, but "bonktown" does)

<!-- gh-comment-id:3902561312 --> @jlucero2 commented on GitHub (Feb 14, 2026): Hi there, I just got the same error "[2026-02-14 16:03:12] [ERROR] in line 44: exit code 1 (General error / Operation not permitted): while executing command systemctl enable -q --now matrix-synapse" I'm running: proxmox-ve: 9.1.0 (running kernel: 6.17.2-1-pve) pve-manager: 9.1.5 (running version: 9.1.5/80cf92a64bef6889) proxmox-kernel-helper: 9.0.4 proxmox-kernel-6.17.9-1-pve-signed: 6.17.9-1 proxmox-kernel-6.17: 6.17.9-1 proxmox-kernel-6.17.2-1-pve-signed: 6.17.2-1 I used the following command to install: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/elementsynapse.sh)" And I selected default install, and named the server. I ran the script several times after seeing that it worked on the second try for summoningpixels. And it did not work three or four times in a row for me. But then on about the fifth try, I used the server name "test" and it worked. Every other time, I had used a server name with spaces or under scores. I deleted the successful attempt, reran with my original server name variations, all failed (all had spaces or underscores). Then I tried the server name I wanted as all one word with no spaces and no special characters. And it worked. Hope that helps someone else! Also not sure if it's worth reopening this as an issue. (For clarity, what I'm saying is that, for example, the server name "bonk town" doesn't work, "bonk_town" doesn't work, but "bonktown" does)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#2478
No description provided.