rhwong / qsign-onekey Goto Github PK

View Code? Open in Web Editor NEW

622.0 5.0 81.0 53.02 MB

Quickly start the Qsign service on Windows

Home Page: https://qsign.dev

Batchfile 100.00%

onekey

qsign-onekey's Introduction

qsign-onekey

本项目用于一键启动qsign

请自行将qsign内容文件和go-cqhttp放到同级别文件夹，脚本会自行读取

✨安装说明

请直接点击 Code - Download ZIP 下载本项目，直接解压缩到任意不包含中文和空格的路径中。

然后将qsign内容文件和go-cqhttp放到同级别文件夹，脚本会自行读取。

文件目录结构如下

└─ qsign-onekey-1.1.9-bitterest
     └─bin
     └─jre
     └─lib
     └─txlib
         └─8.9.70
         └─8.9.80
         └─8.9.85
         └─8.9.88
         └─...
     └─README.md
     └─go-cqhttp.bat
     └─go-cqhttp.exe
     └─Start_Qsign.bat

✨使用方法

如何使用go-cqhttp联动运行

首先，运行 go-cqhttp.bat，按照提示生成 config.yml 。
双击 Start_Qsign.bat 启动Qsign Deamon窗口，按照提示依次键入 txlib_version 参数、设定host、port、key的值。 (👈如果不知道这些是干什么的，请直接依次按下Enter）
如果脚本检测到 config.yml 尚未设定账号和密码，那么会提示你输入账号(Account uin)和密码(password)，输入后会同步进 config.yml 。
输入完成后，会启动Core窗口，用于启动Qsign Core窗口
在启动完成后，qsign会告诉您当前运行api的地址，如果您没设定过host和key，那么默认是 http://127.0.0.1:13579。key已经在开始时设定过，如果您没设定，那么默认是 1145141919810。(👈这些东西会自动写入到 config.yml ）
切勿关闭启动完成后的两个窗口，Qsign Deamon窗口用于监测Qsign Core是否存活，若探活失败将按照pid结束进程并重启Core。
如果日后需要修改 txlib_version 的版本，您可以删除文件夹根目录下的 txlib_version.json 来重新进入设定流程，不建议对此文件进行修改。

✨免责声明

本仓库代码仅供学习参考，用于自动化程序的启动，并无任何侵权内容。

Stargazers over time

qsign-onekey's People

Contributors

Stargazers

Watchers

Forkers

shiabox schwi-xgh matsumotomorami skilittle vincentlin7 miodesuyo begonia1005 fansirsqi 448808614 qinqinqiny alading241 lollipopgeneral qiuranqaq mirkiss zsanjin-p zzz66686 yhh1679 logiest617 benson80 mengniu8 laffylaffyla cutesatou chaichaisi wuyaiii iris7656 whitebearovo youbai520 horizonchaser fightingaction quartzkun super-moe siyue2001 761100192 shuaibibobo tontonnow xhz-txdy lovely-fafa bf179 cangce x-dr daishengsheng kimigaiiwuyi orisland issierhm dear-dee zpluto0705 sbzlzh xh-qiqi bianyuan456 evayo kagangtuya-star flakowesh sanjinbot kxdzzi ab-royo lqa1029 kcn3388 cexer l17eca7 zack-sys hhu233 zlove7i lc12345 amazefcc233 homuralan deliay youqi-0v0 shengwang52005 yuanxi953 iwasakiyouko rabbitfairy wyzmgmdg hw10181913 teriyakisushi soloxiaoye2022 viis233 rxmm49 qte123 crackercat heathzhang35 tenming

qsign-onekey's Issues

当前txlib/8.9.80/android_pad.json里面提供的app_id和sub_app_id有误

截至2023年10月16日13:06:44，txlib8.9.80的android_phone.json和android_pad.json里面的app_id和sub_app_id都是相同的，
这会导致即便在gocq里面选择了android_pad协议登录，但最终登录的协议始终会是android_phone，希望能够修复。

qsign在消息量超过两条每秒时频繁崩溃

8.9.85及以上任何协议版本消息发送稍微快一点qsign会直接崩溃，并且gocq抛出报错
运行在本地机器上 32g内存理论上来说不应该是性能问题
qsign崩溃前抛出日志

Program: D:\aila\new\jre\bin\java.exe
File: C:/msys32/home/Administrator/git/unicorn/qemu/memory.c, Line 1329

Expression: subregion->container == mr
Assertion failed!

Program: D:\aila\new\jre\bin\java.exe
File: qom/object.c, Line 707

Expression: obj->ref > 0

在win11电脑上无法启动

以下是我的操作步骤，不知道是不是我忽略了什么？用的是截至2023/7/31中午12点最新的main分支。

Qsgin异常重启

在Qsgin签名的时候可能会卡死一小会，但此时端口仍旧占用，导致守护进程误以为Qsgin死机了重启新的，但是无法关闭原先的进程，新启动的Qsgin会因为端口占用的问题立马报错而退出（大概是这样）。但是过一会原来的Qsgin就恢复了，没什么影响，就是在登陆的时候弹窗很烦……可不可以修复一下，改善一下守护进程检测的逻辑（？）

【bug】运行久了，cmd那边会卡死未响应，powershell会一直重复创建cmd

有时崩溃后不能正常重启，而是一直卡在了如下图所示的弹窗页面

以下为运行环境信息：
服务器配置：4C4G
操作系统：Windows Server 2012 R2 DataCenter 64bitCN
qsign-onekey版本：1.19b6(2023-12-19)
使用的协议版本：8.9.83
其他说明：如果大佬需要更多信息或协助，也可以让我进行提供

可能与问题 #58 有关联，因为每次连续发送两条消息时，出现上图所示情况的概率会大幅度增加，不过问题 #58 里面没有提到会卡住的问题。

BUG?

    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign(QQSecuritySign.kt:56)
    at com.tencent.mobileqq.sign.QQSecuritySign.getSign$default(QQSecuritySign.kt:51)
    at moe.fuqiuluo.api.QsignKt.requestSign(qsign.kt:92)
    at moe.fuqiuluo.api.QsignKt.access$requestSign(qsign.kt:1)
    at moe.fuqiuluo.api.QsignKt$sign$2.invokeSuspend(qsign.kt:45)
    at moe.fuqiuluo.api.QsignKt$sign$2.invoke(qsign.kt)
    at moe.fuqiuluo.api.QsignKt$sign$2.invoke(qsign.kt)
    at io.ktor.server.routing.Route$buildPipeline$1$1.invokeSuspend(Route.kt:116)
    at io.ktor.server.routing.Route$buildPipeline$1$1.invoke(Route.kt)
    at io.ktor.server.routing.Route$buildPipeline$1$1.invoke(Route.kt)
    at io.ktor.util.pipeline.SuspendFunctionGun.loop(SuspendFunctionGun.kt:120)
    at io.ktor.util.pipeline.SuspendFunctionGun.proceed(SuspendFunctionGun.kt:78)
    at io.ktor.util.pipeline.SuspendFunctionGun.execute$ktor_utils(SuspendFunctionGun.kt:98)
    at io.ktor.util.pipeline.Pipeline.execute(Pipeline.kt:77)
    at io.ktor.server.routing.Routing$executeResult$$inlined$execute$1.invokeSuspend(Pipeline.kt:478)
    at io.ktor.server.routing.Routing$executeResult$$inlined$execute$1.invoke(Pipeline.kt)
    at io.ktor.server.routing.Routing$executeResult$$inlined$execute$1.invoke(Pipeline.kt)
    at io.ktor.util.debug.ContextUtilsKt.initContextInDebugMode(ContextUtils.kt:17)
    at io.ktor.server.routing.Routing.executeResult(Routing.kt:190)
    at io.ktor.server.routing.Routing.interceptor(Routing.kt:64)
    at io.ktor.server.routing.Routing$Plugin$install$1.invokeSuspend(Routing.kt:140)
    at io.ktor.server.routing.Routing$Plugin$install$1.invoke(Routing.kt)
    at io.ktor.server.routing.Routing$Plugin$install$1.invoke(Routing.kt)
    at io.ktor.util.pipeline.SuspendFunctionGun.loop(SuspendFunctionGun.kt:120)
    at io.ktor.util.pipeline.SuspendFunctionGun.proceed(SuspendFunctionGun.kt:78)
    at io.ktor.server.engine.BaseApplicationEngineKt$installDefaultTransformationChecker$1.invokeSuspend(BaseApplicationEngine.kt:124)
    at io.ktor.server.engine.BaseApplicationEngineKt$installDefaultTransformationChecker$1.invoke(BaseApplicationEngine.kt)
    at io.ktor.server.engine.BaseApplicationEngineKt$installDefaultTransformationChecker$1.invoke(BaseApplicationEngine.kt)
    at io.ktor.util.pipeline.SuspendFunctionGun.loop(SuspendFunctionGun.kt:120)
    at io.ktor.util.pipeline.SuspendFunctionGun.proceed(SuspendFunctionGun.kt:78)
    at io.ktor.server.application.hooks.CallFailed$install$1$1.invokeSuspend(CommonHooks.kt:45)
    at io.ktor.server.application.hooks.CallFailed$install$1$1.invoke(CommonHooks.kt)
    at io.ktor.server.application.hooks.CallFailed$install$1$1.invoke(CommonHooks.kt)
    at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:78)
    at kotlinx.coroutines.CoroutineScopeKt.coroutineScope(CoroutineScope.kt:264)
    at io.ktor.server.application.hooks.CallFailed$install$1.invokeSuspend(CommonHooks.kt:44)
    at io.ktor.server.application.hooks.CallFailed$install$1.invoke(CommonHooks.kt)
    at io.ktor.server.application.hooks.CallFailed$install$1.invoke(CommonHooks.kt)
    at io.ktor.util.pipeline.SuspendFunctionGun.loop(SuspendFunctionGun.kt:120)
    at io.ktor.util.pipeline.SuspendFunctionGun.proceed(SuspendFunctionGun.kt:78)
    at io.ktor.util.pipeline.SuspendFunctionGun.execute$ktor_utils(SuspendFunctionGun.kt:98)
    at io.ktor.util.pipeline.Pipeline.execute(Pipeline.kt:77)
    at io.ktor.server.engine.DefaultEnginePipelineKt$defaultEnginePipeline$1$invokeSuspend$$inlined$execute$1.invokeSuspend(Pipeline.kt:478)
    at io.ktor.server.engine.DefaultEnginePipelineKt$defaultEnginePipeline$1$invokeSuspend$$inlined$execute$1.invoke(Pipeline.kt)
    at io.ktor.server.engine.DefaultEnginePipelineKt$defaultEnginePipeline$1$invokeSuspend$$inlined$execute$1.invoke(Pipeline.kt)
    at io.ktor.util.debug.ContextUtilsKt.initContextInDebugMode(ContextUtils.kt:17)
    at io.ktor.server.engine.DefaultEnginePipelineKt$defaultEnginePipeline$1.invokeSuspend(DefaultEnginePipeline.kt:118)
    at io.ktor.server.engine.DefaultEnginePipelineKt$defaultEnginePipeline$1.invoke(DefaultEnginePipeline.kt)
    at io.ktor.server.engine.DefaultEnginePipelineKt$defaultEnginePipeline$1.invoke(DefaultEnginePipeline.kt)
    at io.ktor.util.pipeline.SuspendFunctionGun.loop(SuspendFunctionGun.kt:120)
    at io.ktor.util.pipeline.SuspendFunctionGun.proceed(SuspendFunctionGun.kt:78)
    at io.ktor.util.pipeline.SuspendFunctionGun.execute$ktor_utils(SuspendFunctionGun.kt:98)
    at io.ktor.util.pipeline.Pipeline.execute(Pipeline.kt:77)
    at io.ktor.server.netty.NettyApplicationCallHandler$handleRequest$1$invokeSuspend$$inlined$execute$1.invokeSuspend(Pipeline.kt:478)
    at io.ktor.server.netty.NettyApplicationCallHandler$handleRequest$1$invokeSuspend$$inlined$execute$1.invoke(Pipeline.kt)
    at io.ktor.server.netty.NettyApplicationCallHandler$handleRequest$1$invokeSuspend$$inlined$execute$1.invoke(Pipeline.kt)
    at io.ktor.util.debug.ContextUtilsKt.initContextInDebugMode(ContextUtils.kt:17)
    at io.ktor.server.netty.NettyApplicationCallHandler$handleRequest$1.invokeSuspend(NettyApplicationCallHandler.kt:119)
    at io.ktor.server.netty.NettyApplicationCallHandler$handleRequest$1.invoke(NettyApplicationCallHandler.kt)
    at io.ktor.server.netty.NettyApplicationCallHandler$handleRequest$1.invoke(NettyApplicationCallHandler.kt)
    at kotlinx.coroutines.intrinsics.UndispatchedKt.startCoroutineUndispatched(Undispatched.kt:44)
    at kotlinx.coroutines.CoroutineStart.invoke(CoroutineStart.kt:112)
    at kotlinx.coroutines.AbstractCoroutine.start(AbstractCoroutine.kt:126)
    at kotlinx.coroutines.BuildersKt__Builders_commonKt.launch(Builders.common.kt:56)
    at kotlinx.coroutines.BuildersKt.launch(Unknown Source)
    at io.ktor.server.netty.NettyApplicationCallHandler.handleRequest(NettyApplicationCallHandler.kt:37)
    at io.ktor.server.netty.NettyApplicationCallHandler.channelRead(NettyApplicationCallHandler.kt:29)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
    at io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:61)
    at io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:425)
    at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174)
    at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167)
    at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
    at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
    at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
    at io.ktor.server.netty.EventLoopGroupProxy$Companion.create$lambda$1$lambda$0(NettyApplicationEngine.kt:296)
    at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
    at java.base/java.lang.Thread.run(Unknown Source)

Caused by: unicorn.UnicornException: No memory available or memory not present (UC_ERR_NOMEM)
at unicorn.Unicorn.mem_map(Native Method)
at com.github.unidbg.arm.backend.UnicornBackend.mem_map(UnicornBackend.java:134)
... 432 more

10月 14, 2023 2:06:10 下午 com.github.unidbg.AbstractEmulator handleEmuException
警告: emulate RX@0x4016d504[libfekit.so]0x16d504 exception sp=unidbg@0xbfffcc70, msg=mem_map address=0x41400000, size=402653184, perms=0x3, offset=58ms
[FEKit_]info: qq_sign.h:156 [GetSign] cmd:wtlogin.login

cqhttp登录账号后闪退

qsign版本：1.1.9
qsign qq版本：8.9.68
go cqhttp版本：从此项目下载，下载时间：20230826,从Release下载名称：unidbg-fetch-qsign-onekey-1.1.9-go-cqhttp-x86.zip
go cqhttp qq设备版本：8.9.68
qsign日志：
[FEKit_]info: qq_sign.h:142 [GetSign] cmd:wtlogin.exchange_emp
FEBound.transform(111a0103000000000200030000ea0b0b8996d62ebcd45715f6e842efa8fd2cecac000000004865726f) => a15955f1a8520da7560dbb530da56009b381ab65c1b98b7b3e65300c9e44ef837ba752fda80deed54b
[FEKit_]info: qq_sign.h:142 [GetSign] cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish
FEBound.transform(3444e84777d0e7f5c5f501030000000002000300008250500fedab7964e9d356fd000000004865726f) => 4e93c87e17b21b2bd3fabd560db8630dfda759fda81c8d675b69d5fd33ac342b82a752fda80deed54b
[FEKit_]info: ChannelManager.cpp:98 origin cmd:GetSecConf ,cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish
[FEKit_]error: ChannelManager.cpp:101 [ChannelManager:OnReceive] success:1 cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish bcmd:GetSecConf
[FEKit_]info: task_handle.h:76 TaskSystem not allow
[FEKit_]info: task_handle.h:76 TaskSystem not allow
[FEKit_]info: qq_sign.h:142 [GetSign] cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish
FEBound.transform(3062e852b2d0867d7df70103000000000000030000aff0a030ea9c536032f5c5f5000000004865726f) => 4c72c820c4b257d1fff0bd560db8630dfca759fda89e6d37c2669e663d5d087489a752fda80deed54b
[FEKit_]info: ChannelManager.cpp:98 origin cmd:O3GetTail ,cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish
[FEKit_]error: ChannelManager.cpp:101 [ChannelManager:OnReceive] success:1 cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish bcmd:O3GetTail
[FEKit_]info: task_handle.h:76 TaskSystem not allow
[FEKit_]error: sign_tail_manager.h:79 get tail success 1, retCode 0
FEBound.transform(fb64dea6bfa11285e5d20115904289fd2eb16843ffdc2a73ca7975673e641c31) => 8773a634cb97b0eb7387bd352d3d9a9cd0fb78714bb092ddd4e2511ef2672fe5
[FEKit_]error: ChannelManager.cpp:73 o3cm@S: O3ReportTail, trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Access
uin = 1186431337, id = 3, sendPacket(cmd = trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Access, data = 0a0c4f335265706f72745461696c1222a8bb8a1d95d65a17e09c2bdeb835d18c15c41509610feac33ed6c21c9c54173e00871a20ec85f89f612ba042967ff7284e9251c480a0649ae672b46793bbc8eb56b34054)
[FEKit_]info: qq_sign.h:142 [GetSign] cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish
FEBound.transform(408b45cb6c8a8d64ca1c58d6d68e28e8a0680103000000000000030000e85a21280000000029d0c774) => 0cb64f13f1165894d4ce0aea5a19eb8e7c7055f1a8520da7520dbb530dab1c65d5a752fda8cb2dbaf1
[FEKit_]info: qq_sign.h:142 [GetSign] cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Access
FEBound.transform(42837b0d4e56ba6877dc0103000000000000030000e2fdddfd49e3e3c7e85ea5680000000029d0c774) => 0dbe84f99924f298fa8ebd560db8630dfca759fda88c68c13fa2cb06d0ab16a435a752fda8cb2dbaf1
[FEKit_]info: ChannelManager.cpp:98 origin cmd:getToken ,cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish
[FEKit_]error: ChannelManager.cpp:101 [ChannelManager:OnReceive] success:1 cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish bcmd:getToken
[FEKit_]info: task_handle.h:76 TaskSystem not allow
[FEKit_]info: device_token.h:274 response len :20
[FEKit_]info: device_token.h:297 DeviceToken::saveToken ok! expireTime:1693209356

go cqhttp info日志
[2023-08-27 16:01:52] [INFO]: submit sign: uin=1186431337, cmd=trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish, callbackID=0, buffer=[10 135 2 227 175 135 71 94 195 252 41 169 153 115 29 163 207 162 126 184 19 95 19 93 43 94 169 147 168 60 227 171 112 117 63 141 64 66 104 45 104 88 111 157 209 139 95 50 131 217 29 201 96 140 168 18 88 21 46 111 237 73 51 69]...
[2023-08-27 16:01:53] [INFO]: submit sign: uin=1186431337, cmd=trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish, callbackID=1, buffer=[10 134 1 75 172 95 40 69 220 207 235 2 128 83 153 159 64 94 12 32 42 100 29 164 14 47 213 178 189 195 26 235 217 180 157 121 195 132 20 201 166 48 100 109 114 82 146 7 139 52 139 7 133 170 3 26 29 46 239 77 27 212 138 52]...
[2023-08-27 16:01:53] [INFO]: submit sign: uin=1186431337, cmd=trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish, callbackID=2, buffer=[10 148 1 176 134 229 130 51 0 113 121 204 244 127 188 140 154 237 111 227 62 172 28 207 59 47 210 177 133 153 5 68 166 32 14 82 180 245 177 250 107 183 157 7 161 254 31 78 150 225 253 143 40 136 135 70 5 238 216 47 252 77 63 44]...

windows2012 登录错误

windows 2012 腾讯云不知道什么错误

可否添加中文日志

有时候英文日志太复杂看起来很麻烦还要翻译，是否可以添加以下中文版本的日志

怎么在linux下部署？

怎么在linux下部署？
小白不是很懂

关于go-cqhttp崩溃

嗯，就是，能不能加个对于gocq的进程守护，我这qsign崩溃后gocq也跟着崩溃

运行后core报错无限重启

Qsign API:http://127.0.0.1:13579
KEY=1145141919810
Qsign_version:2023-12-19
TXlib_version:8.9.90
--------------------------------------------------------------------------------
-----------------
Check if the curl command is installed in the environment variables...
The curl command is not detected, use the "curl.exe" from the lib folder.This pr
ecompiled executable works only on x86 architecture systems.
Qsign API is not running, Restarting...
Qsign API running on processes with PID:1428.
Qsign API is not running, Restarting...
Qsign API running on processes with PID:1428.
Qsign API is not running, Restarting...
Qsign API running on processes with PID:1428.
Qsign API is not running, Restarting...
Qsign API running on processes with PID:1428.
Qsign API is not running, Restarting...

Qsign API running on processes with PID:1428.
Qsign API is not running, Restarting...

这两条是同时出现的运行的同时判断未启动导致的重启?

core的报错:
我也不知道哪个端口被占用了

Exception in thread "main" java.net.BindException: Address already in use: bind
       at java.base/sun.nio.ch.Net.bind0(Native Method)
       at java.base/sun.nio.ch.Net.bind(Unknown Source)
       at java.base/sun.nio.ch.Net.bind(Unknown Source)
       at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
       at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSo
ketChannel.java:141)
       at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.
ava:562)
       at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChann
lPipeline.java:1334)
       at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractCha
nelHandlerContext.java:600)
       at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHa
dlerContext.java:579)
       at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.j
va:973)
       at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:260)
       at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:356

       at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventE
ecutor.java:174)
       at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEv
ntExecutor.java:167)
       at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(Single
hreadEventExecutor.java:470)
       at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
       at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThread
ventExecutor.java:997)
       at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java
74)
       at io.ktor.server.netty.EventLoopGroupProxy$Companion.create$lambda$1$la
bda$0(NettyApplicationEngine.kt:296)
       at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalR
nnable.java:30)
       at java.base/java.lang.Thread.run(Unknown Source)

登入失败

最新版本

同目录运行，
windows11
之前用1.1.0用了挺长时间了，然后给风控+登入失败就跟新了

是否可以加入自动更新

一个小小的建议
是否可以在项目中加入自动更新，这样子就可以不用每次都重新下载新的版本并覆盖到项目中。

QQ版本文件请求

佬，可以帮助提取一下8.9.75/8.9.76/8.9.78这三个版本的文件吗

关于配置docker时，一直restarting的问题

情况说明：

我想尝试一个linux服务器上QQ聊天bot；遇到腾子网络问题，需要qsign本地服务器签名。

按照https://zhuanlan.zhihu.com/p/648839865
提供的教程，我使用命令：
docker run -d --restart=always --name qsign -p 5709:8080 -e ANDROID_ID={android_id} xzhouqd/qsign:8.9.63
配置的qsign容器，出现一直restarting的情况。

查看docker logs发现提示：

于是我在docker外的本地环境中安装java且配置了JAVAHOME，rm容器重开一个仍未解决问题。

求佬指导

qsign天天异常关闭,这个事情有办法解决么,一关闭就导致收发不及时

腾讯作妖,
前几天我没断电之前一个月qsign一直没问题,
前天断电以后
qsign天天异常关闭,这个事情有办法解决么,一关闭就导致收发不及时
目前85.90协议都有这个问题

gocq更新1.2.0了。

持续报错后闪退

go cphttp重复提示刷新token错误

刷新 token 出现错误: code=-1, msg: QSign not initialized, unable to request_token, please submit the initialization package first.. server: http://127.0.0.1:13579

请问该项目使用的是什么开源协议，我能将它集成至我的项目里吗?

请问该项目使用的是什么开源协议，我能将它集成至我的项目里吗?
What open source license does the project use, and can I integrate it into my project?

我想做一个多协议集成的QQ机器人一键启动程序，以方便小白和开发者快速登录QQ机器人帐户并切换协议.
I want to make a multi-protocol integrated QQ robot one-click launcher, in order to facilitate Xiaobai and developers to quickly log in to QQ robot accounts and switch protocols.

现在缺少协议库，这是一个不错的项目。
Now the protocol library is missing, which is a nice project.

Thanks!

无限重启

一路回车，使用的是1.2.0版本的go-cqhttp。不停的有新窗口启动，但总是被秒关。

报错后迅速闪退

报错内容如图，由于报错后迅速闪退，我也不确定有没有别的报错

启动后会频繁跳出openJDK停止工作

qsign版本1.1.9bitterest，客户端版本是8.9.83和8.9.85，遇到过两种错误，姑且之前的版本全都不能用只有这俩能登陆，但是一登录就出问题，后一个错误还有好多errorlog

使用高等级的协议时会出现qsign卡死但启动脚本检测不到的情况

建议在启动脚本152行检测端口时加上超时
--connect-timeout 5 -m 5

qsign-onekey/Start_Qsign.bat

Line 152 in 85e3d7f

%curl_command% -I http://!host!:!port!/register?uin=12345678 >nul 2>nul

请考虑打包新的 releases

项目的启动脚本和Qsign都已经更新，但是releases却没有新的版本
所以请考虑打包新的 releases

预设txlib里没有8.9.80，用旧版本也可以吗？

手机qq版本是8.9.80，但预设txlib里没有，用8.9.73可以吗？

无法正常运行

我第一次启动的时候不小心×掉了另一个窗口导致现在一直卡死在一个进程怎么办？
unidbg-fetch-qsign-onekey Ver.2023-11-06 by rhwong shia kagangtuya-star
txlib_Version is 8.9.88
If you want to change txlib_version , please delete [txlib_version.json]

Sync protocol version to go-cqhttp data folder.
子目录或文件 data\versions 已经存在。
已复制 1 个文件。
已复制 1 个文件。

The [config.yml] already contains account information or not exist.
Skip account settings.

Qsign API:http://127.0.0.1:13579
KEY=1145141919810
Qsign_version:2023-11-06
TXlib_version:8.9.88

Check if the curl command is installed in the environment variables...
The curl command is detected, use the installed curl
Qsign API is not running, Restarting...
Qsign API running on processes with PID:.

签名api(energy)异常： 810_9 result(8ms): {"code":-1,"msg":"Request failed with status code 405"}

如何排查 405 错误？

输出log有

[FEKit_]info: qq_sign.h:142 [GetSign] cmd:wtlogin.login
9月 24, 2023 11:10:02 下午 moe.fuqiuluo.unidbg.env.FileResolver resolve
警告: Couldn't find file: /data/app/~~vbcRLwPxS0GyVfqT-nCYrQ==/com.tencent.mobileqq-xJKJPVp9lorkCgR_w5zhyA==/lib/arm64
FEBound.transform(33028c44f3460104000002000200030001479b5cf98cbca1df04eedeeff04555b5e89f274310ce67424e5f5feac7311931000000004865726f) => 44a23178420401a4520db05308b8640df198642f4310ff3ebb04c6e87b48f82429d06c6e9272749aa6a8026c7926a9f841a752fda80deed54b

处理ws命令时发生无法恢复的异常

这玩意部署完之后怎么让别人也用？

在服务器上部署了这个之后，试着用本地goc去用这个qsign，config里写的http://(云服务器的外网IP):13579。服务器的android_id和本地这个goc的android_id是一致的。

[bug]：dial tcp 127.0.0.1:13579: connectex: No connection could be made because the target machine actively refused it.

我使用windows server 2019进行搭建，并且选择了repo版的gocq。但是在bot被风控我再次重启gocq时发生了如下报错，并且在我重新安装了gocq与签名服务器之后仍然不行。请问这是什么原因呢？我感觉似乎是签名服务器的服务没有开启导致连接失败了。
报错截图如下：

1.1.6DEBUG

启动时候显示这个，是环境变量问题吗？
zulu19.32.13-ca-jdk19.0.2-win_x64

Qsign在GO-CQ登录过程中闪退（write file error）

如图所示
Qsign版本号：1.2.3.1
Android Pad QQ版本：8.9.83

jar文件通过winrar解压测试报告没发现问题，已经关闭了系统所有的杀毒软件/防火墙。

qsign无限重启

版本：qsign-2023-10-25，其中lib文件夹和start_qsign.bat 替换为了最新版本
如图，qsign-core正常运行，但qsign-deamon检测qsign-core没有运行，并无限重启qsign-core
令人费解的是，qsign-deamon和qsign-core 在本人的电脑上（win10）可以正常运行，但是在服务器（windows server2012 R2）上就会出现这种情况。

运行Start_Qsign.bat后，cmd窗口闪一下就没了

运行Start_Qsign.bat后，cmd窗口闪一下就没了。
下载了unidbg-fetch-qsign-onekey-1.1.6-go-cqhttp-x86.zip和unidbg-fetch-qsign-onekey-1.1.9-go-cqhttp-x86.zip。
这两个都是同样的问题。
解压运行Start_Qsign.bat，全部回车默认配置。cmd窗口闪一下就没了。

当 host 设为 0.0.0.0 时会无限重启 qsign-onekey-core

因为有远程连接的需求，所以把 host 设为了 0.0.0.0
当 host 设为 0.0.0.0 时会无限重启 qsign-onekey-core
Start_Qsign.bat 版本：2023-11-06

如何配置自动注册实例？

版本：1.1.9
cq日志：2023/10/8 20:24:34WARNING自动注册实例已关闭，请配置 sign-server 端自动注册实例以保持正常签名
2023/10/8 20:24:34INFO从文件 data/versions/1.json 读取协议版本 Android Phone 8.9.73.11945.
2023/10/8 20:24:34INFO自动刷新 token 已关闭，token 过期后获取签名时将不会立即尝试刷新获取新 token
2023/10/8 20:24:34WARNING定时刷新 token 已关闭

请问大佬一键后出现这种问题怎么办？

按照步骤启动bat后出现如下图情况，小白实在搞不清楚是什么问题。。。

【bug】error报错

环境：Windows 11
ICQQ 0.5.4
Qsign 1.1.9
txlib 8.9.80

运行时会一直出现以下error报错

[FEKit_]info: device_info.h:534 534
[FEKit_]info: device_info.h:536 536
[FEKit_]info: device_info.h:538 538
[FEKit_]info: device_token.h:276 begin pack
[FEKit_]info: device_token.h:278 pack buff result len:1412
[FEKit_]info: device_token.h:293 begin sendmessage : len :1412
[FEKit_]info: device_token.h:316 response len :0
[FEKit_]error: device_token.h:320 get token error! errorcode:907,mFailedTimes:5
[FEKit_]info: qq_sign.h:156 [GetSign] cmd:MessageSvc.PbSendMsg
FEBound.transform(22c4b4a4167801080001000102000100001e4617c08fa7a7cd1cf535594c3d1812000000004865726f) => ddc303386c3d01a85203b85708b8690dfc554bced81eab3adfce11a5153fadfeada752fda80deed54b
[FEKit_]error: sign_tail_manager.h:147 tryRequestTail
[FEKit_]error: sign_tail_manager.h:154 channel not ready
[FEKit_]info: qq_sign.h:156 [GetSign] cmd:MessageSvc.PbSendMsg
FEBound.transform(2660baa6e8b2a5940b0001080001000102000100006c8d09ea1db275249e3d3def000000004865726f) => d8770a3406acae845d0dbd510dbe6305fda755fda8e058a074c9f0f5c309adec9fa752fda80deed54b
[FEKit_]error: sign_tail_manager.h:147 tryRequestTail
[FEKit_]error: sign_tail_manager.h:154 channel not ready
[FEKit_]info: qq_sign.h:156 [GetSign] cmd:MessageSvc.PbSendMsg
FEBound.transform(460aee2783e6f6e7c44e70e44580ccabab030108000100010200010000a5a0eaa4000000004865726f) => 08a9c66e2284674ad1a85800b7184fa977ae55fba8570dae560dbd530dc3b3817ea752fda80deed54b
[FEKit_]info: qq_sign.h:156 [GetSign] cmd:MessageSvc.PbSendMsg
[FEKit_]error: sign_tail_manager.h:147 tryRequestTail
[FEKit_]error: sign_tail_manager.h:154 channel not ready
FEBound.transform(029c8b5b5beb0108000100010200010000a7b2ecbe80821300950e7c23e158b4c2000000004865726f) => fd8d3423308301a85203b85708b8690dfc38009fc912507d527ab6f2c6ae1bc2eda752fda80deed54b
[FEKit_]error: sign_tail_manager.h:147 tryRequestTail
[FEKit_]error: sign_tail_manager.h:154 channel not ready
[FEKit_]info: qq_sign.h:156 [GetSign] cmd:MessageSvc.PbSendMsg

有时候也会有
[FEKit_]info: ChannelManager.cpp:121 origin cmd:O3GetTail ,cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish
[FEKit_]error: ChannelManager.cpp:124 [ChannelManager:OnReceive] success:1 cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish bcmd:O3GetTail reason:0
[FEKit_]info: task_handle.h:77 TaskSystem not allow
[FEKit_]info: ChannelManager.cpp:121 origin cmd:GetSecConf ,cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish
[FEKit_]error: ChannelManager.cpp:124 [ChannelManager:OnReceive] success:1 cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish bcmd:GetSecConf reason:0
[FEKit_]info: task_handle.h:77 TaskSystem not allow
Assertion failed: obj->ref > 0, file qom/object.c, line 707

然后qsign就停止运行了，大概每隔几个小时复现一次

登录失败: 当前网络不稳定，登录失败。推荐使用常用设备或通过手机号登录。 Code: 237

[2023-09-13 10:41:08] [WARNING]: callback error: Packet timed out
[2023-09-13 10:41:08] [INFO]: submit sign: uin=1479981061, cmd=trpc.o3.ecdh_acce
ss.EcdhAccess.SsoSecureA2Establish, callbackID=0, buffer=[].
[2023-09-13 10:41:09] [ERROR]: Protocol -> parse incoming packet error: return c
ode unsuccessful: -10005
[2023-09-13 10:41:12] [WARNING]: 登录失败: 当前网络不稳定，登录失败。推荐使用常
用设备或通过手机号登录。 Code: 237
[2023-09-13 10:41:12] [WARNING]: 登录过于频繁, 请在手机QQ登录并根据提示完成认证
后等一段时间重试
[2023-09-13 10:41:12] [INFO]: 按 Enter 继续....
[2023-09-13 10:41:24] [WARNING]: callback error: Packet timed out
[2023-09-13 10:41:24] [INFO]: submit sign: uin=1479981061, cmd=trpc.o3.ecdh_acce
ss.EcdhAccess.SsoSecureA2Establish, callbackID=1, buffer=[].
[2023-09-13 10:41:25] [ERROR]: Protocol -> parse incoming packet error: return c
ode unsuccessful: -10005
[2023-09-13 10:41:26] [ERROR]: Protocol -> parse incoming packet error: return c
ode unsuccessful: -10005
[2023-09-13 10:41:40] [WARNING]: callback error: Packet timed out
[2023-09-13 10:41:40] [INFO]: submit sign: uin=1479981061, cmd=trpc.o3.ecdh_acce
ss.EcdhAccess.SsoSecureA2Establish, callbackID=2, buffer=[].
[2023-09-13 10:41:41] [WARNING]: callback error: Packet timed out
[2023-09-13 10:41:41] [INFO]: submit sign: uin=1479981061, cmd=trpc.o3.ecdh_acce
ss.EcdhAccess.SsoSecureA2Establish, callbackID=3, buffer=[].

在Windows2012下无法运行

会直接乱码，2008也是。
希望可以修正。

是否可以添加其它系统的适配？

请问，是否可以添加其它系统的适配，比如Liunx系统，大多数的服务器并非使用windows系统，而是Liunx或者其它系统，如果可以添加其它系统的适配，会让机器人在服务器的部署变得更加方便

error: sign_tail_manager.h tryRequestTail

在txlib=8.9.85 启动时，bot发送消息时出现类似于以下信息是否正常？

tryRequestTail
curStatus is x duration y

以下是一段1.2.0版本qsign+8.9.90txlib的报错，和119+8985大差不差
[FEKit_]info: qq_sign.h:157 [GetSign] cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish
[FEKit_]info: qq_sign.h:157 [GetSign] cmd:trpc.o3.ecdh_access.EcdhAccess.SsoSecureA2Establish
[FEKit_]info: qq_sign.h:157 [GetSign] cmd:MessageSvc.PbSendMsg
[FEKit_]error: sign_tail_manager.h:147 tryRequestTail
[FEKit_]error: sign_tail_manager.h:166 curStatus is 1 duration 11
[FEKit_]info: qq_sign.h:157 [GetSign] cmd:MessageSvc.PbSendMsg
[FEKit_]error: sign_tail_manager.h:147 tryRequestTail
[FEKit_]error: sign_tail_manager.h:166 curStatus is 1 duration 15
[FEKit_]info: qq_sign.h:157 [GetSign] cmd:MessageSvc.PbSendMsg
[FEKit_]error: sign_tail_manager.h:147 tryRequestTail
[FEKit_]error: sign_tail_manager.h:166 curStatus is 1 duration 17
[FEKit_]info: qq_sign.h:157 [GetSign] cmd:MessageSvc.PbSendMsg
[FEKit_]error: sign_tail_manager.h:147 tryRequestTail
[FEKit_]error: sign_tail_manager.h:166 curStatus is 1 duration 27

gocq可以正常发送消息，没有提示错误
我使用的是go-cq v1.2.0