Skip to main content

Blog

Disclaimer!
Here you will get a little insight into the life of a Matrix administrator. I'll try to describe my impressions to you as best as possible. Don't let this stop you from building your own Matrix server. Basically, it's a lot of fun to explore the peculiarities and deal with problems. If you also decide to run a public server, the learning effect is even greater. :-)

2024-04-01 Happy easter!

Happy Easter to all of you, have a good time with your loved ones!

Some time has passed since the last update. Unfortunately I didn't have much time to feed the blog. But here are a few changes.

Frei.chat switched to KeydB with the last updates from Redis, which has provided a good speed gain. With normal use, the effects are only minimally noticeable, since this benefits more to internal worker processes.

In addition, there has been a problem with telephony and video calls for some time. These were no longer possible through element. I did a configuration adjustment today. So calls should be possible again.

2024-02-18 New Facebook and Instagram bridges

The current Facebook and Instagram bridges can no longer be used due to the meta switch to encrypted chats. The developer of the bridges has therefore started a new project.

With the commissioning of the new bridges, the old bots will no longer be usable. Commands about the management rooms are no longer accepted. Removing the old bots from the management rooms and adding the new bots should be possible. As soon as a new connection has been established with the personal accesses of the Meta-Portal, new rooms should open.

To create a new connection, you can find links to the documentation on the bridge page. Attention, the bots can only be addressed via the prefixes.

2024-02-13 New Element v0.11.58 with RUST-SDK

The Element team has just released the new version 0.11.58 which contains the new RUST-SDK cryptographic implementation. The team recommends a relog of all of your Element sessions including mobile clients. Only after that the new implementation will be used.

2024-02-08 Double-puppeting bridges

The double-puppeting function allows the bridge bots to create new chats from WhatsApp, Telegram and co. to accept automatically. Typically, a Matrix user must accept chat invitations manually.

In case a user sent the logout-matrix command to one of the bots, double-puppeting is disabled for that user. To reactivate this function, a login-matrix TOKEN is required. The personal token of a permanently valid session must be used for this. This session must never be deactivated so that double-puppeting remains functional.

How do I get a persistent token and enable double-puppeting again?

Only do this if you accidentally sent a logout-matrix to the Bridge bot!

  1. In your favorite browser, open a private window
  2. Now go to https://element.frei.chat and log in with your user and password. Then enter your security key.
  3. In the Settings go to the “Help & About” menu and expand “Access Token”. Copy the value shown there.
    Warning: Do not show this value to anyone, as it grants full access to your account!

    grafik.png

  4. Now go to the Bridge bot chat and run the command login-matrix TOKEN (replace TOKEN with the copied value!)

2024-02-06 Docker Security Advisory

The latest Docker news reports security vulnerabilities. Therefore, today there was a short restart of the server with the latest Docker Engine version.
Source: https://www.docker.com/blog/docker-security-advisory-multiple-vulnerabilities-in-runc-buildkit-and-moby/

2024-01-29 Registration issue when using Element

For some days now frei.chat has suffered from a registration issue when using Element chat. An error message was showing up when clicking on the registration button. 
Some user from the Docker Matrix-channel found a solution which I could adapt to frei.chat config. After a quick reboot of the services registration is working fine again.

For anyone who is having the same issue you will have to add the following lines to your vars.yml file.

matrix_ma1sd_configuration_extension_yaml: |
  register:
    policy:
      allowed: true
      threepid:
        email:
          domain:
            blacklist: ~
            whitelist: ~


2024-01-28 Development on Facebook and Instagram bridges / Replacement in sight?

With the announcement I would like to inform you that development on the Facebook and Instagram bridges will soon be discontinued and frei.chat will move to the new development strand as soon as it is available in the playbook.
Currently it looks like existing connections to your accounts will be terminated and you will have to reconnect manually.
You will receive further information as soon as the change takes place.

2024-01-21 NTFY issue

For some time now, the NTFY service on frei.chat has not been able to send notifications. I have not yet been able to resolve the following error message because the DNS resolution for ntfy.frei.chat in the local Matrix network always worked. Today I came across a Github post (Thanks to ToeiRei) that provides a solution to this problem.
Synapse uses a blacklist and excludes local IP address networks. With the frei.chat setup, this prevents Synapse from communicating with NTFY, as this occurs via the public FQDN (ntfy.frei.chat) and not via the internal address. Since ntfy.frei.chat resolves to a local IP in this internal network, it is ignored.

matrix-synapse: synapse.push.httppusher - 415 - WARNING - httppush.process-13060 - Failed to push data to
  @USERNAME:frei.chat/im.vector.app.android/https://ntfy.frei.chat/UNIQUE_IDENTIFIER?up=1: 
  <class 'twisted.internet.error.DNSLookupError'> DNS lookup failed: no results for hostname lookup: ntfy.frei.chat.

The solution is to enter the IP of the internal proxy, in this case an upstream nginx service, in Synapse.

matrix_synapse_configuration_extension_yaml: |
  ip_range_whitelist:
    - 'local_ip_of_nginx_proxy'

2024-01-20 New worker setup / registration issue

Charles Wright from FUTO has been working on a specialized worker setup for more efficiant workload. Frei.chat is running that new setup from today on. Read more.

Unfortunately, the frei.chat Element client is having an issue with the registration process. After successfully finishing the recaptcha authorization the loading circle will not stop spinning and doesn't bring you to the next dialog to complete the registration process. So I changed the documentation for registering new users with the Schildichat app, which surprisingly doesn't seem to have this issue.

2024-01-19 Workers up again

The workers problem has been solved and they are up again. Maybe you have experienced slow message / media transfer to external servers, if not I'm happy it went all good over the last days. Especially mobile apps have sufferd from that single worker setup with log loading screens (> 2 or 3 seconds).

Now with workers there shouldn't have any of these bad latence and messages / media should arrive much faster. The mobile apps should also sync faster when you open the app after a longer time.

2024-01-16 Troublesome day

Today I decided to update to the new Traefik configuration. Unfortunately, this proved to be a major problem.
The configuration in the playbook is still quite young, but since I had good results on my test instance, I took the step. Unfortunately, I discovered that the frei.chat setup is currently not compatible with the configuration.
The problem was the current worker configuration, which splits up certain background processes and is supposed to provide better performance. Unfortunately, Traefik doesn't seem to be configured correctly for the workers to function correctly. Unfortunately there were a few restarts today because the error was difficult to reproduce.
After a few hours of troubleshooting, a delicious, energizing tiramisu and two hours of sleep, I tried it again and was able to narrow down the source of the error to the workers. The setup will now run again on the non-worker setting until the problem with the workers has been resolved.
Please excuse the many restarts.

I also decided to limit the retention time to 7 days for local and remote media. But uploads of up to 250MB in size are now possible. Profile pictures are not affected.

There are no updates... Had a configuration issue which went online. There is no change but you still have to consent again. Sorry!

Additionally I've added history information to the Privacy Policy and Terms of Use pages. No other changes were made to the pages at all!

Update 17:30 Uhr

The developer of the playbook changed some variable names which manage the port definition for internal services. Had to deploy twice to find the correct combination. Therefore frei.chat was unavailable a bit longer than usual during restart

2024-01-09 New website logo, First steps and updated pages

Todays announcement is about presenting the new frei.chat logo and informing about a fresh update of most of the pages, like Bots, Bridges and Services.

If you would like to link frei.chat on your website, you can of course use the logo in conjunction with.

frei.chat now has a new public space for RSS feeds. Each room is assigned a feed and updates once an hour.

The Postmoogle bot allows every user to receive and send emails via frei.chat. The Bots page describes what you need to do for your personal email address.

I have created a "First steps" guide on how to start on frei.chat for new users.

2024-01-06 Revision of the website

I've been working on redesigning the frei.chat website for a few hours now. I switched from the mkdocs for materials software to Bookstack, which makes working on the individual pages much easier.
In addition to updates to the Bridges, Bots and Services pages, illustrated instructions for the first steps to your own frei.chat account have now been added.
In addition, you now have a clear overview of the changes to the frei.chat server on the announcements page.

2024-01-05 Update of the Signal bridge bot

Singal

If you want to have all Signal chats in you very own Signal space you have to run the command !signal sync-spaces in you personal Singal management room.

Maubot

The new maubot can be invited in every unencrypted room. It response to many commands and mostly used for fun actions.

2024-01-04 New Signal bridge bot

The new Signal bridge was installed on top of the existing installation. All devices which have been connected before the 3rd of January 2024 needs to be re-linked manually. Every command has to start with the prefix !signal so talk to the bridge bot.

In case you have problems with the Signal bot please kick the user @signalbot:frei.chat out of the management room, leave that room, create a new unencrypted room and invite the bot again.

Back to top