Nextcloud version (eg, 24.0.1): 30.0.5.1 from nextcloud-snap 30.0.5snap1
Talk Server version (eg, 14.0.2): 20.1.3
Custom Signaling server configured: no
Custom TURN server configured: no
Custom STUN server configured: no
In case the web version of Nextcloud Talk is involved:
Operating system (eg, Windows/Ubuntu/…): linux mint 22.1
Browser name and version (eg, Chrome v101): firefox 134.0.2
In case mobile Nextcloud Talk apps are involved:
Talk iOS version (eg, 14.0.2): none
Talk Android version (eg, 14.0.2): 20.1.1
The issue you are facing:
I’ve installed NCtalk and talk matterbridge 1.31.1026000 apps. So far, I’ve been able to set-up and run a bridge between NCtalk and telegram.
Now I’d like to use a custom matterbridge binary and configuration.
I have downloaded matterbridge binary, made it executable and stored in /var/snap/nextcloud/manual_addon/matterbridge folder; in the same place I have created matterbridge.toml file. Then I have issued the command:
sudo nextcloud.occ config:app:set spreed matterbridge_binary --value=“/var/snap/nextcloud/manual_addon/matterbridge/matterbridge-1.26.0-linux-64bit”
with output
Config value ‘matterbridge_binary’ for app ‘spreed’ is now set to ‘/var/snap/nextcloud/manual_addon/matterbridge/matterbridge-1.26.0-linux-64bit’, stored as mixed in fast cache
To double check:
sudo nextcloud.occ config:app:get spreed matterbridge_binary --details
gives
- app: spreed
- key: matterbridge_binary
- value: /var/snap/nextcloud/manual_addon/matterbridge/matterbridge-1.26.0-linux-64bit
- type: mixed
- lazy: false
- sensitive: false
All these commands seem to have no effect on matterbridge, i.e the original config is still valid. Even after a
sudo snap restart nextcloud
behavior does not change.
I have already asked in nextcloud-snap github, they suggested me to ask here.
Any suggestion is welcome.
Is this the first time you’ve seen this error? (Y/N): y
Steps to replicate it:
- install talk and talk matterbridge in nextcloud snap
- create a NCtalk-telegram bridge (see matterbridge doc and be careful to get the right channel ID with standard matterbridge binary and config
- download/compile a custom matterbridge binary, make it executable and store it in /var/snap/nextcloud/manual_addon/matterbridge folder;
- in the same place, create a custom matterbridge.toml file (I have copied the existing /tmp/snap-private-tmp/snap.nextcloud/tmp/bridge-xxxx.toml file and only renamed the sections and gateway therein)
- change matterbridge binary in talk config:
sudo nextcloud.occ config:app:set spreed matterbridge_binary --value=“/var/snap/nextcloud/manual_addon/matterbridge/matterbridge-1.26.0-linux-64bit” - check matterbridge log in order to see if new config has been applied (in my case: no).
The output of your Nextcloud log in Admin > Logging or errors in nextcloud.log in /var/www/:
file_get_contents(/tmp/bridge-td7s4pyt.log): Failed to open stream: No such file or directory at /var/snap/nextcloud/46218/nextcloud/extra-apps/spreed/lib/MatterbridgeManager.php#91
Any suggestion is welcome. Thanks in advance