Are you in the right dir?
cd /opt/mautrix-telegram
Maybe you missed that?
source ./bin/activate
Did you get errors at pip install ?
pip install --upgrade mautrix-telegram[all]
1 Like
Thanks for your help 
Here is what I done with your suggestions:
[root@matrix opt]# cd /opt/mautrix-telegram
[root@matrix mautrix-telegram]# source ./bin/activate
(mautrix-telegram) [root@matrix mautrix-telegram]# python -m mautrix_telegram -g
/opt/mautrix-telegram/bin/python: No module named mautrix_telegram
(mautrix-telegram) [root@matrix mautrix-telegram]# pip install --upgrade mautrix-telegram[all]
Collecting mautrix-telegram[all]
Downloading https://files.pythonhosted.org/packages/c7/f9/19692e42d925e7d49d48930360344d0516b105332a450ed9e2327878d011/mautrix-telegram-0.6.1.tar.gz (142kB)
100% |████████████████████████████████| 143kB 2.8MB/s
Collecting aiohttp<4,>=3.0.1 (from mautrix-telegram[all])
Could not find a version that satisfies the requirement aiohttp<4,>=3.0.1 (from mautrix-telegram[all]) (from versions: 0.1, 0.2, 0.3, 0.4, 0.4.1, 0.4.2, 0.4.3, 0.4.4, 0.5.0, 0.6.0, 0.6.1, 0.6.2, 0.6.3, 0.6.4, 0.6.5, 0.7.0, 0.7.1, 0.7.2, 0.7.3, 0.8.0, 0.8.1, 0.8.2, 0.8.3, 0.8.4, 0.9.0, 0.9.1, 0.9.2, 0.9.3, 0.10.0, 0.10.1, 0.10.2, 0.11.0, 0.12.0, 0.13.0, 0.13.1, 0.14.0, 0.14.1, 0.14.2, 0.14.3, 0.14.4, 0.15.0, 0.15.1, 0.15.2, 0.15.3, 0.16.0, 0.16.1, 0.16.2, 0.16.3, 0.16.4, 0.16.5, 0.16.6, 0.17.0, 0.17.1, 0.17.2, 0.17.3, 0.17.4, 0.18.0, 0.18.1, 0.18.2, 0.18.3, 0.18.4, 0.19.0, 0.20.0, 0.20.1, 0.20.2, 0.21.0, 0.21.1, 0.21.2, 0.21.4, 0.21.5, 0.21.6, 0.22.0a0, 0.22.0b0, 0.22.0b1, 0.22.0b2, 0.22.0b3, 0.22.0b4, 0.22.0b5, 0.22.0b6, 0.22.0, 0.22.1, 0.22.2, 0.22.3, 0.22.4, 0.22.5, 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.5, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.2.0, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 2.0.0rc1, 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6.post1, 2.0.7, 2.1.0, 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5, 2.3.0a4, 2.3.0, 2.3.1, 2.3.2b2)
No matching distribution found for aiohttp<4,>=3.0.1 (from mautrix-telegram[all])
You are using pip version 9.0.1, however version 20.0.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
(mautrix-telegram) [root@matrix mautrix-telegram]# pip install --upgrade pip
Cache entry deserialization failed, entry ignored
Collecting pip
Using cached https://files.pythonhosted.org/packages/54/0c/d01aa759fdc501a58f431eb594a17495f15b88da142ce14b5845662c13f3/pip-20.0.2-py2.py3-none-any.whl
Installing collected packages: pip
Found existing installation: pip 9.0.1
Uninstalling pip-9.0.1:
Successfully uninstalled pip-9.0.1
Successfully installed pip-20.0.2
(mautrix-telegram) [root@matrix mautrix-telegram]# python -m mautrix_telegram -g
/opt/mautrix-telegram/bin/python: No module named mautrix_telegram
(mautrix-telegram) [root@matrix mautrix-telegram]# pip install --upgrade mautrix-telegram[all]
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
Collecting mautrix-telegram[all]
Using cached mautrix-telegram-0.6.1.tar.gz (142 kB)
ERROR: Could not find a version that satisfies the requirement aiohttp<4,>=3.0.1 (from mautrix-telegram[all]) (from versions: 0.1, 0.2, 0.3, 0.4, 0.4.1, 0.4.2, 0.4.3, 0.4.4, 0.5.0, 0.6.0, 0.6.1, 0.6.2, 0.6.3, 0.6.4, 0.6.5, 0.7.0, 0.7.1, 0.7.2, 0.7.3, 0.8.0, 0.8.1, 0.8.2, 0.8.3, 0.8.4, 0.9.0, 0.9.1, 0.9.2, 0.9.3, 0.10.0, 0.10.1, 0.10.2, 0.11.0, 0.12.0, 0.13.0, 0.13.1, 0.14.0, 0.14.1, 0.14.2, 0.14.3, 0.14.4, 0.15.0, 0.15.1, 0.15.2, 0.15.3, 0.16.0, 0.16.1, 0.16.2, 0.16.3, 0.16.4, 0.16.5, 0.16.6, 0.17.0, 0.17.1, 0.17.2, 0.17.3, 0.17.4, 0.18.0, 0.18.1, 0.18.2, 0.18.3, 0.18.4, 0.19.0, 0.20.0, 0.20.1, 0.20.2, 0.21.0, 0.21.1, 0.21.2, 0.21.4, 0.21.5, 0.21.6, 0.22.0a0, 0.22.0b0, 0.22.0b1, 0.22.0b2, 0.22.0b3, 0.22.0b4, 0.22.0b5, 0.22.0b6, 0.22.0, 0.22.1, 0.22.2, 0.22.3, 0.22.4, 0.22.5, 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.5, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.2.0, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 2.0.0rc1, 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6.post1, 2.0.7, 2.1.0, 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5, 2.3.0a4, 2.3.0, 2.3.1, 2.3.2b2)
ERROR: No matching distribution found for aiohttp<4,>=3.0.1 (from mautrix-telegram[all])Is rh-python36 installed?
yum -y install rh-python36
You may need to remove /opt/mautrix-telegram and go through the whole mautrix-telegram install process again as it may have created a wrong python environment.
Hello @mrmarkuz How’s the going.
Did you figure out, how to use an owned jitsi meet server instead of the default one in the software that takes users to jitsi on riot server?
The other bridges, like discord.
i noticed that the integrated video and voice call works, but there is no video or audio on the other end… not sure where the problem is, it’s a similar problem i incur with my locally configured turn server also on nextcloud.
No, sorry. I’ll post when I have something.
Jitsi meet should be easily installable on ubuntu so it’s just about making the bridge work.
1 Like
Thanks for your help!
Yes rh-python36 is installed.
I have restarted this installation. I found this little error:
It’s not:
app_service_config_files:
- "/opt/synapse-telegram/registration.yaml"
but it’s:
- "/opt/mautrix-telegram/registration.yaml"
And now I’m blocked with this error :
(mautrix-telegram) [root@matrix mautrix-telegram]# python -m mautrix_telegram
[2020-04-16 18:01:58,292] [DEBUG@mau.init] Initializing mautrix-telegram 0.7.2
[2020-04-16 18:01:58,651] [CRITICAL@mau.init] alembic_version table not found. Did you forget to `alembic upgrade head`?
1 Like
Thanks for testing, I corrected it.
Sorry, I missed step 7 in the howto:
Create the database with
alembic upgrade head. If you have a custom config path, usealembic -x config=/path/to/config.yaml upgrade head
1 Like
You’re welcome!
Many thanks, it works! 
Perhaps you could add it in the howto too…
And now I have to learn how it works… 
1 Like
Done.
i am getting this error below
mautrix-telegram) [root@auth mautrix-telegram]# python -m mautrix_telegram -g
[2020-04-16 21:39:24,287] [CRITICAL@mau.init] Configuration error: bridge.permissions not configuredI assume in the config.yaml you need to configure the following:
permissions:
"*": "relaybot"
"public.example.com": "user"
"example.com": "full"
"@admin:example.com": "admin"
so what details does one put there?
This is what I have but I think it’s well documented:
# Permissions for using the bridge.
# Permitted values:
# relaybot - Only use the bridge via the relaybot, no access to commands.
# user - Relaybot level + access to commands to create bridges.
# puppeting - User level + logging in with a Telegram account.
# full - Full access to use the bridge, i.e. previous levels + Matrix login.
# admin - Full access to use the bridge and some extra administration commands.
# Permitted keys:
# * - All Matrix users
# domain - All users on that homeserver
# mxid - Specific user
permissions:
'*': relaybot
mydomain.tld: full
'@admin:mydomain.tld': admin
'@admin1:mydomain.tld': admin
DId anyone manage to get the built it call function to work after integrating their TUR and STUN
@mrmarkuz do you know where we can define a custom jitsi server on this riot we installed.
The riot nextcloud app has the menu and it works, but on my direct install, i am not sure how to do it.
I assume the jitsi bridge is needed:
How close are you guys to a module/package for NS 7?
Sorry, not really close yet, it’s still on the todo list.
2 Likes
Its currently called element the name riot was replaced and other components.
@mrmarkuz How is the update process to the new version, it seems to have some improvements
Sorry, lack of time, other projects.
Would you like to test the update and probably update the howto?