Problem: Even though the end to bridge option is enabled, the bridge is not configured correctly.
You can reproduce it by installing the bridge, using the the e2be option and checking the config.yaml. The bot will not work neither and error out with "This bridge is not configured to use encryption"
Desired goals
install/remove the optional dependencies
enable at least the config option to allow encrypted chats. If that works reliably, the “force encryption“ option should be enabled.
Changes that could resolve it:
add a variable in the config, like it is done with __SERVER_NAME__ to corrispond to the switch
install python-olm, pycryptodome and unpaddedbase64
but im not an expert, its more of an educated guess from the mautrx docs and looking at the config scripts. A low effort, imho shitty workaround would be to remove the e2be switch.
Environment: VPS with Debian 10 running YH 4.3.5 (stable).
Problem: Even though the end to bridge option is enabled, the bridge is not configured correctly.
You can reproduce it by installing the bridge, using the the e2be option and checking the config.yaml. The bot will not work neither and error out with "This bridge is not configured to use encryption"
Desired goals
Changes that could resolve it:
__SERVER_NAME__
to corrispond to the switchbut im not an expert, its more of an educated guess from the mautrx docs and looking at the config scripts. A low effort, imho shitty workaround would be to remove the e2be switch.
Environment: VPS with Debian 10 running YH 4.3.5 (stable).
This is the same with other mautrix bridges. See https://github.com/YunoHost-Apps/mautrix_whatsapp_ynh/issues/40 and https://github.com/YunoHost-Apps/mautrix_signal_ynh/issues/35