dosubot[bot] commented on issue #36602: URL: https://github.com/apache/superset/issues/36602#issuecomment-3650250669
<!-- Greeting --> Hi @udayv2000! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> This isn't a widely reported issue, but it's plausible given recent architectural changes in Superset 6.0.0rc4. The introduction of the new AppRootMiddleware means that if your SUPERSET_APP_ROOT, APPLICATION_ROOT, or proxy (Nginx/Apache) settings are misconfigured, requests that don't start with the expected prefix will return 404s or 405s—even intermittently if the proxy or asset build is inconsistent. This is especially common in subpath deployments or when proxy headers like X-Forwarded-Prefix aren't set exactly once and correctly [[source]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/app.py#L41-L107) [[discussion]](https://github.com/apache/superset/discussions/36453). Your Python (3.9) and Node (16) versions are no longer supported for master/6.0.0rc4—Superset now requires Python 3.10/3.11 and Node 18+/20.x. Running unsupported versions can cause unpredictable routing and asset issues [[issue]](https://github.com/apache/superset/issues/35823). Troubleshooting steps: - Make sure SUPERSET_APP_ROOT, APPLICATION_ROOT, and STATIC_ASSETS_PREFIX are set consistently (or unset if not using a subpath). - If behind a proxy, ensure ProxyPass/ProxyPassReverse only apply to the subpath (not /), and all X-Forwarded-* headers are set exactly once. - Set ENABLE_PROXY_FIX = True and configure PROXY_FIX_CONFIG appropriately. - Confirm the frontend asset build is complete and you're accessing the correct port (often 9000, not 8088). - Clear your browser cache after config or proxy changes. - If you use multi-domain or CORS, check SUPERSET_WEBSERVER_DOMAINS and CORS_OPTIONS. If the issue persists after these checks, try upgrading your Python and Node versions, and look for patterns in the failing routes or actions. The new error handling stack will log all routing exceptions centrally, so detailed logs may help pinpoint the root cause [[source]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/views/error_handling.py#L132-L224). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/0603aa68-205f-490e-a7af-c105e4bd2fdd?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0603aa68-205f-490e-a7af-c105e4bd2fdd?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0603aa68-205f-490e-a7af-c105e4bd2fdd?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0603aa68-205f-490e-a7af-c105e4bd2fdd?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0603aa68-205f-490e-a7af-c105e4bd2fdd?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/0603aa68-205f-490e-a7af-c105e4bd2fdd?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0603aa68-205f-490e-a7af-c105e4bd2fdd?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=This%20isn%27t%20a%20widely%20reported%20issue%2C%20but%20it%27s%20plausible%20given%20recent%20architectural%20changes%20in%20Superset%206.0.0rc4.%20The%20introduction%20of%20the%20new%20AppRootMiddleware%20means%20that%20if%20your%20SUPERSET_APP_ROOT%2C%20APPLICATION_ROOT%2C%20or%20proxy%20%28Nginx/Apache%29%20settings%20are%20misconfigured%2C%20requests%20that%20don%27t%20start%20with%20the%20expected%20prefix%20will%20return%20404s%20or%20405s%E2%80%94even%20intermittently%20if%20the%20proxy%20or%20asset%20build%20is%20inconsistent.%20This%20is%20especially%20common%20in%20subpath%20deployments%20or%20when%20proxy%20headers%20like%20X-Forwarded-Prefix%20aren%27t%20set%20exactly%20once%20and%20correctly%20%5B%5Bsource%5D%5D%28https%3A//github.co m/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/app.py%23L41-L107%29%20%5B%5Bdiscussion%5D%5D%28https%3A//github.com/apache/superset/discussions/36453%29.%0A%0AYour%20Python%20%283.9%29%20and%20Node%20%2816%29%20versions%20are%20no%20longer%20supported%20for%20master/6.0.0rc4%E2%80%94Superset%20now%20requires%20Python%203.10/3.11%20and%20Node%2018%2B/20.x.%20Running%20unsupported%20versions%20can%20cause%20unpredictable%20routing%20and%20asset%20issues%20%5B%5Bissue%5D%5D%28https%3A//github.com/apache/superset/issues/35823%29.%0A%0ATroubleshooting%20steps%3A%0A-%20Make%20sure%20SUPERSET_APP_ROOT%2C%20APPLICATION_ROOT%2C%20and%20STATIC_ASSETS_PREFIX%20are%20set%20consistently%20%28or%20unset%20if%20not%20using%20a%20subpath%29.%0A-%20If%20behind%20a%20proxy%2C%20ensure%20ProxyPass/ProxyPassReverse%20only%20apply%20to%20the%20subpath%20%28not%20/%29%2C%20and%20all%20X-Forwarded-%2A%20headers%20are%20set%20exactly%20once.%0A-%20Set%20ENABLE_PROXY_FIX%20%3D%20Tr ue%20and%20configure%20PROXY_FIX_CONFIG%20appropriately.%0A-%20Confirm%20the%20frontend%20asset%20build%20is%20complete%20and%20you%27re%20accessing%20the%20correct%20port%20%28often%209000%2C%20not%208088%29.%0A-%20Clear%20your%20browser%20cache%20after%20config%20or%20proxy%20changes.%0A-%20If%20you%20use%20multi-domain%20or%20CORS%2C%20check%20SUPERSET_WEBSERVER_DOMAINS%20and%20CORS_OPTIONS.%0A%0AIf%20the%20issue%20persists%20after%20these%20checks%2C%20try%20upgrading%20your%20Python%20and%20Node%20versions%2C%20and%20look%20for%20patterns%20in%20the%20failing%20routes%20or%20actions.%20The%20new%20error%20handling%20stack%20will%20log%20all%20routing%20exceptions%20centrally%2C%20so%20detailed%20logs%20may%20help%20pinpoint%20the%20root%20cause%20%5B%5Bsource%5D%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/views/error_handling.py%23L132-L224%29.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/36602) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
