https://git.cloudron.io/packages/synapse-app/-/merge_requests/23

@jdaviescoates I installed Element X the moment I heard about it. It logged in fine and ran both apps on my phone for a while. @BrutalBirdie I think that's the root of my issues now that you mention it. I migrated my Synapse to another Cloudron a while back, app only and not the CR users. Luckily, I just had to reset the password to get it working again, but things definitely aren't wired right in the backend. I have too many work related room that I don't want to lose, hence the procrastination of setting up a new Synapse.

@nichu42 OK thanks I have to read through the whole documentation then to try this out

@nebulon not sure. Maybe I accidentally removed it when I set up Prometheus

Negative. Please, disregard what have been said earlier: OpenID from Cloudron could be used as is. Happy to share my findings on setting up the service with @vladimir.d or whoever will be doing this configuration for everyone on Cloudron.

I've deleted everything due to me making an error - use the base domain for checking, not matrix.basedoman.com.

Sorry, this is a native Ubuntu install. I suppose this is the wrong venue. Thanks for the heads up.

You can see it here - https://git.cloudron.io/apps/synapse-app/-/merge_requests/10 . The tests are failing, we have to investigate. The update won't work with Element X though, I am pretty sure

@nebulon Correct, but I just realised that in copying and pasting I appear to have missed something. That's embarassing. In any case it has now worked and this is resolved. Thanks for the quick reply.

@girish all sounds very promising indeed. I just went to see if I can now connect to my Cloudron Matrix using Element X... the QR Code login thing at least doesn't seem to have been implemented on Cloudron yet: [image: 1730726405515-b6462474-d41a-457f-97d6-545ddad657f8-image-resized.png] And trying to login in manually doesn't seem to work yet either: [image: 1730726733558-screenshot_20241104-132148_element-x.png] Hopefully in the coming months such things will begin to work? Do we know what we're waiting for? I guess maybe for 2.0 to actually release and packaged?

Hello, it seems there is a loop with SSO Login. It´s jumped back to ..#Login after Authentifcation.

thanks @joseph, for any mods, feel free to remote this thread.

@andreasdueren yes exactly, that's the bug. They are yet to add OIDC support in the Element X apps . the one you linked is the iOS app, the one I linked earlier was for the android app.

@nebulon Thanks! Got it working finally

Just uploaded and extracted latest version but it's just loading, don't see any login screen

@gargamel8 ok, there are some suggested solutions at https://docs.cloudron.io/troubleshooting/#hairpin-nat . Maybe something works for you.

This is very interesting @jdaviescoates thank you for this. I'll examinate this more deeply !

@girish Thanks for the tip, I have entered pfSense as DNS, now it works again. At the end of last week I set up a test server to play with which is connected to a different firewall. I had exactly the same problem with this fresh installation. Another problem with the new login procedure is that mobile devices with the policy of not allowing cookies can no longer log in to the Element app. An alternative solution must now be found, possibly deactivating openID if this is possible, but that is another topic. Many thanks for your help and have a good week! For all those who need a short summary: Log in via SSH Create the file "custom.conf": sudo touch /etc/unbound/unbound.conf.d/custom.conf Edit file: sudo nano /etc/unbound/unbound.conf.d/custom.conf Insert content into the file: # this disables DNSSEC server: val-permissive-mode: yes # forward all queries to the internal DNS forward-zone: name: "." forward-addr: 172.xxx.xxx.xxx Restart: sudo systemctl restart unbound Check: sudo systemctl status unbound

So for two days, it looks like everything's fine. I think I can close this thread.