After upgrading rocketchat to v1.0.0, it's not starting with TypeError: Cannot read property '0' of undefined error.
I've tried both: manual installation and official docker image:
docker run -e ROOT_URL=http://rocketchat.example.org/ -e MONGO_URL=mongodb://rocketchat:thupho6lah9foamiShai@rocketchat-db:27017/rocketchat -e MONGO_OPLOG_URL='mongodb://rocketchat:thupho6lah9foamiShai@rocketchat-db:27017/local?replicaSet=rs0&authSource=admin' -e PORT=3000 -e BIND_IP=127.0.0.1 -ti --net=host -v /tmp/:/tmp rocketchat/rocket.chat:1.0.0
/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:218
throw error;
^
TypeError: Cannot read property '0' of undefined
at retrieveRegistrationStatus (app/cloud/server/functions/retrieveRegistrationStatus.js:15:28)
at getWorkspaceAccessToken (app/cloud/server/functions/getWorkspaceAccessToken.js:11:50)
at index.js (app/cloud/server/index.js:13:1)
at fileEvaluate (packages/modules-runtime.js:336:7)
at Module.require (packages/modules-runtime.js:238:14)
at Module.moduleLink [as link] (/app/bundle/programs/server/npm/node_modules/meteor/modules/node_modules/reify/lib/runtime/index.js:38:38)
at rest.js (app/apps/server/communication/rest.js:1:344)
at fileEvaluate (packages/modules-runtime.js:336:7)
at Module.require (packages/modules-runtime.js:238:14)
at Module.moduleLink [as link] (/app/bundle/programs/server/npm/node_modules/meteor/modules/node_modules/reify/lib/runtime/index.js:38:38)
at index.js (app/apps/server/communication/index.js:1:271)
at fileEvaluate (packages/modules-runtime.js:336:7)
at Module.require (packages/modules-runtime.js:238:14)
at Module.moduleLink [as link] (/app/bundle/programs/server/npm/node_modules/meteor/modules/node_modules/reify/lib/runtime/index.js:38:38)
at orchestrator.js (app/apps/server/orchestrator.js:1:534)
at fileEvaluate (packages/modules-runtime.js:336:7)
see #14231
@hypery2k 14231 is a closed issue, and I just had this very same issue. It's not resolved yet
Most helpful comment
@hypery2k 14231 is a closed issue, and I just had this very same issue. It's not resolved yet