Hello everyone!

After much pain and agony I was able to setup my matrix server! Huzzah!

Until I went to sign in with element x :(

It says my server does not have sliding sync support. I have tried looking at the official documentation and trying to getbit working but to no avail. I went thrught the only limited tutorial provided by the actual matrix channel. Still no success.

I was able to install shildichat and that works just fine! Same with the element desktop client.

Do I need to completely restart my matrix installation to get this working? Is there an easy way to get it working now that my mattix-synapse server is already setup?

For context I followed this exact tutorial (though instead of nginx proxy manager I used cloudflare tunnel)

https://www.youtube.com/watch?v=TFDFR6EBG3k

In the video it says nothing about sliding sync but when you go to his wiki site the matrix config has been updated with an empty sliding scale patameter.

Any help would be appreciated!

EDIT:

I am using ubuntu 20.04 deploying my matrix server through docker. I am using the latest build of dendrite matrix-synapse

Dendrite monolith matrix github:

https://github.com/matrix-org/dendrite/blob/main/build/docker/README.md

This is the documentation I followed:

https://wiki.opensourceisawesome.com/books/setup-matrix-chat/page/install-matrix-using-the-dendrite-server

EDIT 2:

please forgive my idiocy. What I wanted was element the app not element x. Unless there is a problem wjth me running matrix without this supposed sliding sync, my issue is solved lol. I will take the advice to implement it if necessary.

  • WIPocket@lemmy.worldEnglish
    8·
    10 days ago

    Sliding sync was recently implemented in Synapse itself, so as long as your Synapse is up to date there shouldnt be any more setup on the matrix side. Try checking the Synapse logs for any issues and/or the cloudflare tunnel configuration (I have no idea about what it does to traffic).

    • ludicolo@lemmy.mlOPEnglish
      2·
      10 days ago

      Well damn. I guess I will check out another method to getting it up and running aooner or later. But for now this will do…

      What is the benefit of sliding sync if you don’t mind me asking? What will I be missing out on?

      • Eskuero@lemmy.fromshado.wsEnglish
        2·
        10 days ago

        It’s supposedly faster/snappier loading on large rooms. But if you are self-hosting a single user instance, you might not notice much improvement.

        I was also running the dendrite but I gave up because it seemed like development was stalled so I moved over to Synapse.

        • WIPocket@lemmy.worldEnglish
          2·
          10 days ago

          I recently migrated from Element to Element X with first the proxy and now simplified sliding sync, and it feels way faster. Imho Element X is still very alpha software, so I wouldnt recommend it to the general population just yet (and I still occasionally have to open the old Element), but the speed is really noticeable on even a very small instance.

  • bmcgonag@lemmy.worldEnglish
    3·
    10 days ago

    Just and FYI those are my pages and Video, and I also don’t have sliding sync working yet. I work on it here and there, but other than Element X, I’ve had no issues getting clients to connect to my servers running dendrite. I’ll update those docs, and probably do an update video when I get it working on Dendrite.

    • ludicolo@lemmy.mlOPEnglish
      1·
      7 days ago

      Wow! Hey thanks for the tutorial! It was beyond helpful! Oh hell yeah can’t wait!

      I do have some questions if you don’t mind me asking

      So I recently used your affliate link for digital ocean and started following your coturn tutorial. I followed everything but my home server can’t seem to connect to it. Anytime I set the turn rules in the dendrite.yaml the server won’t start. I am using cloudflare tunnels for my actual matrix server then I use dns records to set the coturn record. Matrix works fine with turn variables uncommented just with no rtc on out of network. Do I need to forward the digital ocean ports? If so how do I do that and which ports do I forward? How can I get my home server to find my digital ocean server and use coturn?

      EDIT:

      I feel like it has to be something with dns records on cloudflare. I have been using tunnels for a majority of things inclueing matrix without coturn. I have no idea how to fix this portion of setup, any help would be appreciated!

      EDIT 2:

      NVM IT’S BEEN FIXED!!

      I do have a question, did you ever figure out message rention and deletion?

      • bmcgonag@lemmy.worldEnglish
        1·
        7 days ago

        Glad you got Coturn working, what was it?

        Haven’t messed with retention and deletion yet. Not enough data to mess with it so far.

        • ludicolo@lemmy.mlOPEnglish
          1·
          7 days ago

          In cloudflare I had my digital ocean dns record set to proxied when it needed to be “dns only”

          That and I formatted my dendrite.yaml to have more spaces in the turn section than it should have. Now it’s all up and running!

          Oh ok cool! I had just seen another forum where they mentioned it and became concerned.

          Thanks again!