-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
新的版本在哪里保存rpc-secret? #473
Comments
It will be easier to help you if you could speak english. I believe most of the contributors to this projects don't speak this language. |
TL;DR: Solution 1: try #417 |
@no1xsyzy But!!!! In my scene, I use webui-aria2 to link my remote aria2 server. So I need define my host, post and token parameter. I want to know, does any plan to set a configure file? |
Found the problem. Packing caused it. @anthonyraymond Mark as bug report that |
I don't understand why people stick to this I don't need to rewrite rpc-secret everytime. |
@anthonyraymond because |
@anthonyraymond |
@no1xsyzy i see. Didn't know people used to acces it that way. That's problematic then :/ |
Closing in favor of #472. |
Just open the app.js, search " (c = p && p.auth && p.auth.token ? p.auth.token : null),", find it and modify it to “(c = "xxxx-there is your own token-xxxx"),”. 在app.js中搜索上面提到的那行代码,修改成上面提到的格式,这样做对于直接从文件打开index.html有效,也没有别的影响,唯一的问题只是在输入token的元素内不会显示占位符,它直接就是空的。
|
下载了最新的版本,在网页界面的设置--连接设置--主机里面输入rpc-secret=SECRET@localhost, 或是在密码令牌(可选)处输入SECRET,可以正确的连接aria2c,但是退出浏览器后,再打开,又要再次输入,如何才能输入一次后保存呢?以前的版本是在configuration.js里面修改,现在修改了这个文件也是无效。求帮助,谢谢。
Download the latest version, in the web interface settings - connection settings - enter rpc-secret=SECRET@localhost in the host, or enter SECRET at the password token (optional), i can connect aria2c correctly, but exit After the browser, open it again, and then enter it again. How can I save it after entering it once? The previous version was modified in configuration.js, and now modifying this file is also invalid. Ask for help, thank you.
The text was updated successfully, but these errors were encountered: