Infinite loop on home screen [resolved]

Community Support
1

Description

I’m running Rocket chat and MongoDB using docker.
When opening the URL of my domain I find the RocketChat default configuration screen

However, after informing my data, I receive the activation email and when I click on the link, I receive a blank screen of the address.
https://cloud.rocket.chat/verify-workspace/

After several attempts I noticed that the WorkSpaces tab doesn’t have any self-hosted domains showing up.

And every time I enter my site I get looped through the configuration screen.

Server Setup Information

  • Version of Rocket.Chat Server: 5.1.2
  • Operating System: CentOS7 CyberPanel
  • Deployment Method:
  • Number of Running Instances: 01
  • DB Replicaset Oplog:
  • NodeJS Version:
  • MongoDB Version:
  • Proxy: openlitespeed
  • Firewalls involved: No

Any additional Information

My compose.yml

volumes:
  mongodb_data: { driver: local }

services:
  rocketchat:
    image: registry.rocket.chat/rocketchat/rocket.chat:${RELEASE:-5.1.2}
    restart: on-failure
    labels:
      traefik.enable: "true"
      traefik.http.routers.rocketchat.rule: Host(`${DOMAIN}`)
      traefik.http.routers.rocketchat.tls: "true"
      traefik.http.routers.rocketchat.entrypoints: https
      traefik.http.routers.rocketchat.tls.certresolver: le
    environment:
      MONGO_URL: "${MONGO_URL:-\
        mongodb://${MONGODB_ADVERTISED_HOSTNAME:-mongodb}:${MONGODB_INITIAL_PRIMARY_PORT_NUMBER:-27017}/\
        ${MONGODB_DATABASE:-rocketchat}?replicaSet=${MONGODB_REPLICA_SET_NAME:-rs0}}"
      MONGO_OPLOG_URL: "${MONGO_OPLOG_URL:\
        -mongodb://${MONGODB_ADVERTISED_HOSTNAME:-mongodb}:${MONGODB_INITIAL_PRIMARY_PORT_NUMBER:-27017}/\
        local?replicaSet=${MONGODB_REPLICA_SET_NAME:-rs0}}"
      ROOT_URL: ${ROOT_URL:-https://chat.mysite.com.br:${HOST_PORT:-3008}}
      PORT: ${PORT:-3008}
      DEPLOY_METHOD: docker
      DEPLOY_PLATFORM: ${DEPLOY_PLATFORM}
    depends_on:
      - mongodb
    expose:
      - ${PORT:-3008}
    ports:
      - "${BIND_IP:-0.0.0.0}:${HOST_PORT:-3008}:${PORT:-3008}"

  mongodb:
    image: docker.io/bitnami/mongodb:${MONGODB_VERSION:-4.4}
    restart: on-failure
    volumes:
      - mongodb_data:/bitnami/mongodb
    environment:
      MONGODB_REPLICA_SET_MODE: primary
      MONGODB_REPLICA_SET_NAME: ${MONGODB_REPLICA_SET_NAME:-rs0}
      MONGODB_PORT_NUMBER: ${MONGODB_PORT_NUMBER:-27017}
      MONGODB_INITIAL_PRIMARY_HOST: ${MONGODB_INITIAL_PRIMARY_HOST:-mongodb}
      MONGODB_INITIAL_PRIMARY_PORT_NUMBER: ${MONGODB_INITIAL_PRIMARY_PORT_NUMBER:-27017}
      MONGODB_ADVERTISED_HOSTNAME: ${MONGODB_ADVERTISED_HOSTNAME:-mongodb}
      MONGODB_ENABLE_JOURNAL: ${MONGODB_ENABLE_JOURNAL:-true}
      ALLOW_EMPTY_PASSWORD: ${ALLOW_EMPTY_PASSWORD:-yes}
2

Hi @eu_andrealmeida !

Welcome to our community :slight_smile:

I have seen other users with this exact issue and already warned our cloud team to take a look on this.

I also assisted a user, and we got around it by:

  • Choose to not register at the Setup Wizard (go standalone)
  • Log in your cloud account
  • Generate and copy a token
  • Paste it under Admin > Connectivity Services

It took us 4 attempts before it succeeded :grimacing:

Sorry for the inconvenience. We should fix this soon.

Let me know if this helps. Thanks!

3

Also, in order to avoid the Setup Wizard altogether (if you get caught on a Wizard Loop)
you can add

OVERWRITE_SETTING_Setup_Wizard: completed

to the environment variables of your docker compose.yml