starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 01:06:06 +03:00

[GH-ISSUE #7073] Synapse Bridge #1511

New issue

Closed

opened 2026-02-26 12:49:17 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 12:49:17 +03:00

Owner

Originally created by @Acharab on GitHub (Aug 21, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/7073

Originally assigned to: @michelroegl-brunner on GitHub.

🌟 Briefly describe the feature

Synapse Bridge

📝 Detailed description

This feature request is to add support for bridges to the existing Proxmox Element Synapse helper script. This functionality would enable the Synapse server to seamlessly communicate with other messaging platforms like WhatsApp and Signal, similar to how bridges work in other Matrix instances.

💡 Why is this useful?

The current helper script simplifies the deployment of a Matrix Synapse server on a Proxmox virtual machine. However, its utility is limited to communication within the Matrix network. To make the Synapse instance a more comprehensive messaging solution, it needs the ability to connect to external services. Integrating bridges would provide this functionality, allowing users to:

Consolidate their messaging into a single client (Element).
Improve privacy by routing traffic through their self-hosted server.
Enhance convenience by managing conversations from multiple platforms in one place.

Originally created by @Acharab on GitHub (Aug 21, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/7073 Originally assigned to: @michelroegl-brunner on GitHub. ### 🌟 Briefly describe the feature Synapse Bridge ### 📝 Detailed description This feature request is to add support for bridges to the existing Proxmox Element Synapse helper script. This functionality would enable the Synapse server to seamlessly communicate with other messaging platforms like WhatsApp and Signal, similar to how bridges work in other Matrix instances. ### 💡 Why is this useful? The current helper script simplifies the deployment of a Matrix Synapse server on a Proxmox virtual machine. However, its utility is limited to communication within the Matrix network. To make the Synapse instance a more comprehensive messaging solution, it needs the ability to connect to external services. Integrating bridges would provide this functionality, allowing users to: Consolidate their messaging into a single client (Element). Improve privacy by routing traffic through their self-hosted server. Enhance convenience by managing conversations from multiple platforms in one place.

kerem

2026-02-26 12:49:17 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-26 12:49:17 +03:00

Author

Owner

@michelroegl-brunner commented on GitHub (Aug 21, 2025):

Any link to any documentation how this can be configured? Any lxc has access to your LAN and Internet anyway, otherwise you could not install.
Can you precisice your request pls?

@michelroegl-brunner commented on GitHub (Aug 21, 2025): Any link to any documentation how this can be configured? Any lxc has access to your LAN and Internet anyway, otherwise you could not install. Can you precisice your request pls?

kerem commented

2026-02-26 12:49:17 +03:00

Author

Owner

@Acharab commented on GitHub (Aug 21, 2025):

Thanks for your response!

The bridge client should run inside a Docker container, as described in the documentation at this link: https://docs.mau.fi/bridges/go/setup.html?bridge=whatsapp

In my view, when creating the container, you're asked whether you want to add a bridge, and at that point, you can select the desired bridge.

With this setup, you can also add other messaging servers to your Synapse and Matrix servers via the bridge, allowing for integration with external services.

Let me know if you have any further questions.

@Acharab commented on GitHub (Aug 21, 2025): Thanks for your response! The bridge client should run inside a Docker container, as described in the documentation at this link: https://docs.mau.fi/bridges/go/setup.html?bridge=whatsapp In my view, when creating the container, you're asked whether you want to add a bridge, and at that point, you can select the desired bridge. With this setup, you can also add other messaging servers to your Synapse and Matrix servers via the bridge, allowing for integration with external services. Let me know if you have any further questions.

kerem commented

2026-02-26 12:49:17 +03:00

Author

Owner

@MickLesk commented on GitHub (Sep 23, 2025):

I just reviewed this request and I think integrating bridges directly into the Synapse script would massively bloat it. Each bridge has different dependencies, configs, and use cases, which would easily add 200–400 extra lines of code. That would make the script harder to maintain in the long run.

Instead, I’d suggest either writing a separate guide or adding a link on the website pointing to the official bridge documentation. This keeps the main script lean and maintainable, while still giving users a clear path if they want to set up bridges like WhatsApp, Signal, or Discord.

@MickLesk commented on GitHub (Sep 23, 2025): I just reviewed this request and I think integrating bridges directly into the Synapse script would massively bloat it. Each bridge has different dependencies, configs, and use cases, which would easily add 200–400 extra lines of code. That would make the script harder to maintain in the long run. Instead, I’d suggest either writing a separate guide or adding a link on the website pointing to the official bridge documentation. This keeps the main script lean and maintainable, while still giving users a clear path if they want to set up bridges like WhatsApp, Signal, or Discord.

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#1511

No description provided.

Rows
Columns