Network Error

[DANW999]

Hi, whenever I launched Revolt using Docker Compose with the exact same template as given here, I am able to get to the login page just fine but whenever I attempt to create an account I get "FAILED TO REGISTER - NETWORK ERROR". I have even when tested filling in the SMTP details in the env file and making sure all my ports are open as part of troubleshooting. What am I doing wrong? Thank you.

[elightcap]

Are you reverse proxying it? I have mine behind caddy and am running into the same issue

[engineeringsys]

@DANW999 Check to make sure you aren't already using any of the ports from revolt in other docker containers on your host. ie if you have Portainer running 8000/9000 may be occupied. You can change them in the docker-compose.yml I just ran into this issue.

[yllekz]

Getting the same thing. Not sure why this error would fire out of the box. All ports are available/separate from Portainer's/etc and no reverse proxy involved.

[elightcap]

Ah. Issue for me was i didnt set a vapid key. revoltchat/server was panicking. After adding that, things to be mostly working as intended.

[yllekz]

I generated new keys but am still getting the network error. None of the containers/logs seem to be throwing errors either, so I'm stumped as to what's going on.

[Jimmy-SafeCash]

I have the same issue when trying to create an account. No errors in logs. (Using Traefik if that's of use).

[DANW999]

@elightcap I am not running behind proxy and @engineeringsys I am not running on used ports (docker would provent me from spinning up the container in the first place otherwise). How would I go about generating keys? As that does not appear to be mentioned the documentation page, unless I missed it. All help is appreciated, thank you.

[engineeringsys]

@Jimmy-SafeCash Can you post your docker-compose.yml with traefik setup?

[engineeringsys]

@DANW999 If you do a quick search there's quite a few utilities online to generate valid Vapid keys. Or in the .env-example file there's a link

[Xynnix]

I’m sure this has been said or done, if not, try checking the browsers web console if you haven’t. if it’s a proxy issue, I made a PR for those who wish to use NGINX as an easier proxy since it would just need editing/adding of nginx.conf and a proxy through cloud-flare for ssl. It will also redirect most to port 80 and for the specified sub/domain. It will keep localhost (127.0.0.1 or whatever) accessible for you on locally.

[insertish]

The default configuration is intended for your local machine only, you have to configure the endpoints for it to work outside of your local machine.

[DANW999]

@Jimmy-SafeCash Can you post your docker-compose.yml with traefik setup?

Hi @Jimmy-SafeCash sorry for the late reply. I have not changed anything from the original file. Here is it:

version: '3.8'

services:

MongoDB database

database: image: mongo restart: always volumes:

• ./data/db:/data/db

  Redis server

  redis: image: eqalpha/keydb restart: always

  REVOLT API server (Delta)

  api: image: revoltchat/server env_file: .env depends_on:

• database
• redis environment:
• REVOLT_MONGO_URI=mongodb://database
• REVOLT_REDIS_URI=redis://redis/ ports:
• "8000:8000"

• "9000:9000" restart: always

  REVOLT Web App

  web: image: revoltchat/client:master env_file: .env ports:

• "5000:5000" restart: always

  S3-compatible storage server

  minio: image: minio/minio command: server /data env_file: .env volumes:

• ./data/minio:/data ports:

• "10000:9000" restart: always

  Create buckets for minio.

  createbuckets: image: minio/mc depends_on:

• minio env_file: .env entrypoint: > /bin/sh -c " while ! curl -s --output /dev/null --connect-timeout 1 http://minio:9000; do echo 'Waiting minio...' && sleep 0.1; done; /usr/bin/mc alias set minio http://minio:9000 $MINIO_ROOT_USER $MINIO_ROOT_PASSWORD; /usr/bin/mc mb minio/attachments; /usr/bin/mc mb minio/avatars; /usr/bin/mc mb minio/backgrounds; /usr/bin/mc mb minio/icons; /usr/bin/mc mb minio/banners; exit 0; "

  REVOLT file hosting service (Autumn)

  autumn: image: revoltchat/autumn env_file: .env depends_on:

• database
• createbuckets environment:
• AUTUMN_MONGO_URI=mongodb://database ports:

• "3000:3000" restart: always

  REVOLT metadata and image proxy (January)

  january: image: revoltchat/january ports:

• "7000:3000" restart: always

[DANW999]

The default configuration is intended for your local machine only, you have to configure the endpoints for it to work outside of your local machine.

That does not sound right. Docker port forwards exposed ports by default, unless I am missing something here?

[DANW999]

@DANW999 If you do a quick search there's quite a few utilities online to generate valid Vapid keys. Or in the .env-example file there's a link

Right thanks. I have left everything as default at the moment as I wish to test it first before making custom configurations.

[insertish]

In an effort to clean up the global issue tracker, I'm currently consolidating all issues regarding self-hosting into https://github.com/revoltchat/self-hosted/issues/25#issuecomment-1113606628.