Hubs cloud is currently offline.

[nupur711]

After successful deployment of the custom client, the main page of hubs cloud shows following error

[pattersonbl2]

It's very hard to tell what could be the issue based on the screenshot. This could range from service on the server not working to a database issue. I would need more logs information to start.

[nupur711]

This is what I am getting after deployment of the custom client on AWS hubs cloud.

[esperecyan]

I am having the same problem in my environment.

1. npm run deploy
2. When I access the top page, it is now loading for a few seconds and then Offline is displayed.
3. npm run undeploy
4. Still Offline.
5. Switched the stack to Offline and then to Online. Restarted the EC2 instance.
6. Offline is now displayed as soon as I open the top page.

If I try npm run undeploy in this state, I will see the following:

> [email protected] undeploy
> node -r @babel/register -r esm -r ./scripts/shim scripts/undeploy.js

Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
√ hubs.example now using Hubs master client.

If I try npm run deploy in this state, I will get the following error:

> [email protected] deploy
> node -r @babel/register -r esm -r ./scripts/shim scripts/deploy.js

Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
Deploying to hubs.example.
  |
○○○○○○○○○\hubs\node_modules\node-fetch\lib\index.js:272
                                return Body.Promise.reject(new FetchError(`invalid json response body at ${_this2.url} reason: ${err.message}`, 'invalid-json'));
                                                           ^
FetchError: invalid json response body at https://hubs.example/api/ita/configs/hubs reason: Unexpected token < in JSON at position 0
    at ○○○○○○○○○\hubs\node_modules\node-fetch\lib\index.js:272:32
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  type: 'invalid-json'
}

Node.js v17.1.0