@cssxsh okok,我晓得了,总之就是在整个登陆过程中,具体会弹出什么样的验证,以及验证结果如何,全听腾讯安排是吧,那我就还是老老实实的走滑块验证好了)
bcdw2333 发布的最新帖子
-
RE: 卡在了qq登录验证步骤
-
RE: 卡在了qq登录验证步骤
好吧,没事了,我成功登陆上去了,我又试了一下滑块登录,这回没有直接报错,而是接着提示我接收短信验证码了,现在我成功把自己的qq登录到mirai-console了,感谢各位dalao)
-
RE: 卡在了qq登录验证步骤
@Nambers 不使用滑块还有一个原因,就是我的mirai挂在了公网服务器,这种网络环境下使用滑块登录会提示“在陌生网络环境登录,滑块验证失败”之类的信息,二维码登录也是类似的情况,不过二维码的话,我可以在本地也部署一个mirai-console,然后将生成的登录文件再重新传给服务器那边的文件夹里。不过实际上我也没搞明白如何让mirai-console从滑块登录切换到二维码扫码登录)。不过听说新版本mirai支持手机验证码了,虽然我暂时还没找到让mirai使用手机验证码来验证登录的方法)
-
卡在了qq登录验证步骤
平台:debian11
java:openjdk18
使用了:- mcl-installer-1.0.7-linux-amd64
- MCL 2.1.2-61c8bd8
- chat-command-0.5.1.mirai.jar
- mcl-addon-2.1.1.jar
- mirai-api-http-2.8.0.mirai2.jar
看起来正常的部分:
00:48:39 [INFO] iTX Technologies Mirai Console Loader version 2.1.2-61c8bd8 00:48:39 [INFO] Runtime: OpenJDK 64-Bit Server VM 18.0.2.1 (arch: 64) 00:48:39 [INFO] https://github.com/iTXTech/mirai-console-loader 00:48:39 [INFO] This program is licensed under GNU AGPL v3 00:48:40 [INFO] Mirai Console Loader Announcement: Mirai Console Loader 公告栏 如果在图片上传的时候遇到问题请与我们联系 (需要提供图片文件源本) `- 如 Unsupported image type for ExternalResource * ` considering use gif/png/bmp/jpg format. `- Tracker: https://github.com/mamoe/mirai/issues/new/choose 常用资源整合 `- https://mirai.mamoe.net/topic/653 MCL 已推出 2.1.0,更好的支持 Mirai 2.11 的插件系统,建议更新。 00:48:40 [INFO] Verifying "net.mamoe:mirai-console" v2.14.0 00:48:40 [INFO] Verifying "net.mamoe:mirai-console-terminal" v2.14.0 00:48:41 [INFO] Verifying "net.mamoe:mirai-core-all" v2.14.0 00:48:41 [INFO] Verifying "org.itxtech:mcl-addon" v2.1.1 00:48:41 [INFO] Verifying "org.bouncycastle:bcprov-jdk15on" v1.64 00:48:41 [INFO] Verifying "net.mamoe:mirai-api-http" v2.8.0 00:48:41 [INFO] Verifying "net.mamoe:chat-command" v0.5.1 00:48:41 [WARN] Package "net.mamoe:chat-command" requires "net.mamoe:mirai-console" version 2.0-RC. Current version is 2.14.0 2023-02-12 00:48:42 I/main: Starting mirai-console... 2023-02-12 00:48:42 I/main: ==================================[ Mirai consosle 2.14.0 ]=================================== __ __ __ __ ______ __ | \ / \ \ | \/ \ | \ | ▓▓\ / ▓▓\▓▓ ______ ______ \▓▓ ▓▓▓▓▓▓\ ______ _______ _______ ______ | ▓▓ ______ | ▓▓▓\ / ▓▓▓ \/ \ | \| \ ▓▓ \▓▓/ \| \ / \/ \| ▓▓/ \ | ▓▓▓▓\ ▓▓▓▓ ▓▓ ▓▓▓▓▓▓\ \▓▓▓▓▓▓\ ▓▓ ▓▓ | ▓▓▓▓▓▓\ ▓▓▓▓▓▓▓\ ▓▓▓▓▓▓▓ ▓▓▓▓▓▓\ ▓▓ ▓▓▓▓▓▓\ | ▓▓\▓▓ ▓▓ ▓▓ ▓▓ ▓▓ \▓▓/ ▓▓ ▓▓ ▓▓ __| ▓▓ | ▓▓ ▓▓ | ▓▓\▓▓ \| ▓▓ | ▓▓ ▓▓ ▓▓ ▓▓ | ▓▓ \▓▓▓| ▓▓ ▓▓ ▓▓ | ▓▓▓▓▓▓▓ ▓▓ ▓▓__/ \ ▓▓__/ ▓▓ ▓▓ | ▓▓_\▓▓▓▓▓▓\ ▓▓__/ ▓▓ ▓▓ ▓▓▓▓▓▓▓▓ | ▓▓ \▓ | ▓▓ ▓▓ ▓▓ \▓▓ ▓▓ ▓▓\▓▓ ▓▓\▓▓ ▓▓ ▓▓ | ▓▓ ▓▓\▓▓ ▓▓ ▓▓\▓▓ \ \▓▓ \▓▓\▓▓\▓▓ \▓▓▓▓▓▓▓\▓▓ \▓▓▓▓▓▓ \▓▓▓▓▓ \▓▓ \▓▓\▓▓▓▓▓▓▓ \▓▓▓▓▓▓ \▓▓ \▓▓▓▓▓▓▓ 2023-02-12 00:48:42 I/main: Backend: version 2.14.0, built on 2023-02-06 14:25:21. 2023-02-12 00:48:42 I/main: Frontend Terminal: version 2.14.0, provided by Mamoe Technologies 2023-02-12 00:48:42 I/main: Welcome to visit https://mirai.mamoe.net/ 2023-02-12 00:48:43 I/plugin: Successfully loaded plugin mirai-api-http v2.8.0 2023-02-12 00:48:43 I/plugin: Successfully loaded plugin Chat Command v0.5.0 2023-02-12 00:48:43 I/plugin: Successfully loaded plugin MCL Addon v2.1.1 2023-02-12 00:48:44 I/main: Prepared built-in commands: autoLogin, help, login, logout, permission, status, stop 2023-02-12 00:48:44 W/mirai-api-http: USING INITIAL KEY, please edit the key 2023-02-12 00:48:44 I/Mirai HTTP API: ******************************************************** 2023-02-12 00:48:44 I/MahKtorAdapter[http]: Autoreload is disabled because the development mode is off. 2023-02-12 00:48:44 I/MahKtorAdapter[http]: Application started in 0.194 seconds. 2023-02-12 00:48:44 I/MahKtorAdapter[http]: Responding at http://localhost:8080 2023-02-12 00:48:44 I/http adapter: >>> [http adapter] is listening at http://localhost:8080 2023-02-12 00:48:44 I/Mirai HTTP API: Http api server is running with verifyKey: INITKEYsyl2QJUZ 2023-02-12 00:48:44 I/Mirai HTTP API: adaptors: [http] 2023-02-12 00:48:44 I/Mirai HTTP API: ********************************************************
使用起来感到困难的部分:
2023-02-12 00:48:44 I/MCL Addon: iTXTech MCL Version: 2.1.2-61c8bd8 2023-02-12 00:48:44 W/MCL Addon: iTXTech Soyuz 未安装,Soyuz MCL Handler 特性已禁用 2023-02-12 00:48:44 I/main: 3 plugin(s) enabled. 2023-02-12 00:48:44 I/main: Auto-login 1921360252, protocol: MACOS, heartbeatStrategy: STAT_HB 2023-02-12 00:48:45 I/Bot.1921360252: [SliderCaptcha] 需要滑动验证码, 请按照以下链接的步骤完成滑动验证码, 然后输入获取到的 ticket 2023-02-12 00:48:45 I/Bot.1921360252: [SliderCaptcha] Slider captcha required. Please solve the captcha with following link. Type ticket here after completion. 2023-02-12 00:48:45 I/Bot.1921360252: [SliderCaptcha] @see https://github.com/project-mirai/mirai-login-solver-selenium 2023-02-12 00:48:45 I/Bot.1921360252: [SliderCaptcha] @see https://docs.mirai.mamoe.net/mirai-login-solver-selenium/ 2023-02-12 00:48:45 I/Bot.1921360252: [SliderCaptcha] 或者输入 TxCaptchaHelper 来使用 TxCaptchaHelper 完成滑动验证码 2023-02-12 00:48:45 I/Bot.1921360252: [SliderCaptcha] Or type `TxCaptchaHelper` to resolve slider captcha with TxCaptchaHelper.apk 2023-02-12 00:48:45 I/Bot.1921360252: [SliderCaptcha] Captcha link: https://ssl.captcha.qq.com/template/wireless_mqq_captcha.html?style=simple&aid=16&uin=1921360252&sid=5367932870761891565&cap_cd=0ukZSdbklkE7wBahXzS4bqhrXaw6-ib8dN-v57IJmPLdabOuPZsP6A**&clientype=1&apptype=2
本人尝试了:
- 使用第一种滑动验证
- 使用第二种验证(请求码)
- 安装mirai-login-solver-sakura并重启mcl
- 试图使用gocqhttp-mirai
- 试图将生成的device.json放入自己本地的gocqhttp程序,以生成session.token,供mirai使用
但结果均以失败告终。
目前已知问题:- 两种滑动验证模块都已经(在github自称)失效
- mirai-login-solver-sakura似乎只支持andriod客户端使用,在我使用ssh远程命令行时,并未见到任何弹窗
- 貌似gocqhttp-mirai不是一个mirai插件,而是需要单独运行的jar文件,但是对我而言使用方法尚未明晰)
- 我使用的qq账号已经不再支持陌生网络环境下使用命令行滑块验证登录,而二维码登录则需要两边设备在同一个网络环境下。因此我在服务器上运行的机器人服务最常用的登录办法,通常是“本地扫描二维码生成token文件,然后将device.json和session.token上传到服务器使用”。我不确定miraiqq是否也能用同样的操作登录。
题外话:在我跟随安装指南的安装步骤时,曾经试图安装luckperms插件。然而在我启动mcl的时候,该插件(从logs来看)verify的时候报了网络错误,导致mcl无法启动。虽然现在我已经将该插件删除,但我认为这应该不是插件本身的锅)
若有dalao知道这种情况该如何解决,请不吝赐教,感谢各位老哥)