dosubot[bot] commented on issue #29913: URL: https://github.com/apache/superset/issues/29913#issuecomment-2282369279
<!-- Answer --> To resolve the proxy issue with the Superset frontend, ensure that the backend server (Superset server) is running and accessible at the specified port. The error `[ECONNREFUSED]` indicates that the connection to the backend server was refused, which typically means that the server is not running or is not accessible at the specified address and port. Here are the steps to resolve the issue: 1. **Ensure the Superset Backend is Running**: Make sure that the Superset backend server is running on the specified port (e.g., `http://xxxx:8000`). You can start the backend server using the following command: ```bash superset run -p 8000 --with-threads --reload --debugger --debug ``` 2. **Check the Configuration**: Verify that the `supersetPort` and `supersetUrl` are correctly set to point to your running Superset backend server. In your case, it seems you are using a custom URL. Ensure that the URL is correct and the server is accessible. 3. **Modify the Configuration if Necessary**: If your Superset backend is running on a different port or URL, update the configuration accordingly. For example, if your backend is running on port `8000`, you can modify the configuration like this: ```js const { supersetPort = 8000, superset: supersetUrl = 'http://xxxx:8000' } = parsedEnvArg(); const backend = (supersetUrl || `http://localhost:${supersetPort}`).replace( '//+$/', '', ); // strip ending backslash ``` 4. **Restart the Frontend Development Server**: After making any changes, restart your frontend development server to apply the new configuration. You can start the Webpack dev server using the following command: ```bash npm run dev-server -- --env=--superset=http://xxxx:8000 ``` Additionally, ensure that the `webpack.config.js` file is correctly set up to handle the proxy configuration. Here is the relevant part of the `webpack.config.js` file: ```js const getProxyConfig = require('./webpack.proxy-config'); let proxyConfig = getProxyConfig(); if (isDevMode) { config.devtool = 'eval-cheap-module-source-map'; config.devServer = { onBeforeSetupMiddleware(devServer) { // load proxy config when manifest updates const { afterEmit } = getCompilerHooks(devServer.compiler); afterEmit.tap('ManifestPlugin', manifest => { proxyConfig = getProxyConfig(manifest); }); }, historyApiFallback: true, hot: true, port: devserverPort, // Only serves bundled files from webpack-dev-server // and proxy everything else to Superset backend proxy: [ // functions are called for every request () => proxyConfig, ], client: { overlay: { errors: true, warnings: false, runtimeErrors: error => !/ResizeObserver/.test(error.message), }, logging: 'error', }, static: path.join(process.cwd(), '../static/assets'), }; } ``` By ensuring that the backend server is running and accessible at the specified address and port, and that the Webpack configurations are correctly set up, you should be able to resolve the proxy issue <sup>[[1]](https://github.com/apache/superset/blob/master/superset-frontend/webpack.proxy-config.js)</sup><sup>[[2]](https://github.com/apache/superset/blob/master/superset-frontend/webpack.config.js)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
