[Support]: [Errno 98] Address already in use #5444
Comments
|
Please read the release notes, this is covered https://github.com/blakeblackshear/frigate/releases/tag/v0.12.0-beta7 |
|
Thanks, I removed the PATH variable override in Portainer and it starts now but yields a different problem. What I removed (PATH variable shown below): What I see: Logs: |
|
looks like the container uses a port that another one of your containers also is using |
|
Hmm odd, I've only dipped my toes into docker/portainer so I don't have much running: After a bit it does restart and it shows the port bindings for frigate: |
|
what network mode is frigate running in? |
|
Just the default I believe, I tried a macvlan when I first tested the stable build and couldn't get that to work so I just went back to the default.
This is the full info from Inspect: |
|
By the way, if I roll back to stable it seems to run fine (I tested before removing the PATH variable) |
|
you may want to try getting frigate to run in bridge network_mode, otherwise try running
there are like 4 ports that have been added in this release so that isn't unexpected |
|
Here's the output from that; I'll try and figure out how to swap to bridge mode a second to test that. Edit -- same result with bridge mode (seems to show a loading indicator on the web page and then frigate stops and restarts in an indefinite loop.) |
|
Nothing particularly telling/new from the inspector network tab but I figured I'd drop a screenshot here just in case you see anything I don't. This is when I'm trying to just load the page before it exits and restarts: |
|
can you try disabling RTMP and see what happens? |
|
We have seen this reported a couple times, but can't track it down. This could be another way portainer is ruining everything good in this world /s Rather than modifying an existing stack in portainer, can you just delete the whole thing and recreate it? |
|
Yes I will try both of those things tomorrow; thank you for the help!! |
|
This can be resolved by setting the Command back to Default instead of Override in Portainer
|
NickM-27
changed the title
I can confirm this fixes the issue on beta 8 -- thank you!! |
|
Oh wow, that is interesting, good to know. I will add this to the release notes |
|
Was running in to the same issue but on Synology Docker. The following worked for me:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the problem you are having
Moved from stable to beta on a raspberry pi 4 to try and get hardware acceleration going, however, I am running into an issue where it says NGINX isn't found? Not sure how to proceed here; any help would be much appreciated. Thank you!
Version
0.12.0-beta7
Frigate config file
Relevant log output
FFprobe output from your camera
N/A won't startFrigate stats
No response
Operating system
Debian
Install method
Docker Compose
Coral version
CPU (no coral)
Network connection
Wired
Camera make and model
Wyze Cam v3
Any other information that may be helpful
No response
The text was updated successfully, but these errors were encountered: