RocketChat / RocketChat/Rocket.Chat

Rocket chat setup-wizard doesn't work after install

Open
#15,744 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

deployment
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

rocketchat_1          | ➔ |  Rocket.Chat Version: 2.0.0                           |
rocketchat_1          | ➔ |       NodeJS Version: 8.11.4 - x64                    |
rocketchat_1          | ➔ |      MongoDB Version: 4.0.13                          |
rocketchat_1          | ➔ |       MongoDB Engine: mmapv1                          |
rocketchat_1          | ➔ |             Platform: linux                           |
rocketchat_1          | ➔ |         Process Port: 3000                            |
rocketchat_1          | ➔ |             Site URL: http://{mydomain}.com  |
rocketchat_1          | ➔ |     ReplicaSet OpLog: Enabled                         |
rocketchat_1          | ➔ |          Commit Hash: 92c00dc3c2                      |
rocketchat_1          | ➔ |        Commit Branch: HEAD   

I setup rocket chat and configured ssl as guide direct.
After visit my domain it redirected to setup-wizard.
But it shows black blank screen. so I checked console. it shows below.

cc945290c4dafe28d2516121de8ec1f7c477a095.js?meteor_js_resource=true:21 Mixed Content: The page at 'https://{mydomain}.com/setup-wizard' was loaded over HTTPS, but requested an insecure resource 'http://{mydomain}.com/__meteor__/dynamic-import/fetch'. This request has been blocked; the content must be served over HTTPS.

Anybody help...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the blank setup-wizard page over HTTPS and inspect the meteor/dynamic-import/fetch request shown in the browser console. Trace how the setup wizard and dynamic import resource build their URLs, then verify that the wizard renders without a mixed-content error when SSL is enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
mongodb, nodejs
Domain
frontend, security, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.