Page 1 of 1

error enabling ACC

Posted: Sat Mar 07, 2015 1:21 am
by raoulney
I am unable to enable ACC.

Making no other changes on the Qos Download page, I set the checkbox on the Qos download page and press SAVE CHANGES but nothing happens. The enabled setting is not preserved if I leave the page & return.

Checking the browser console I find that an error has occurred during the on-click processing (screenshot of the error attached).

This behaviour is the same under IE, FF & Chrome

Gargoyle Version:1.6.2
Model:TP-Link TL-WR1043N/ND v2
Device Configuration:Gateway

Re: error enabling ACC

Posted: Sat Mar 07, 2015 8:48 am
by pbix
v1.6.2 is quite old by now and if you search the forum you will find that no one has ever reported a problem like this before. So I am left to think that it is specific to your setup despite the fact that you have tried different browsers.

The following lines can be executed from the command line to manually enable ACC if both upload and download QoS are already enabled.

Code: Select all

uci set qos_gargoyle.download.qos_monenabled=true
uci commit
/etc/init.d/qos_gargoyle restart
If ACC still fails to enable post the output of the above qos_gargoyle restart command and

Re: error enabling ACC

Posted: Wed Jul 13, 2016 2:31 am
by RisingXun

Code: Select all

uci set qos_gargoyle.download.qos_monenabled=true
uci commit
/etc/init.d/qos_gargoyle restart
Router: TL-WDR3600v1
Firmware: gargoyle_1.9.1
qos_gargoyle config file: http://pastebin.com/t1cpLW3y

Hello,

I ran the commands you recommended and everything appears to work but I am just concerned about the error message I am getting when running the last command. Everything else is default.
Thanks

http://i63.tinypic.com/2qjk1u9.png
Image

Re: error enabling ACC

Posted: Wed Jul 13, 2016 3:32 am
by Lantis
You can't/shouldn't use WinSCP to run these commands.
You need to be logged in via SSH with a full terminal.

That is likely why you got the error.
You can alternatively reboot your router instead of issuing this restart command.

Further to this however we really should be starting a whole new thread as this is a separate issue.
1.9.1 is leaps and bounds ahead of 1.6.2 and we need to figure out what and why things aren't working for you.

So please start a new thread (even if it is the exact same problem) describing where you ran into trouble and we will go from there and see what needs fixing.
Thanks