Giter VIP home page Giter VIP logo

Comments (4)

exsilium avatar exsilium commented on June 10, 2024

Hi @loop2 ! Which version you are pulling? v3.8.0?

With the guided setup the NVC reported IP will be the Docker internal IP, in your case the 172.170.0.2. It should be and has been thus far only cosmetic and shouldn’t impact functionality.

However, v3.8.0 introduced a new secure communication port so altough my own setup keeps on working, I haven’t provisioned new cameras.

If you did try v3.8.0 and are trying a new setup maybe you can pull v3.7.3 to see if that works for you. If it does, I can try to reproduce the issue on v3.8.0.

Let me know, thanks!

from docker-unifi-video.

loop2 avatar loop2 commented on June 10, 2024

Hi! Thanks for the support!
Finally i can use it... but i need to unmanage the camera and after that clik on manage, set the camera ip in 172.170.0.1 (instead the real ip), set the real ip of controller and the port 7442 in the camera setup...
The strange thing is that the setup is with this fake ip but the camera information show the real ip!
Now is fully working! thanks

from docker-unifi-video.

exsilium avatar exsilium commented on June 10, 2024

Hi and thanks for the feedback. It seems it needs further testing on the newest version of the NVC. Thus far the internal IP hasn't blocked any update or provisioning processes, you just needed to do it once from the camera side.

It sounds like

  1. You provisioned camera on an older firmware to v3.8.0
  2. The provisioning worked or required a camera firmware upgrade right away?
  3. Either case the cameras were unable to connect to the NVC because they were trying to connect to the Docker's internal IP.
  4. You needed to unmanage the cameras and re-provision them from the camera side.

If nothing else then probably this scenario needs further documenting. In my case, my cameras were already provisioned prior to moving to v3.8.0. The camera firmware upgrade happened normally after the NVC version upgrade and all the cameras connected automatically after firmware upgrade.

It might be that the NVC reported IP is used in this case when the camera firmware upgrade happens during provisioning of the camera....

from docker-unifi-video.

exsilium avatar exsilium commented on June 10, 2024

Closing as of now, let me know if there are further issues with your setup. Cheers! 🍻

from docker-unifi-video.

Related Issues (9)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.