JamesTX10 7 Posted October 21, 2025 Posted October 21, 2025 I was looking at the log file to review something else and see that I have a 404 error every 30 seconds 2025-10-21 00:00:29.249 Info Server-0HNGG4CFL03EP:00000001: http/1.1 Response 404 to ::1. Time: 0ms. GET http://localhost:8096/health. What is the cause and how do I resolve? embyserver.txt
Luke 42077 Posted October 21, 2025 Posted October 21, 2025 Hi, the server has no such api named /health. You must have something on your server machine sending out those requests. You will need to find out what it is and shut it down.
JamesTX10 7 Posted October 21, 2025 Author Posted October 21, 2025 Any ideas on how to track that down?
Luke 42077 Posted October 21, 2025 Posted October 21, 2025 If you temporarily enable debug logging, then you will see the request headers that it is sending, and that might have some clues in it.
JamesTX10 7 Posted October 21, 2025 Author Posted October 21, 2025 Here is what that added 2025-10-21 15:25:44.159 Debug Server-0HNGG4CFL05I4:00000001: http/1.1 GET http://localhost:8096/health. Source Ip: ::1, UserAgent: curl/8.14.1 2025-10-21 15:25:44.159 Info Server-0HNGG4CFL05I4:00000001: http/1.1 Response 404 to ::1. Time: 0ms. GET http://localhost:8096/health.
Luke 42077 Posted October 21, 2025 Posted October 21, 2025 I would start shouting down software on the server machine until they go away.
Solution speechles 2055 Posted October 21, 2025 Solution Posted October 21, 2025 @JamesTX10https://jellyfin.org/docs/general/post-install/networking/advanced/monitoring/ I would suspect it is some plugin doing it and mistakenly polling an endpoint meant for a different server platform. 1
JamesTX10 7 Posted October 21, 2025 Author Posted October 21, 2025 1 hour ago, speechles said: @JamesTX10https://jellyfin.org/docs/general/post-install/networking/advanced/monitoring/ I would suspect it is some plugin doing it and mistakenly polling an endpoint meant for a different server platform. You nailed it. I run Jellyfin in docker and configured it to use a different port BUT the health check URL was not updated. Changed that URL to have the correct port and no more errors in my Emby Logs. THANKS 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now