Hi

I'm running VigorConnect using Docker on a Synology NAS.
I have a 2860 and 4 AP906 AP's.  I've also got a 3912s & PQ2200xb waiting to be deployed over the next few days.

I go into VigorConnect and can discover all these devices.  If I use the checkbox against an item in the Discover box/area having updated the login details for that device, it disappears from the list but never appears anywhere else.  If I hit the Discover button again, it will reappear in the Discover box.
A couple of weeks ago I had the root node appearing but adding the nodes did nothing.  At some point in my diagnosis, I have lost the root node from being recognised (something I've done) and due to the above, I can't add it again (doing so does nothing).
There doesn't seem to be any relevant logging that I can find (I've even looked at the docker container from the command line).  I've created a new container from the image but I have the same issue.

In VigorConnect, I go to System / ACS Server and I have the IP address, port, username and password for my VC installation on my Synology NAS (so the username/password I use to login in to VC rather than the NAS).  At the bottom of that page, I have the VigorConnect section with username and password; I've tried various options there.
In the AP906, System Maintenance / TR-069 section, there is a username and password for ACS Settings, CPE settings - I don't know if those are supposed to match any of the settings in VC.  There's also the STUN settings and XMPP settings options which again may be relevant.  I'm thinking there's an inconsistency between APs and VC.
Ideally I'd like to reset the APs but I can't get downtime at the minute.

I'm running VigorConnect 1.8.2; trying 1.9.2 fails to start the container, saying the file used to start the application doesn't exist.

Any ideas?  I've had a support ticket open for a couple of weeks but it hasn't made much progress (I've not had the level of support I've had in the past which has been detailed and excellent).

Thanks
 

Hi  amadeus ,


Which model Synology Nas are you running and what version of the DSM are you on? Have you tried the VC 1.9.2 in ‘Container Manager’ rather than ‘Docker’?

I have 1.9.2 working fine on a Synology system on the latest DSM version using ‘Container Manager’ to host the VC (downloaded directly from DrayTek).


On adding devices, I tried adding the devices via the discovery tool at first, then switched to adding the devices to VC via the device’s TR069 page instead. (And I suggest using https connections wherever possible).

Within the VC software, you’ll need to setup your networks first. Create a Username and password for each network(site), then goto the device’s TR069 page and enter those matching credentials in. The device will then connected to the VC and be added to that relevant network within VC.

So if you have 5 networks (sites), for example, you can quite quickly add each device to the correct network on VC by entering in the relevant credentials for that site so the device(s) get assigned automatically to them.

There are some limitations with VC, it only really supports APs and Switches, even though you can add  older model routers to it as well, but I wouldn’t advise it nowadays, VC almost “bricked” my 2862ac which I only realised after several days of no issues until I needed to reboot the router after a firmware update and suddenly it wouldn’t reboot, it just got stuck in a boot-loop, the only way to recover the router was via a TFTP restore, and it wasn’t the firmware version, as I rolled back to the previous 5 releases and all of them “bricked” (boot-looped) after a restart!
Restoring my config each time, and then only enabling TR069 and connecting it to VC, would cause the loop during a reboot!