dosubot[bot] commented on issue #31025: URL: https://github.com/apache/superset/issues/31025#issuecomment-2492580834
<!-- Greeting --> Hey there, @arm-moodys! I'm here to help you with any bugs, questions, or contributions you have. Let's tackle this issue together! <!-- Answer --> I found a similar unsolved discussion that might be relevant to your issue: [Custom Logo with Docker + nginx-proxy not working](https://github.com/apache/superset/discussions/28206) <sup>[[1]](https://github.com/apache/superset/discussions/28206)</sup>. To address the "404 NOT FOUND" error for "/favicon.ico" in Superset, ensure that the favicon path is correctly configured. According to the `superset/config.py`, the favicon is set as follows: ```python FAVICONS = [{"href": "/static/assets/images/favicon.png"}] ``` Make sure the file `/static/assets/images/favicon.png` exists in your Superset deployment. If the file is missing, place the favicon image at the specified path. If the path is incorrect, update the `FAVICONS` configuration with the correct path to your favicon file. If the file exists and the path is correct, but you are still encountering the error, check your Nginx Ingress configuration to ensure that requests to `/favicon.ico` are correctly routed to the Superset application. You may need to add a location block in your Nginx configuration to handle requests for the favicon <sup>[[2]](https://github.com/apache/superset/blob/master/superset/config.py)</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: [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]
