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


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    error when editing channel and team

    Rocket.Chat
    2
    4
    216
    Loading More Posts
    • 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.
    • B
      blaise last edited by

      I have two frustrated issue

      1- when i want to edit a team or a chanel , i got this message error
      No channel with name "publicteam" was found!
      Room not found
      it did the same thing for any channel or team i want to edit

      2- i also got this error message: You found a Cloudron out in the wild! its happen when i click the invote link generate to invite someone in a team

      someone can help to correct those two issues?
      Thank

      1 Reply Last reply Reply Quote 0
      • nebulon
        nebulon Staff last edited by

        Do you see any errors in the app logs or browser console during the rename?

        I just tried to rename a channel on latest package and it works, however, if I also had that channel currently open, then I see some error "No private group with name ... was found"
        This however is then gone in my case, if I just switch to the channel again based on the new name.

        B 1 Reply Last reply Reply Quote 0
        • B
          blaise @nebulon last edited by

          @nebulon not the rename, when i turn the channel from private to public or something else..... it give that same message. even its modfy sucessfull the setting...

          nebulon 1 Reply Last reply Reply Quote 0
          • nebulon
            nebulon Staff @blaise last edited by

            @blaise ah ok, but yes I can see the same error message as such, but after revisiting the channel it seems to work fine. If that is what you mean, then this is very much an upstream bug.

            I did a quick search in their issue tracker, but couldn't find anything specific yet.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Powered by NodeBB