brewDuck
-
Posts
3 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by brewDuck
-
-
Thanks for the reply. I use the same docker image with 3.9.0 and it works perfectly. the .../work mount is unnecessary, forgot about that. I use .../video/ext as where I place an NFS mount to my NAS for recordings. I change this in the interface after startup.
What's interesting is that in 3.9.0 after a reset of the camera it pops back up in the camera list as unmanaged and from there i can manage and start using it. but in 3.9.2+ nothing shows up. I go to the camera and add the video server address and adoption token, but get the above log from the camera.
-
I've been using this container for a while but when upgrading from 3.9.0 it no longer is able to connect to the camera. I run the container on a libreelec system, with a few adjustments to the docker-compose.yml to fit my needs.
When I tell the camera the controller address (doesn't show up in the controller like it does in 3.9.0) I see the error in the camera log where its unable to fully connect to the controller.
1970-01-22 21:40:23 843,818 P6 avclient[422]: standalone mode 'off', connecting to 'wss://192.168.44.233:7442/camera/1.0/ws' with uuid='' [ubnt_avclient:avclient.cpp:main:299] 1970-01-22 21:40:23 843,818 P6 avclient[422]: WAITING_FOR_CONTROLLER_ADDRESS->CONNECTING_TO_CONTROLLER [ubnt_avclient:avclient_app.cpp:State:1451] 1970-01-22 21:40:23 843,822 P6 avclient[422]: Connecting to UniFi Video: 192.168.44.233:7442. [ubnt_avclient:avclient_app.cpp:Connect:304] 1970-01-22 21:40:23 843,822 P6 avclient[422]: Connection 0990892921: changing state 'initialized' -> 'connecting' [ubnt_avclient:connection_state.cpp:SetState:28] 1970-01-22 21:40:23 843,826 P6 avclient[422]: Changing TCP_SYNCNT from 6 to 2 [ubnt_avclient:connection.cpp:ProtocolConnect:182] 1970-01-22 21:40:23 843,827 P6 analytics[393]: Entering interrupted state, reason: avclient init [ubnt_analytics:Analytics.cpp:interrupt:552] 1970-01-22 21:40:23 843,882 P6 avclient[422]: No local copy of remote cert - default to OK [ubnt_avclient:certificate_store.cpp:CompareCert:29] 1970-01-22 21:40:23 843,960 P4 avclient[422]: Internal transfer error occurred: HS: ACCEPT missing [ubnt_avclient:connection.cpp:SecureTransferProtocolHandler:285] 1970-01-22 21:40:23 843,960 P4 avclient[422]: Failed to establish connection [ubnt_avclient:avclient_app.cpp:Service:365] 1970-01-22 21:40:23 843,961 P4 avclient[422]: Host could not be reached or refused connection [ubnt_avclient:avclient_app.cpp:Service:381] 1970-01-22 21:40:23 843,962 P6 avclient[422]: try the next IP, if there is one [ubnt_avclient:avclient.cpp:main:321] 1970-01-22 21:40:23 843,962 P6 avclient[422]: Pause before restart [ubnt_avclient:avclient.cpp:main:345]
I've done all the restarts, reboots, resets, firmware upgrades I can think of. What am I missing?
Thanks.
[support] pducharme's Dockers support thread
in Docker Containers
Posted · Edited by brewDuck
Issue resolved.
Changing to 'host' gets the camera to show up. But I still have the communication problem in managing the camera. I think we've established its not a container issue (the bridge/host thing needs to be figured out) so I'll take my issue to the unify forums. Thanks a lot for the help.
-Matt
Update: starting a new container and new data directory with the container set to host network made it work! I have not yet tried to turn host network off to see if it continues working or not. Without Host networking it was unable to authenticate with the camera for managing.