Closed Kurisutian closed 1 year ago
This is also happening with multiple apps (like Readarr, Radarr...)
2023-04-19 9:46:06
Startup probe failed: Get "http://172.16.1.69:8787/": dial tcp 172.16.1.69:8787: connect: connection refused
2023-04-19 9:45:53
Created container readarr
2023-04-19 9:45:53
Started container readarr
Well it's hopefully going to be enough apps which act out this way so it will become a bit of a higher priority. The spouse is not very amused to not be able to watch any TV atm. 🙈
Unfortunately it still is not working despite the attempt to fix it. The suggestion in Discord was to change the probe to TCP (https://discord.com/channels/830763548678291466/1098128570234187806/1098608187139170336)
This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists
App Name
tvheadend
SCALE Version
22.12.2
App Version
15.0.6
Application Events
Application Logs
Application Configuration
Intentionally changed:
Describe the bug
As you can see in the application events there is a startup probe error:
Startup probe failed: HTTP probe failed with statuscode: 401
However the app works fine till it gets killed by the system most likely due to this error. TV Headend does not have a restricted login locally but a static IP because of the SatIP server as described above. So currently until the container is restarting everything works, watching TV is possible, until the restart of the container happens.
To Reproduce
Expected Behavior
Since the app is running and can be reached through the static IP, the startup probe succeeds since I can already get to the TV Headend website until the container will be force restarted.
Screenshots
N.A.
Additional Context
Needed to set a static IP and the runtime options to get the SatIP Server in the network working. It worked prior to the latest upgrade so the settings are verified and did work already. I cannot leave them out otherwise the SatIP Server cannot be used.
I've read and agree with the following