Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Matrix (Synapse/Element)
  3. stuck on sign in for new account

stuck on sign in for new account

Scheduled Pinned Locked Moved Solved Matrix (Synapse/Element)
13 Posts 4 Posters 3.1k Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • BrutalBirdieB BrutalBirdie

    There is one 404 error when opening element for me and the same error.

    Aug 02 22:54:24 [2021-08-02T20:54:24.897Z] "GET /config.element.deadsec.net.json?cachebuster=1627937670348" Error (404): "Not found"
    

    ca704ce0-fff9-41ad-9bf7-66bc16d60bdd-image.png

    But this seems not be an Element Issue but more a Matrix Home Server issue, since I can login with my @brutalbirdie:matrix.org username.

    86f5b269-4f17-4359-a553-45da2f38df15-image.png

    If I give Element the explicit login this error appears.

    And the federation check seems also OK.

    https://federationtester.matrix.org/#deadsec.net

    eda6983a-bacf-43a1-8eaa-8cf447866973-image.png


    restarting both did also not help.

    Hmmmm

    BrutalBirdieB Offline
    BrutalBirdieB Offline
    BrutalBirdie
    Partner
    wrote on last edited by
    #3

    OK so this should be a Matrix Home Server Problem.
    Since even when using https://app.element.io/#/login with the explicit login it also throws the error.

    d5de247e-14b5-4351-8209-04996fbc3f31-image.png


    I even restored the app to version 1.27.1 and the issue persists. What is going on here?
    Well I changed my DNS to Cloudflare and have the subdomains proxied. Maybe there is something about that.

    Like my work? Consider donating a drink. Cheers!

    ianhyzyI 1 Reply Last reply
    1
    • BrutalBirdieB BrutalBirdie

      OK so this should be a Matrix Home Server Problem.
      Since even when using https://app.element.io/#/login with the explicit login it also throws the error.

      d5de247e-14b5-4351-8209-04996fbc3f31-image.png


      I even restored the app to version 1.27.1 and the issue persists. What is going on here?
      Well I changed my DNS to Cloudflare and have the subdomains proxied. Maybe there is something about that.

      ianhyzyI Offline
      ianhyzyI Offline
      ianhyzy
      wrote on last edited by
      #4

      @brutalbirdie said in stuck on sign in for new account:

      Well I changed my DNS to Cloudflare and have the subdomains proxied. Maybe there is something about that.

      I'm using Gandi DNS so it doesn't seem limited to cloudflare, but I'm trying to dig into the homeserver now

      BrutalBirdieB 1 Reply Last reply
      1
      • ianhyzyI ianhyzy

        @brutalbirdie said in stuck on sign in for new account:

        Well I changed my DNS to Cloudflare and have the subdomains proxied. Maybe there is something about that.

        I'm using Gandi DNS so it doesn't seem limited to cloudflare, but I'm trying to dig into the homeserver now

        BrutalBirdieB Offline
        BrutalBirdieB Offline
        BrutalBirdie
        Partner
        wrote on last edited by BrutalBirdie
        #5

        @ianhyzy questionable since I even restored the version before and the issue is the same. Time for a Cloudron reboot 😉
        Have to do that anyway.


        Edit nope issue persists.

        Like my work? Consider donating a drink. Cheers!

        1 Reply Last reply
        1
        • humptydumptyH Offline
          humptydumptyH Offline
          humptydumpty
          wrote on last edited by
          #6

          Element/Matrix are working fine on my server. I can sign in with the iOS mobile app, on Element (self-hosted on CR) and on Element (app.element.io) by editing the homeserver and using mine. All's good.

          Cloudron app details:
          Matrix: org.matrix.synapse@1.28.0
          Element: im.riot.cloudronapp@1.5.14
          Cloudron: v6.3.5 (Ubuntu 20.04.2 LTS)

          I'm not running a proxy or cloudflare.. maybe that's the issue? lmk if you need me to test anything on my end.

          ianhyzyI 1 Reply Last reply
          0
          • humptydumptyH humptydumpty

            Element/Matrix are working fine on my server. I can sign in with the iOS mobile app, on Element (self-hosted on CR) and on Element (app.element.io) by editing the homeserver and using mine. All's good.

            Cloudron app details:
            Matrix: org.matrix.synapse@1.28.0
            Element: im.riot.cloudronapp@1.5.14
            Cloudron: v6.3.5 (Ubuntu 20.04.2 LTS)

            I'm not running a proxy or cloudflare.. maybe that's the issue? lmk if you need me to test anything on my end.

            ianhyzyI Offline
            ianhyzyI Offline
            ianhyzy
            wrote on last edited by
            #7
            This post is deleted!
            1 Reply Last reply
            0
            • ianhyzyI Offline
              ianhyzyI Offline
              ianhyzy
              wrote on last edited by ianhyzy
              #8

              I have my desktop app open and I can still send messages, but no dice on login - extremely weird. Nothing in logs at all other than that cachebuster error.

              also turned on debug mode but it doesn't seem to be showing me anything more.

              loggers:
                synapse.storage.SQL:
                  # beware: increasing this to DEBUG will make synapse log sensitive
                  # information such as access tokens.
                  level: DEBUG
                twisted:
                  # We send the twisted logging directly to the file handler,
                  # to work around https://github.com/matrix-org/synapse/issues/3471
                  # when using "buffer" logger. Use "console" to log to stderr instead.
                  handlers: [file]
                  propagate: false
              root:
                level: DEBUG
                # Write logs to the `buffer` handler, which will buffer them together in memory,
                # then write them to a file.
                #
                # Replace "buffer" with "console" to log to stderr instead. (Note that you'll
                # also need to update the configuration for the `twisted` logger above, in
                # this case.)
                #
                handlers: [buffer]
              disable_existing_loggers: false
              
              girishG 1 Reply Last reply
              0
              • ianhyzyI ianhyzy

                I have my desktop app open and I can still send messages, but no dice on login - extremely weird. Nothing in logs at all other than that cachebuster error.

                also turned on debug mode but it doesn't seem to be showing me anything more.

                loggers:
                  synapse.storage.SQL:
                    # beware: increasing this to DEBUG will make synapse log sensitive
                    # information such as access tokens.
                    level: DEBUG
                  twisted:
                    # We send the twisted logging directly to the file handler,
                    # to work around https://github.com/matrix-org/synapse/issues/3471
                    # when using "buffer" logger. Use "console" to log to stderr instead.
                    handlers: [file]
                    propagate: false
                root:
                  level: DEBUG
                  # Write logs to the `buffer` handler, which will buffer them together in memory,
                  # then write them to a file.
                  #
                  # Replace "buffer" with "console" to log to stderr instead. (Note that you'll
                  # also need to update the configuration for the `twisted` logger above, in
                  # this case.)
                  #
                  handlers: [buffer]
                disable_existing_loggers: false
                
                girishG Offline
                girishG Offline
                girish
                Staff
                wrote on last edited by
                #9

                @ianhyzy Did you install synapse with Cloudron user integration disabled? Earlier I had reported an issue along these lines at https://github.com/matrix-org/matrix-synapse-ldap3/issues/124 . If you installed Synapse with Cloudron user integration disabled, then can you check homeserver.yml and ensure that it does not have the Ldap configuration ? If there is some ldap configuration just remove it entirely and restart synapse. Note that there is a "disabled" flag but that does nothing (I reported that as https://github.com/matrix-org/matrix-synapse-ldap3/issues/123)

                ianhyzyI 1 Reply Last reply
                1
                • girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by
                  #10

                  I thought I automatically deleted the password_providers section when user management is disabled with https://git.cloudron.io/cloudron/synapse-app/-/commit/6775418dafd900ddd5dd7ce9201014f227571de7 but maybe I got something wrong.

                  1 Reply Last reply
                  0
                  • girishG girish

                    @ianhyzy Did you install synapse with Cloudron user integration disabled? Earlier I had reported an issue along these lines at https://github.com/matrix-org/matrix-synapse-ldap3/issues/124 . If you installed Synapse with Cloudron user integration disabled, then can you check homeserver.yml and ensure that it does not have the Ldap configuration ? If there is some ldap configuration just remove it entirely and restart synapse. Note that there is a "disabled" flag but that does nothing (I reported that as https://github.com/matrix-org/matrix-synapse-ldap3/issues/123)

                    ianhyzyI Offline
                    ianhyzyI Offline
                    ianhyzy
                    wrote on last edited by
                    #11

                    @girish
                    Interesting, yes I did have this:

                    password_providers:
                      - module: "synapse.util.ldap_auth_provider.LdapAuthProvider"
                        config:
                          enabled: true
                          uri: "ldap://ldap.example.com:389"
                          start_tls: true
                          base: "ou=users,dc=example,dc=com"
                          attributes:
                            uid: "username"
                            mail: "mail"
                            name: "username"
                          bind_dn: "ou=users,dc=cloudron"
                          bind_password: "password"
                          filter: "(objectClass=posixAccount)"
                    

                    so i deleted it and boom, working again! Cloudron support remains unmatched in speed and ticket resolution time 🤗

                    girishG 1 Reply Last reply
                    0
                    • ianhyzyI ianhyzy

                      @girish
                      Interesting, yes I did have this:

                      password_providers:
                        - module: "synapse.util.ldap_auth_provider.LdapAuthProvider"
                          config:
                            enabled: true
                            uri: "ldap://ldap.example.com:389"
                            start_tls: true
                            base: "ou=users,dc=example,dc=com"
                            attributes:
                              uid: "username"
                              mail: "mail"
                              name: "username"
                            bind_dn: "ou=users,dc=cloudron"
                            bind_password: "password"
                            filter: "(objectClass=posixAccount)"
                      

                      so i deleted it and boom, working again! Cloudron support remains unmatched in speed and ticket resolution time 🤗

                      girishG Offline
                      girishG Offline
                      girish
                      Staff
                      wrote on last edited by
                      #12

                      @ianhyzy oh 🤦 I made a mistake in the script.

                      1 Reply Last reply
                      0
                      • girishG Offline
                        girishG Offline
                        girish
                        Staff
                        wrote on last edited by
                        #13

                        I fixed this in package 1.28.0-1

                        1 Reply Last reply
                        3
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        • Login

                        • Don't have an account? Register

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Bookmarks
                        • Search