From 9fee1aa68ac6dbc53615332bc0142a06f3e5f03f Mon Sep 17 00:00:00 2001 From: Vojtech Simetka Date: Wed, 2 Jun 2021 12:13:17 +0200 Subject: [PATCH] fix: troubleshooting on a mac and clearer CORS setup guide (#131) * fix: service status check on macOS * fix: config file location on mac and making the CORS setup clearer * fix: error in the README cors instructions --- README.md | 2 +- .../status/SetupSteps/DebugConnectionCheck.tsx | 15 ++++++--------- .../status/SetupSteps/NodeConnectionCheck.tsx | 8 ++------ 3 files changed, 9 insertions(+), 16 deletions(-) diff --git a/README.md b/README.md index e3fb3ae..347d678 100644 --- a/README.md +++ b/README.md @@ -38,7 +38,7 @@ npm install -g @ethersphere/bee-dashboard ## Usage -:warning: To successfully connect to the Bee node, you will need to enable CORS for it. You can do so by setting `cors-allowed-origins: *` in the Bee config file and then restart the Bee node. To see where the bee config file is, consult the [official Bee documentation](https://docs.ethswarm.org/docs/working-with-bee/configuration#configuring-bee-installed-using-a-package-manager) +:warning: To successfully connect to the Bee node, you will need to enable the Debug API and CORS. You can do so by setting `cors-allowed-origins: ['*']` and `debug-api-enable: true` in the Bee config file and then restart the Bee node. To see where the config file is, consult the [official Bee documentation](https://docs.ethswarm.org/docs/working-with-bee/configuration#configuring-bee-installed-using-a-package-manager) ### Terminal diff --git a/src/pages/status/SetupSteps/DebugConnectionCheck.tsx b/src/pages/status/SetupSteps/DebugConnectionCheck.tsx index c7a7409..d61d646 100644 --- a/src/pages/status/SetupSteps/DebugConnectionCheck.tsx +++ b/src/pages/status/SetupSteps/DebugConnectionCheck.tsx @@ -41,11 +41,7 @@ export default function NodeConnectionCheck({ isLoading, isOk }: Props): ReactEl
  1. Check the status of your node by running the below command to see if your node is running.
    2. - +
  2. If your node is running, check your firewall settings to make sure that port 1635 (or your custom specified port) is bound to localhost. If your node is not running try executing the below command @@ -71,19 +67,20 @@ export default function NodeConnectionCheck({ isLoading, isOk }: Props): ReactEl
  3. Lastly, check your nodes configuration settings to validate the debug API is enabled and the Cross Origin Resource Sharing (CORS) setting is configured to allow your host. Config parameter{' '} debug-api-enable must be set to true and{' '} - cors-allowed-origins must be set to your host domain or IP. If edits are made to - the configuration run the restart command below for changes to take effect. + cors-allowed-origins must be set to your host domain or IP (you can also use the + wildcard {"cors-allowed-origins: ['*']"}). If edits are made to the configuration run + the restart command below for changes to take effect.
diff --git a/src/pages/status/SetupSteps/NodeConnectionCheck.tsx b/src/pages/status/SetupSteps/NodeConnectionCheck.tsx index 1bc871e..f571451 100644 --- a/src/pages/status/SetupSteps/NodeConnectionCheck.tsx +++ b/src/pages/status/SetupSteps/NodeConnectionCheck.tsx @@ -32,11 +32,7 @@ export default function NodeConnectionCheck({ isLoading, isOk }: Props): ReactEl
  1. Check the status of your node by running the below command to see if your node is running.
    2. - +
  2. If your node is running, check your firewall settings to make sure that port 1633 (or your custom specified port) is exposed to the internet. If your node is not running try executing the below @@ -51,7 +47,7 @@ export default function NodeConnectionCheck({ isLoading, isOk }: Props): ReactEl