Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error No static resource favicon.ico on actuator paths #2469

Closed
AUMakarov opened this issue Sep 17, 2024 · 4 comments · Fixed by #2479
Closed

Error No static resource favicon.ico on actuator paths #2469

AUMakarov opened this issue Sep 17, 2024 · 4 comments · Fixed by #2479

Comments

@AUMakarov
Copy link

Describe the bug
Request to /actuator/prometheus or /actuator/health generate error
org.springframework.web.servlet.resource.NoResourceFoundException: No static resource favicon.ico

To Reproduce
Steps to reproduce the behavior:

  1. Start docker compose
  2. Open browser and navigate to http://localhost:8080/actuator/prometheus
  3. See log:
    2024-09-17T20:21:07.986Z ERROR 1 --- [nio-8080-exec-1] io.tolgee.ExceptionHandlers : org.springframework.web.servlet.resource.NoResourceFoundException: No static resource favicon.ico.

Versions and environment

  • Tolgee Platform version: Version: v3.72.0
  • Environment: Docker version v27.2.0
  • Browser: Chrome
@AUMakarov
Copy link
Author

and how to change debug level using env

@empz
Copy link

empz commented Sep 22, 2024

+1

@JanCizmar
Copy link
Contributor

Hello, I believe this error is actually incorrectly handled 404, which is currently analyzed by @Anty0. Our production prometheus run correctly, so I think you just have it disabled.

@JanCizmar
Copy link
Contributor

Oh! I see. The prometheus works. It just throws an error, when the browser searches for favicon.

@JanCizmar JanCizmar linked a pull request Sep 23, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants