|
新版默认配置用RPC密钥登陆,取代旧的用户名密码方式
token不是用户名,token:secret是token是secret的意思,是yaaw兼容新版指定的https://github.com/binux/yaaw#usage
aria2c --enable-rpc --rpc-listen-all=true --rpc-allow-origin-all with 'JSON-RPC PATH' like http://hostname:port/jsonrpc
Recommend: Set --rpc-secret=<secret> if you are using aria2 1.18.4(or higher) with 'JSON-RPC PATH' like http://token:secret@hostname:port/jsonrpc
Set --rpc-user=<username> --rpc-passwd=<passwd> if you are using aria2 1.15.2(or higher) with 'JSON-RPC PATH' like http://username:passwd@hostname:port/jsonrpc
https问题aria2官网有说明https://github.com/aria2/aria2/blob/master/README.rst
Since 1.1.0, aria2 checks the certificate of HTTPS servers by default. If you build with OpenSSL or the recent version of GnuTLS which has gnutls_certificate_set_x509_system_trust() function and the library is properly configured to locate the system-wide CA certificates store, aria2 will automatically load those certificates at the startup. If it is not the case, I recommend to supply the path to the CA bundle file. For example, in Debian the path to CA bundle file is '/etc/ssl/certs/ca-certificates.crt' (in ca-certificates package). This may vary depending on your distribution. You can give it to configure script using --with-ca-bundle option:
$ ./configure --with-ca-bundle='/etc/ssl/certs/ca-certificates.crt'
$ make
Without --with-ca-bundle option, you will encounter the error when accessing HTTPS servers because the certificate cannot be verified without CA bundle. In such case, you can specify the CA bundle file using aria2's --ca-certificate option. If you don't have CA bundle file installed, then the last resort is disable the certificate validation using --check-certificate=false.
3种解决方法都可以
1:指定证书重编译
2:opkg安装证书,启动参数或配置文件指定证书
3:启动参数或配置文件设置不检查证书
有了Aria-Ng就可以抛弃YAAW了。
|
|