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
C

carlos

@carlos
About
Posts
3
Topics
1
Shares
0
Groups
0
Followers
0
Following
1

Posts

Recent Best Controversial

  • Consider packaging v10.1.1 pre-release due to bug
    C carlos

    I have built a custom image based on the repo for the mysql version, which we're still using, but I think the issue exists in the postgres version as well.

    I've successfully updated my instance to it by running cloudron build && cloudron update --app 966c02cf-fa46-4eec-ab1f-abb35c60e093.

    My diff is below:

    diff --git a/CHANGELOG.md b/CHANGELOG.md
    index 67b07f7..924863d 100644
    --- a/CHANGELOG.md
    +++ b/CHANGELOG.md
    @@ -777,4 +777,8 @@
     * Update Mattermost to 10.0.0
     * [Full changelog](https://github.com/mattermost/mattermost-server/releases/tag/v10.0.0)
     
    +[2.4.1-rc0]
     
    +* Update Mattermost to 10.1.1
    +* Fixes [GH issue #28344](https://github.com/mattermost/mattermost/issues/28344)
    +* [Full changelog](https://github.com/mattermost/mattermost-server/releases/tag/v10.1.1)
    diff --git a/CloudronManifest.json b/CloudronManifest.json
    index c928002..e3d1d15 100644
    --- a/CloudronManifest.json
    +++ b/CloudronManifest.json
    @@ -4,8 +4,8 @@
       "author": "Mattermost Team",
       "description": "file://DESCRIPTION.md",
       "tagline": "Slack alternative",
    -  "version": "2.4.0",
    -  "upstreamVersion": "10.0.0",
    +  "version": "2.4.1-rc0",
    +  "upstreamVersion": "10.1.1",
       "healthCheckPath": "/",
       "httpPort": 8065,
       "addons": {
    diff --git a/Dockerfile b/Dockerfile
    index 3bc42d7..06f88fa 100644
    --- a/Dockerfile
    +++ b/Dockerfile
    @@ -6,7 +6,7 @@ WORKDIR /app/code
     RUN apt-get update && apt-get install -y pgloader poppler-utils wv unrtf tidy && rm -rf /var/cache/apt /var/lib/apt/lists
     
     # renovate: datasource=github-releases depName=mattermost/mattermost versioning=semver extractVersion=^v(?<version>.+)$
    -ARG MM_VERSION=10.0.0
    +ARG MM_VERSION=10.1.1
     
     # https://docs.mattermost.com/upgrade/upgrading-mattermost-server.html#upgrading-team-edition-to-enterprise-edition
     # in mm 10, despite --config, we have to create the config.json symlink
    

    If someone can let me know how I can go back to the app store provided packages once there is one which fixes the issue, that would be appreciated 😅

    Mattermost

  • Consider packaging v10.1.1 pre-release due to bug
    C carlos

    Hello,

    Since the recent update of org.mattermost.cloudronapp to 2.4.0 (= Mattermost v10.0.0) our users have been unable to change their statuses. Upon taking a look at the logs, I've come across API calls such as GetUsersByGroupChannelIds, UpdateUser failing with the same error as the one below:

    {
      "timestamp": "2024-10-07 08:02:24.115 Z",
      "level": "error",
      "msg": "We encountered an error finding the account.",
      "caller": "web/context.go:124",
      "path": "/api/v4/users/me/patch",
      "request_id": "**************************",
      "ip_addr": "192.0.2.222",
      "user_id": "***************************",
      "method": "PUT",
      "err_where": "UpdateUser",
      "http_code": 500,
      "error": "UpdateUser: We encountered an error finding the account., failed to get User with userId=fgp3pubedi8umdyckiwtgdcm6h: missing destination name MfaUsedTimestamps in *model.User"
    }
    

    Upon further investigation I saw that it has already been reported on the Mattermost issue tracker, with an user claiming that the version above fixes the problem.

    Would it be possible to make that version available on Cloudron already?

    Tagging @joseph @girish for extra visibility, since it's a pressing issue for us.

    Thanks in advance!

    Mattermost

  • Consider packaging v10.1.1 pre-release due to bug
    C carlos

    @nebulon Just popping back here to say this worked a charm, thanks!

    Mattermost
  • Login

  • Don't have an account? Register

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