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 go to 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 that 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!

Hi @HodgesanDY,

Sorry for the delay; mainly due to life getting in the way but also due to excitement of it working!

So, to answer your questions:
I am trying this on a Synology DS713 NAS; it's old but I use it as my sacrificial device to try things, as well as a backup of my live NAS data (NAS is not a backup, right?).  It only has Docker, as opposed to Container Manager available for it.
After your comment on this, I tried uploading the 1.9.2 image to the live NAS (DS1520) and starting a container which worked fine.  Re-uploading the 1.9.2 image to the DS713 then allowed me to create a container sucessfully.  For some reason I'd understood that there was some degree of validation on an image upload but with hindsight that was foolish (where would the validation end without starting a container?), but regardless, I assume there was an issue with the upload.  The DS713 only has 2GB RAM which I'd have expected to be enough, but it seems not. 

I did as you suggested (including using HTTPS which I'd do as a matter of course); in VC I went to Network Management, added a new network and made a note of the username and password used for that new network.  I then went to each of the AP906 devices, System Maintenance, TR-069 and in the ACS settings section (the top section of the page - CPE Settings, Periodic Inform Settings, STUN Settings, XMPP Settings are below that), I used the username and password I'd used in the VC Network Management settings.  I then saved the pageand the "Test With Inform" returned a green icon.  Success. 
Note: the "Test With Inform" button seems to use the *saved* version of the details as opposed to what you might have typed in before pressing the OK button.

Going back to VC, Dashboard, New Devices, Discover, and this time adding them worked fine; they appeared in the Device Overview panel.

On your advice, I eschewed adding the Vigor 2860 router.

I'm currently having issues with Configuration / Mesh, which shows (only) my root node and a checkbox; the link on the root node is active but doesn't take me anywhere.  Hitting the "Add Mesh Group" button takes me to a screen asking for various data but it timesout when I hit the "Create" button.  I've had a scan through documentation and not found the issue yet (again, lack of logging makes it more diffcult) but I'll report back here once I've got it sorted so any other users will be able to find it all in on thread.

Thanks very much for your help @HodgesanDY, really appreciated.

rgds


 

Hi amadeus ,

On your advice, I eschewed adding the Vigor 2860 router. 

By all means try it, just make sure you create a config backup of the router before you do so, you may have more success than I did, plus, yours is a slightly different model, so you never know... If it does enter a boot-loop, just hold the reset button in for 10 seconds (roughly) until the LEDs on the front blink in a unique sequence (see here for more info), then plug an ethernet cable directly into one of the ports and re-flash it with the latest, or older, firmware; downloadable from DrayTek's FTP. (See here )

I'm currently having issues with Configuration / Mesh, which shows (only) my root node and a checkbox; the link on the root node is active but doesn't take me anywhere.  Hitting the "Add Mesh Group" button takes me to a screen asking for various data but it timesout when I hit the "Create" button.  I've had a scan through documentation and not found the issue yet (again, lack of logging makes it more diffcult) but I'll report back here once I've got it sorted so any other users will be able to find it all in on thread.

I can't lend any help to the Mesh system, only for lack of experience, as I tend to avoid Mesh at all costs, instead running cables to every AP to make their connection to the network, but I appreciate this isn't always possible for everyone.

With Vigor Connect, and this is only my opinion, and also stretches to the 'Central Management' config pages of the many routers that cater to them, is that DrayTek realised their license-based ACS management service would be far more lucrative for them and abandoned development of these features in the local routers (and software like 'Connect') to focus on the cloud management version (or rather, licenced versions), I don't blame them, as it is a better business model but, surely you wouldn't want to limit your product range from having fantastic features - as it attracts long-term users that become loyal to the brand based on the ecosystem that they get used to.

My point is, the Vigor Connect software has clearly been stripped back and has some leftover function calls still remaining, for example with the AP802, if you click on the LAN port icon in the image of the unit when viewing the 'Dashboard' page of that device, it tries to launch the 'LAN' config page which does appear in the ACS licensed version. (See page 356 of the ACS3 manual here )

So if you find yourself wondering why it's offering you functions that don't work or take you to a never ending loading page, I reckon that is why! 

Admittedly though, that green "Create" button should really work. Have you checked that your container isn't blocking certain ports, that the software needs open, to be able to communicate with the AP's?

@HodgesanDY

I may register the 2860 at some point but I'm about to deploy my new 3912s so once that's up and going, I'll try the 2860 because if things *do* go wobbly, I won't have anyone (specifically my wife!) shouting at me that she's not able to work.

I've come up with a handful of issues with VC that I'll call support about to see if they'd like them all in one ticket or as individual tickets, and maybe gently probe the question of how interested they are in dealing with issues.  Like you, for various reasons, I'm getting the feeling it's a little unloved.
I suppose I could get an ACS licence but frankly it's only for my home use and I just prefer to use containers locally (as well as saving a few quid) and don't need the extra functionality that ACS provides.  Once I'm fully au fait with it, I may want to migrate but that day is not today (to coin a phrase).

So, for anyone else who wonders why their devices are not in a network group.
I went to (in VC) Network Management and saw a list of my 4 AP906 devices under the Root Network node.  Clicking each of those nodes takes me to a page with CPE client data on it, including the CPE Client User Name and associated password.  Those details need to matcht the details on the AP906 in System Maintenance/TR-069 page.
Once that was done, things kicked into life.

The only thing which is *slightly* odd (and on my list of topics to discuss with Draytek) is that one of the AP906 devices in VC has the old/default username and password and when I try to change it, it says "Processing..." for a minute or so, then fails with a message "Response Timeout".  I've not worked out what the issue is.  I can use wget to get the CRN.html page, using the username and password which is shown on the AP906.  I guess maybe the solution (and what I'd expect Draytek to direct me to do) would be to do a reset of the AP906 and re-add it but given this seems a little fragile (tho may be my current lack of knowledge), I'm loathe to do that in case it makes things worse.

many thanks for your help, much appreciated.
I'll add to this ticket if I get any more relevant info so others may benefit, as well as for my reference should I ever need it again!