好像qsign配置文件我的还少了
"package_name": "com.tencent.mobileqq",
这一行
和
"black_list": [
1008611
]
这一块
Jadlokin-Scarlet 发布的帖子
-
RE: 协议问题汇报
-
RE: 协议问题汇报
@cssxsh 试了一下这个,居然成功登上去了,不知道为啥,按理来说应该没差别才对,难道是txlib除了android_phone.json还需要另外这几个文件?
https://github.com/MrXiaoM/qsign -
RE: 协议问题汇报
mirai 版本
===================================[ Mirai console 2.15.0 ]===================================
| \ / \ \ | / \ |
| ▓▓\ / ▓▓\▓▓ ______ ______ \▓▓ ▓▓▓▓▓▓\ ______ _______ _______ ______ | ▓▓ ______
| ▓▓▓\ / ▓▓▓ / \ | | \ ▓▓ \▓▓/ | \ / / | ▓▓/
| ▓▓▓▓\ ▓▓▓▓ ▓▓ ▓▓▓▓▓▓\ \▓▓▓▓▓▓\ ▓▓ ▓▓ | ▓▓▓▓▓▓\ ▓▓▓▓▓▓▓\ ▓▓▓▓▓▓▓ ▓▓▓▓▓▓\ ▓▓ ▓▓▓▓▓▓
| ▓▓\▓▓ ▓▓ ▓▓ ▓▓ ▓▓ \▓▓/ ▓▓ ▓▓ ▓▓ | ▓▓ | ▓▓ ▓▓ | ▓▓\▓▓ | ▓▓ | ▓▓ ▓▓ ▓▓ ▓▓
| ▓▓ \▓▓▓| ▓▓ ▓▓ ▓▓ | ▓▓▓▓▓▓▓ ▓▓ ▓▓/ \ ▓▓__/ ▓▓ ▓▓ | ▓▓_\▓▓▓▓▓▓\ ▓▓__/ ▓▓ ▓▓ ▓▓▓▓▓▓▓▓
| ▓▓ \▓ | ▓▓ ▓▓ ▓▓ \▓▓ ▓▓ ▓▓\▓▓ ▓▓\▓▓ ▓▓ ▓▓ | ▓▓ ▓▓\▓▓ ▓▓ ▓▓\▓▓
\▓▓ \▓▓\▓▓\▓▓ \▓▓▓▓▓▓▓\▓▓ \▓▓▓▓▓▓ \▓▓▓▓▓▓ \▓▓ \▓▓\▓▓▓▓▓▓▓ \▓▓▓▓▓▓ \▓▓ \▓▓▓▓▓▓▓2023-09-11 15:08:48 I/main: Backend: version 2.15.0, built on 2023-07-11 04:57:17.
2023-09-11 15:08:48 I/main: Frontend Terminal: version 2.15.0, provided by Mamoe Technologies
协议版本信息
ANDROID_PHONE 8.9.63.11390 2023-05-26T10:46:18+08:00
ANDROID_PAD 8.9.63.11390 2023-05-26T10:46:18+08:00
ANDROID_WATCH 2.0.8 2019-06-03T20:25:31+08:00
IPAD 8.9.50.611 2023-02-16T15:10:14+08:00
MACOS 6.8.2.21241 2022-03-14T11:11:35+08:00
登录方式及使用的协议
密码登录(ANDROID_PAD)出现的问题
登录不上,日志为17:10:37 [INFO] iTX Technologies Mirai Console Loader version 2.1.2-61c8bd8 17:10:37 [INFO] Runtime: OpenJDK 64-Bit Server VM 11.0.16 (arch: 64) 17:10:37 [INFO] https://github.com/iTXTech/mirai-console-loader 17:10:37 [INFO] This program is licensed under GNU AGPL v3 17:10:38 [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 的插件系统,建议更新。 17:10:38 [INFO] Verifying "net.mamoe:mirai-console" v2.15.0 17:10:39 [INFO] Verifying "net.mamoe:mirai-console-terminal" v2.15.0 17:10:39 [INFO] Verifying "net.mamoe:mirai-core-all" v2.15.0 17:10:40 [INFO] Verifying "org.itxtech:mcl-addon" v2.1.1 17:10:40 [INFO] Verifying "org.bouncycastle:bcprov-jdk15on" v1.64 2023-09-11 17:10:41 I/main: Starting mirai-console... 2023-09-11 17:10:41 I/main: ===================================[ Mirai console 2.15.0 ]=================================== __ __ __ __ ______ __ | \ / \ \ | \/ \ | \ | ▓▓\ / ▓▓\▓▓ ______ ______ \▓▓ ▓▓▓▓▓▓\ ______ _______ _______ ______ | ▓▓ ______ | ▓▓▓\ / ▓▓▓ \/ \ | \| \ ▓▓ \▓▓/ \| \ / \/ \| ▓▓/ \ | ▓▓▓▓\ ▓▓▓▓ ▓▓ ▓▓▓▓▓▓\ \▓▓▓▓▓▓\ ▓▓ ▓▓ | ▓▓▓▓▓▓\ ▓▓▓▓▓▓▓\ ▓▓▓▓▓▓▓ ▓▓▓▓▓▓\ ▓▓ ▓▓▓▓▓▓\ | ▓▓\▓▓ ▓▓ ▓▓ ▓▓ ▓▓ \▓▓/ ▓▓ ▓▓ ▓▓ __| ▓▓ | ▓▓ ▓▓ | ▓▓\▓▓ \| ▓▓ | ▓▓ ▓▓ ▓▓ ▓▓ | ▓▓ \▓▓▓| ▓▓ ▓▓ ▓▓ | ▓▓▓▓▓▓▓ ▓▓ ▓▓__/ \ ▓▓__/ ▓▓ ▓▓ | ▓▓_\▓▓▓▓▓▓\ ▓▓__/ ▓▓ ▓▓ ▓▓▓▓▓▓▓▓ | ▓▓ \▓ | ▓▓ ▓▓ ▓▓ \▓▓ ▓▓ ▓▓\▓▓ ▓▓\▓▓ ▓▓ ▓▓ | ▓▓ ▓▓\▓▓ ▓▓ ▓▓\▓▓ \ \▓▓ \▓▓\▓▓\▓▓ \▓▓▓▓▓▓▓\▓▓ \▓▓▓▓▓▓ \▓▓▓▓▓▓ \▓▓ \▓▓\▓▓▓▓▓▓▓ \▓▓▓▓▓▓ \▓▓ \▓▓▓▓▓▓▓ 2023-09-11 17:10:41 I/main: Backend: version 2.15.0, built on 2023-07-11 04:57:17. 2023-09-11 17:10:41 I/main: Frontend Terminal: version 2.15.0, provided by Mamoe Technologies 2023-09-11 17:10:41 I/main: Welcome to visit https://mirai.mamoe.net/ 2023-09-11 17:11:36 I/org.apache.http.impl.execchain.RetryExec: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://maven.aliyun.com:443: The target server failed to respond 2023-09-11 17:11:36 I/org.apache.http.impl.execchain.RetryExec: Retrying request to {s}->https://maven.aliyun.com:443 2023-09-11 17:11:56 I/plugin: Successfully loaded plugin mirai-api-http v2.9.1 2023-09-11 17:11:56 I/fix-protocol-version: 协议版本检查更新... 2023-09-11 17:11:56 I/fix-protocol-version: ANDROID_PHONE load from file:///root/android_phone.json 2023-09-11 17:11:56 I/fix-protocol-version: ANDROID_PAD load from file:///root/android_pad.json 2023-09-11 17:11:56 I/fix-protocol-version: 注册服务... 2023-09-11 17:11:56 I/fix-protocol-version: 服务配置文件: file:///root/KFCFactory.json 2023-09-11 17:11:56 I/plugin: Successfully loaded plugin fix-protocol-version v1.11.0 2023-09-11 17:11:56 I/plugin: Successfully loaded plugin MCL Addon v2.1.1 2023-09-11 17:11:57 I/main: Prepared built-in commands: autoLogin, help, login, logout, permission, status, stop 2023-09-11 17:11:57 I/Mirai HTTP API: ******************************************************** 2023-09-11 17:11:57 I/MahKtorAdapter[http,ws]: Autoreload is disabled because the development mode is off. 2023-09-11 17:11:57 I/MahKtorAdapter[http,ws]: Application started in 0.157 seconds. 2023-09-11 17:11:57 I/MahKtorAdapter[http,ws]: Responding at http://0.0.0.0:8085 2023-09-11 17:11:57 I/http adapter: >>> [http adapter] is listening at http://0.0.0.0:8085 2023-09-11 17:11:57 I/ws adapter: >>> [ws adapter] is listening at ws://0.0.0.0:8085 2023-09-11 17:11:57 I/Mirai HTTP API: Http api server is running with verifyKey: ********* 2023-09-11 17:11:57 I/Mirai HTTP API: adaptors: [http,ws] 2023-09-11 17:11:57 I/Mirai HTTP API: ******************************************************** 2023-09-11 17:11:57 I/fix-protocol-version: protocol commands: info, load, fetch example: protocol info protocol load ANDROID_PHONE protocol fetch ANDROID_PAD 8.9.63 2023-09-11 17:11:57 I/fix-protocol-version: 当前各登录协议版本日期: ANDROID_PHONE 8.9.63.11390 2023-05-26T10:46:18+08:00 ANDROID_PAD 8.9.63.11390 2023-05-26T10:46:18+08:00 ANDROID_WATCH 2.0.8 2019-06-03T20:25:31+08:00 IPAD 8.9.50.611 2023-02-16T15:10:14+08:00 MACOS 6.8.2.21241 2022-03-14T11:11:35+08:00 2023-09-11 17:11:57 I/fix-protocol-version: 当前签名服务配置信息: v8.9.63 by fuqiuluo/unidbg-fetch-qsign from ********* 2023-09-11 17:11:57 I/MCL Addon: iTXTech MCL Version: 2.1.2-61c8bd8 2023-09-11 17:11:57 W/MCL Addon: iTXTech Soyuz 未安装,Soyuz MCL Handler 特性已禁用 2023-09-11 17:11:57 I/main: 3 plugin(s) enabled. 2023-09-11 17:11:57 I/main: Auto-login *********, protocol: ANDROID_PAD, heartbeatStrategy: STAT_HB 2023-09-11 17:11:57 W/EncryptService.alert: Encrypt service was loaded: KFCFactory(config=file:///root/KFCFactory.json) 2023-09-11 17:11:57 W/EncryptService.alert: All outgoing message may be leaked by this service. 2023-09-11 17:11:57 W/EncryptService.alert: Use this service if and only if you trusted this service and the service provider. 2023-09-11 17:11:57 W/EncryptService.alert: Service details: 2023-09-11 17:11:57 W/EncryptService.alert: `- Jvm Class: class xyz.cssxsh.mirai.tool.KFCFactory 2023-09-11 17:11:57 W/EncryptService.alert: `- ClassLoader: JvmPluginClassLoader{fix-protocol-version-1.11.0.mirai2.jar} 2023-09-11 17:11:57 W/EncryptService.alert: `- Source: file:/root/plugins/fix-protocol-version-1.11.0.mirai2.jar 2023-09-11 17:11:57 W/EncryptService.alert: `- Protected Domain: ProtectionDomain (file:/root/plugins/fix-protocol-version-1.11.0.mirai2.jar <no signer certificates>) JvmPluginClassLoader{fix-protocol-version-1.11.0.mirai2.jar} <no principals> java.security.Permissions@7cec3975 ( ("java.io.FilePermission" "/root/plugins/fix-protocol-version-1.11.0.mirai2.jar" "read") ) 2023-09-11 17:11:57 I/KFCFactory: ANDROID_PAD(8.9.63) EncryptService by fuqiuluo/unidbg-fetch-qsign from file:///root/KFCFactory.json 2023-09-11 17:11:57 I/KFCFactory: unidbg-fetch-qsign by ********* about { "code": 0, "msg": "IAA 云天明 章北海", "data": { "version": "1.1.9", "protocol": { "qua": "V1_AND_SQ_8.9.63_4194_YYB_D", "version": "8.9.63", "code": "4194" } } } 2023-09-11 17:11:58 I/UnidbgFetchQsign: Bot(*********) initialize by ********* 2023-09-11 17:12:06 I/UnidbgFetchQsign: Bot(*********) register, Instance loaded successfully. 2023-09-11 17:12:06 I/UnidbgFetchQsign: Bot(*********) initialize complete 2023-09-11 17:12:10 E/main: net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.login(SsoProcessor.kt:263) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$StateConnecting$startState$2.invokeSuspend(CommonNetworkHandler.kt:247) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664) Suppressed: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(*********), code=45, title=禁止登录, message=你当前使用的QQ版本过低,请前往QQ官网im.qq.com下载最新版QQ后重试。, errorInfo=) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:490) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) ... 5 more Caused by: [CIRCULAR REFERENCE: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(*********), code=45, title=禁止登录, message=你当前使用的QQ版本过低,请前往QQ官网im.qq.com下载最新版QQ后重试。, errorInfo=)] 2023-09-11 17:12:10 V/Bot.1701008067: Event: net.mamoe.mirai.console.events.AutoLoginEvent$Failure@6d5de79a 2023-09-11 17:12:10 I/main: mirai-console started successfully. 2023-09-11 17:12:12 W/UnidbgFetchQsign: with CoroutineName(SendMessage) java.lang.RuntimeException: Bot(1701008067) callback trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish at fix-protocol-version-1.11.0.mirai2.jar//xyz.cssxsh.mirai.tool.UnidbgFetchQsign$callback$1.invokeSuspend(UnidbgFetchQsign.kt:236) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664) Caused by: java.util.concurrent.CancellationException: net.mamoe.mirai.internal.network.components.LoginFailedExceptionAsNetworkException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. at net.mamoe.mirai.internal.network.handler.selector.SelectorNetworkHandler.sendAndExpect$suspendImpl(SelectorNetworkHandler.kt:157) at net.mamoe.mirai.internal.network.handler.selector.SelectorNetworkHandler.sendAndExpect(SelectorNetworkHandler.kt) at net.mamoe.mirai.internal.network.handler.NetworkHandler.sendAndExpect$default(NetworkHandler.kt:194) at net.mamoe.mirai.internal.network.protocol.packet.OutgoingPacketKt$createChannelProxy$1.sendMessage(OutgoingPacket.kt:328) at fix-protocol-version-1.11.0.mirai2.jar//xyz.cssxsh.mirai.tool.UnidbgFetchQsign$callback$1.invokeSuspend(UnidbgFetchQsign.kt:229) ... 6 more Caused by: net.mamoe.mirai.internal.network.components.LoginFailedExceptionAsNetworkException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$StateConnecting$startState$2.invokeSuspend(CommonNetworkHandler.kt:249) ... 6 more Suppressed: net.mamoe.mirai.internal.network.handler.selector.SelectorRequireReconnectException Caused by: net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.login(SsoProcessor.kt:263) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$StateConnecting$startState$2.invokeSuspend(CommonNetworkHandler.kt:247) ... 6 more Suppressed: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(*********), code=45, title=禁止登录, message=你当前使用的QQ版本过低,请前往QQ官网im.qq.com下载最新版QQ后重试。, errorInfo=) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:490) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) ... 5 more Caused by: [CIRCULAR REFERENCE: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(*********), code=45, title=禁止登录, message=你当前使用的QQ版本过低,请前往QQ官网im.qq.com下载最新版QQ后重试。, errorInfo=)] 2023-09-11 17:12:12 I/UnidbgFetchQsign: Bot(*********) destroy, Instance destroyed successfully. 2023-09-11 17:12:12 I/Bot.*********: Bot cancelled: Bot closed
-
RE: 调用mirai-http-api发送群消息,mirai的日志里显示发送了,但是群里没有消息
日志里相关的只有这么多,其他的都是其他的消息记录,没有报错信息,配置文件里的
debug: true
开了 -
调用mirai-http-api发送群消息,mirai的日志里显示发送了,但是群里没有消息
另外经过测试,复现条件为发送的消息当大于100个字符,并且消息中出现一定比例曾经经常的字符,就会发不出去。
请求详情,
mirai-http日志2023-02-02 18:41:24 V/Bot.***: Group(***) <- 咱可以帮你做这些事!查看详情发送(帮助 [指令])\n1.推荐: 推荐,自荐,tj,zj\n2.删除推荐: 移除推荐,移除自荐\n3.关注: 关注,s.gz\n4.日程表: 日程表,rc\n5.找图: 找图,zt\n6.翻译: 翻译,fy\n7.不色: bs,不色\n8.撤回: 撤回,ch\n9.新视频: 新视频,nv\n10.tag: tag\n11.对话: 对话\n12.mcp: mcp,mcpd,mcm,mcl,在线人数,在线玩家\n13.色图: 色图,st,ss,色色\n14.puser: puser\n15.pid: pid\n16.关注推特: 关注推特\n17.推特token: 推特token,tttoken\n18.重启: 重启,cq\n19.推荐色图: 推荐色图,tjst,好,不,推荐不色,推荐色色,tjss,tjbs\n20.关注b博: 关注b博\n21.翻译替换: 翻译替换,fyth\n22.推特原文: 推特原文,ttyw\n23.找本子: 找本子,zbz\n24.夸夸我: 夸夸我,kkw,夸夸他,kkt,骂骂我,mmw\n25.相似推荐: 相似推荐,xstj\n26.收藏色图: 收藏色图,scst\n27.24点: 玩24点,回答24点,放弃24点,w24,hd24,fq24\n28.签到: 签到,qd,积分排行,jfph,积分查询,jfcx\n29.什么时候: 什么时候,when,还有多久\n30.买水果小游戏: 买水果小游戏,zb,进货,摆烂,孤注一掷,准备,退出,掀桌,jh,bl,gzyz,分家,fj,投降,tx,桌面\n31.转发制作: 转发制作\n32.商店: 兑换,回收,背包,道具,使用\n33.钓鱼: 收杆,抛杆,收竿,抛竿,鱼呢,钓鱼榜,乐观榜\n34.百度: 百度\n35.文本图片: 文本图片\n36.藏头诗: 藏头诗五言,藏头诗,藏头诗七言,藏尾诗五言,藏尾诗七言,藏尾诗\n37.牛子: 比划比划,天榜,地榜,杀,男蛮入侵,领取牛牛,我的牛牛,我牛牛呢,赎回牛牛,撅斗\n38.地图: 前往\n39.好感度: \n40.聊天: \n
-
关于mirai-http-api的未bind的session的问题
mirai-http-api的verify得到的session如果没bind和release,文档里说是一定时间后将会被自动释放,这个时间是多久,可以自定义吗,如果开启了websocket,bind的session就不会自动释放了,那没bind的呢
-
使用mirai-http时遇到的关于messageId的问题
我现在的场景是将mirai和mirai-http作为一个独立的模块部署在docker中,其他模块通过通过http与mirai通信。
我会把通过websocket收到的每一条消息存入记录表,以供回复消息的场景使用。
如果我重新打包部署mirai,那么mirai的缓存消息将会清空,这导致新生成的messageId可能会和已经清理掉的缓存消息的messageId重复。(推测的重复原因)
希望生成新的messageId的时候,加入时间戳参数,使mirai即使重新打包部署也能不出现重复的messageId。:P -
RE: mirai-http-api启动时报错
@sxaaaaaaaaaaaa
./mcl --update-package net.mamoe:mirai-console --channel stable --version 2.5.0
调整mirai-console版本至2.5.0,或者你可以尝试升级至http-api 2.x