Useful or not, from you.
wekan Wekan doesn't start anymore after trying to upgrade

Wekan doesn't start anymore after trying to upgrade:

					return fn.apply(this, arguments);

Error: Must pass options.rootUrl or set ROOT_URL in the server environment
    at Object.Meteor.absoluteUrl (packages/meteor.js:1378:11)
    at runWebAppServer (packages/webapp/webapp_server.js:771:18)
    at webapp_server.js (packages/webapp/webapp_server.js:1175:1)
    at fileEvaluate (packages/modules-runtime.js:336:7)
    at Module.require (packages/modules-runtime.js:238:14)
    at require (packages/modules-runtime.js:258:21)
    at /build/programs/server/packages/webapp.js:1588:15
    at /build/programs/server/packages/webapp.js:1597:3
    at /build/programs/server/boot.js:419:36
    at Array.forEach (<anonymous>)
    at /build/programs/server/boot.js:228:19
    at /build/programs/server/boot.js:479:5
    at (/build/programs/server/profile.js:510:12)
    at /build/programs/server/boot.js:478:11

Server Setup Information:

  • Did you test in newest Wekan?: yes, and in older Wekans as well, it stays the same error in the logs
  • For new Wekan install, did you configure root-url correctly: ? yes, it worked till today
  • Wekan version: now
  • If this is about old version of Wekan, what upgrade problem you have?:
  • Operating System: 3.36
  • Deployment Method(snap/docker/sandstorm/mongodb bundle/source): docker
  • Http frontend if any (Caddy, Nginx, Apache, see config examples from Wekan GitHub wiki first): nginx
  • Node Version: ?
  • MongoDB Version: 4.0.11
  • ROOT_URL environment variable http(s)://(subdomain)
  • Wekan only works on newest desktop Firefox/Chromium/Chrome/Edge/Chromium Edge and mobile Chrome. What webbrowser version are you using? ...
That's a useful answer
Without any help

Update: the wekan version 3.37 from docker hub restarts every 5 minutes. Rolled back to 3.35. Will post update

The latest (docker) version (pulled yesterday) crashed repeatedly without an error message for us. Docker logs unfortunately didn't show any errors. The container just goes down and up again for a few seconds. The workaround was pulling v3.37 from wekanteam/wekan and not "latest" I think that must be actually version 3.36 because there is a gap between 3.35 and 3.37. "latest" seems to be different from 3.37 on Dockerhub. Mayhaps something with the latest build on Dockerhub went wrong