Turn domain Matrix-Synapse not changing after moving to another my.domain

[DanTheMan]

Hi there,

I recently moved the Cloudrons my.domain (Dashboard) to another domain of mine.
Now after a while i could not connect new calls through Matrix-Synapse so i checked the Turn settings in the config (homeserver.yaml).

I discovered that it was still pointing to the old my.domain address so i changed it to the new one, but after rebooting Matrix it came back to the old one......

What to do now.....?

[jdaviescoates]

I'm not sure but perhaps you need to update the well-known location?

https://docs.cloudron.io/domains/#well-known-locations

[DanTheMan]

I have checked that one but I think federation still works. It is only the turn server that points to the old domain and will not change to the new one....

[girish]

@DanTheMan Think this is a bug . We don't seem to update the turn server information when the dashboard domain changes. I will investigate tomorrow and provide a fix/workaround.

[DanTheMan]

Thanks for checking that Girish

[girish]

This is a bug and I can reproduce it. A silly workaround:

• Backup synapse
• Move synapse to another domain. For example, synapse2.domain.com
• Create a clone of the backup to the original domain synapse.domain.com

This should fixup the turn server configuration.

[DanTheMan]

Thanks a lot for that Girish
I will check on it tommorow and report back when successfully accomplished....

[DanTheMan]

@girish
In the meantime I was thinking about the domain change (move) for cloning, like you described.

But doesn't this interfere with the rules that Synapse has/depends on?

I read this (old) article somewhere:

Why can't I rename my homeserver?
Currently, the homeserver name is assumed never to change. This means that if you rename your server, other servers will think it's a different server.

Perhaps in the future we will add an API for changing the homeserver name, but for now this is not supported.

https://matrix.org/docs/older/faq/

It's an old documentation, but I just want to be on the safe side....

[girish]

@DanTheMan we are not changing the matrix location. We are simply restoring from latest backup into same location as before. You can delete the synapse2.domain.com in the steps above. So:

The end goal is here is just restore from latest backup to synapse.domain.com. This fixes up the turn configuration.

• Backup your current synapse located at synapse.domain.com
• Stop the synapse app synapse.domain.com
• Move synapse to another domain. For example, move it to synapse2.domain.com. The reason for this is to free up synapse.domain.com
• Now, create a clone of the backup created in step 1 to synapse.domain.com

If everything is fine, you can just delete the app at synapse2.domain.com .

[DanTheMan]

@girish I'm a little stuck (not sure) with step 3 and maybe 4:

• 3: Move synapse to another domain. For example, move it to synapse2.domain.com. The reason for this is to free up synapse.domain.com

How do we move Synapse exactly? By just going to the location of the existing install and change the synapse.domain.com to synapse2.domain.com?
Or do we have to install a second app with synapse2.domain.com pointed to it?

[girish]

@DanTheMan said in Turn domain Matrix-Synapse not changing after moving to another my.domain:

How do we move Synapse exactly? By just going to the location of the existing install and change the synapse.domain.com to synapse2.domain.com?

yes, exactly. Just go to Location view of the app and change the subdomain to synapse2 - https://docs.cloudron.io/apps/#location

Then, clone is the clone button in the backup section of the synapse2 app - https://docs.cloudron.io/backups/#clone-app

[DanTheMan]

Everything worked out really good and calling through the Elements app is working again.
Thanks for the great and fast support Girish

We can close this one as solved!!

[girish]

@DanTheMan thanks! I am working on fixing the bug in any case.

[DanTheMan]

Great
then we have at least tackled this bug for the upcoming future.