版本2.1.2无法登录 code=235，希望能修复

8898c86e-a22b-4f2f-a2f8-f4a169db1ad7-image.png
请问这是怎么回事啊，又该怎么解决呢
在线求助！！！

机器人运行中，当我使用okhttp3进行http请求的时候，会出现机器人直接掉线的情况，请问有人知道是什么原因吗？偶尔出现。QQ截图20230320032144.png
错误信息：2023-03-20 02:46:33 V/Bot.3489291735: Event: BotOfflineEvent.Dropped(bot=Bot(3489291735), cause=HeartbeatFailedException: 3489291735.StatHeartbeat, recoverable=true, cause=PacketTimeoutException(message=3489291735.StatHeartbeat Scheduler: Timeout receiving action response, cause=kotlinx.coroutines.TimeoutCancellationException: Timed out waiting for 5000 ms), reconnect=true)
2023-03-20 02:46:33 W/Bot.3489291735: Connection lost, reconnecting... (HeartbeatFailedException: 3489291735.StatHeartbeat, recoverable=true, cause=PacketTimeoutException(message=3489291735.StatHeartbeat Scheduler: Timeout receiving action response, cause=kotlinx.coroutines.TimeoutCancellationException: Timed out waiting for 5000 ms))
2023-03-20 02:46:33 W/Bot.3489291735: An exception occurred when processing event. Subscriber scope: '<unnamed>'. Broadcaster scope: 'Bot 3489291735.EventDispatcher'
java.lang.IllegalStateException: NetworkHandler is already closed.
at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$StateClosed.sendPacketImpl(CommonNetworkHandler.kt:389)
at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler.sendPacketImpl(CommonNetworkHandler.kt:36)
at net.mamoe.mirai.internal.network.handler.NetworkHandlerSupport.sendAndExpect(NetworkHandlerSupport.kt:123)
at net.mamoe.mirai.internal.network.handler.NetworkHandlerSupport$sendAndExpect$1.invokeSuspend(NetworkHandlerSupport.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)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:233)
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: kotlinx.coroutines.TimeoutCancellationException: Timed out waiting for 5000 ms
at kotlinx.coroutines.TimeoutKt.TimeoutCancellationException(Timeout.kt:184)
at kotlinx.coroutines.TimeoutCoroutine.run(Timeout.kt:154)
at kotlinx.coroutines.EventLoopImplBase$DelayedRunnableTask.run(EventLoop.common.kt:508)
at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:284)
at kotlinx.coroutines.DefaultExecutor.run(DefaultExecutor.kt:108)
at java.base/java.lang.Thread.run(Unknown Source)
最后是一句2023-03-20 02:47:03 I/Bot.3489291735: Bot cancelled: Bot closed。
我看了下我的代码，QQ截图20230320032403.png
QQ截图20230320032421.png 大概率是到这个地方报错了。但是我也不确定是不是代码的问题，因为大部分时间都正常。我刚学kotlin不是很懂，麻烦大佬们看看。

17fd9a61-1eea-4eb9-8af4-074b4f2e0228-image.png
我总共下了这仨放进plugins里了
重启后status看不到下面俩
429321dd-7a2d-4dd7-8c3b-283278688043-image.png
config文件看了一下也没生成

/status
Running MiraiConsole v2.14.0, built on 2023-02-06 14:25:21.
Frontend Terminal: version 2.14.0, provided by Mamoe Technologies

Permission Service: Built In Permission Service

Plugins: Chat Command v0.6.0, fix-protocol-version v1.2.0, Jeff v1.0, mirai-login-solver-sakura v0.0.9, MiraiNative v2.0.5-cp, indi.eiriksgata.rulateday-dice v0.0.1, MCL Addon v2.1.1

Object Pending Finalization Count: 0
committed | init | used | max
Heap Memory: 97.0MB | 64.0MB | 40.34MB | 1.0GB
Non-Heap Memory: 94.75MB | 7.31MB | 92.34MB | -1

根据控制台和status报告的信息插件应该已经加载了，但无法使用。
使用了2.1.2版本的MCL，安装了cwyu的猫娘gpt、jeff笑话和Eiriksgata /
mirai-rulateday-dice 插件。猫娘gpt和jeff笑话能正常使用，但dice插件按照预设用法无法得到回应。
插件放置在主目录下的plugins文件夹里，文件名称是rulateday-server-pro-0.4.8-SNAPSHOT-jar-with-dependencies.jar

5b52d425-e782-4026-928f-d5576a8a3781-image.png

禁止登录 code＝238 请使用手q扫码登录或短信验证

现在不管使用什么登录协议（WATCH或者PHONE）都没有办法登录了，登录显示235（要求更新版本）或者238（要求手机号短信登录）错误
之前也有过这样的情况，解决方案是直接把deviceInfo删除，随机刷一个新的设备信息出来，然后再登录，会提示新设备登录短信验证，通过之后就能登录了
但今天开始，这个最后的办法也不行了，就算换了新的deviceInfo也没有办法登录，不管怎么修改都不行

建议：
目前腾讯QQ是把短信登录作为最高登录权重的，不管什么情况下的风控，短信登录都可以解除。所以考虑直接开发一下 短信登录 吧。好像只有这一个办法了

另外吐一吐苦水：
只能说腾讯是真的恶心哦，其他通讯软件比如Discord都是故意容许用户去做一些自动化Bot的，唯独马化腾这个，百般阻挠登录，各种风控，仗着自己是国民软件用户多就为所欲为了

"pool-6-thread-18" #60 prio=5 os_prio=0 tid=0x00007f2d1803e800 nid=0x3ef02d runnable [0x00007f2d109e7000] java.lang.Thread.State: RUNNABLE at net.mamoe.mirai.internal.contact.CommonGroupImpl.get(GroupImpl.kt:210) at net.mamoe.mirai.internal.contact.CommonGroupImpl.get(GroupImpl.kt:135) at com.king.api.messageapis.group.MessageRank.sendRank(MessageRank.java:71) at com.king.api.messageapis.group.MessageRank.sendRank(MessageRank.java:50) at com.king.api.messageapis.group.MessageRank.handler(MessageRank.java:45) at com.king.api.messageapis.GroupMessageApiGroup.lambda$handler$0(GroupMessageApiGroup.java:65) at com.king.api.messageapis.GroupMessageApiGroup$$Lambda$875/1976446850.run(Unknown Source) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:750) "pool-6-thread-30" #74 prio=5 os_prio=0 tid=0x00007fc8f4053800 nid=0xc4be in Object.wait() [0x00007fc8e9de2000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000e210de80> (a me.him188.kotlin.jvm.blocking.bridge.internal.RunSuspend) at java.lang.Object.wait(Object.java:502) at me.him188.kotlin.jvm.blocking.bridge.internal.RunSuspend.await(RunSuspend.kt:38) - locked <0x00000000e210de80> (a me.him188.kotlin.jvm.blocking.bridge.internal.RunSuspend) at me.him188.kotlin.jvm.blocking.bridge.internal.RunSuspendKt.$runSuspend$(RunSuspend.kt:19) at net.mamoe.mirai.contact.Contact$Companion.uploadImage(Contact.kt) at net.mamoe.mirai.contact.Contact$Companion.uploadImage$default(Contact.kt:155) at net.mamoe.mirai.contact.Contact$Companion.uploadImage(Contact.kt) at net.mamoe.mirai.contact.Contact.uploadImage(Contact.kt) at com.king.api.messageapis.group.MessageRank.sendRank(MessageRank.java:91) at com.king.api.messageapis.group.MessageRank.sendRank(MessageRank.java:54) at com.king.api.messageapis.group.MessageRank.handler(MessageRank.java:49) at com.king.api.messageapis.GroupMessageApiGroup.lambda$handler$0(GroupMessageApiGroup.java:65) at com.king.api.messageapis.GroupMessageApiGroup$$Lambda$878/1694548510.run(Unknown Source) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:750)

以上是线程被阻塞时的一些信息，重启应用后又恢复正常了，不太清楚这是不是风控导致的。
还有就是最近发现同一批被设置的群成员特殊头衔部分获取不到，包括设置头衔的事件也收不到。不确定是不是qq没有及时更新那部分信息导致的

在Debian系统的服务器上运行bot几个小时后会出现HeartbeatFailedException然后自动下线。已经出现两次了。

2023-03-05 14:57:16 V/Bot.[qq号]: [发送者] -> Test 2023-03-05 23:44:05 V/Bot.[qq号]: Event: BotOfflineEvent.Dropped(bot=Bot([qq号]), cause=HeartbeatFailedException: [qq号].AliveHeartbeat, recoverable=true, cause=PacketTimeoutException(message=[qq号].AliveHeartbeat Scheduler: Timeout receiving action response, cause=kotlinx.coroutines.TimeoutCancellationException: Timed out waiting for 5000 ms), reconnect=true) 2023-03-05 23:44:05 W/Bot.[qq号]: Connection lost, reconnecting... (HeartbeatFailedException: [qq号].AliveHeartbeat, recoverable=true, cause=PacketTimeoutException(message=[qq号].AliveHeartbeat Scheduler: Timeout receiving action response, cause=kotlinx.coroutines.TimeoutCancellationException: Timed out waiting for 5000 ms)) 2023-03-05 23:44:26 I/Bot.[qq号]: Bot cancelled: Bot closed

Mirai版本是这样的

14:55:30 [INFO] Verifying "net.mamoe:mirai-console" v2.14.0 14:55:35 [INFO] Verifying "net.mamoe:mirai-console-terminal" v2.14.0 14:55:37 [INFO] Verifying "net.mamoe:mirai-core-all" v2.14.0 14:55:38 [INFO] Verifying "org.itxtech:mcl-addon" v2.1.1 14:55:39 [INFO] Verifying "net.mamoe:mirai-api-http" v2.8.0 14:55:39 [WARN] Package "net.mamoe:mirai-api-http" has newer version "2.9.1" 14:55:39 [INFO] Verifying "net.mamoe:chat-command" v0.5.1 14:55:39 [WARN] Run ./mcl -u to update packages. 14:55:39 [WARN] Package "net.mamoe:chat-command" requires "net.mamoe:mirai-console" version 2.0-RC. Current version is 2.14.0

想问一下是什么问题导致的，怎么修复？谢谢！

如图我尝试获取群友发言时间以改善我的娶群友插件
f78f6a51bbee28d904ecac7569b9e92d.png
但是当我进行测试，发现无法获取到正确的时间（几乎所有人的发言时间都大于19400天）
c61770d38ce6928d5419f15829ae1e55.png
不管是活跃的人还是不活跃的人

QQ截图20230304214526.png

由于之前完成滑动验证码后报网络状态异常，我删除了bot文件夹，然后再次完成滑动验证码后报了如下错误

2023-03-04 17:50:46 E/main: net.mamoe.mirai.internal.utils.crypto.DecryptionFailedException net.mamoe.mirai.internal.utils.crypto.DecryptionFailedException at net.mamoe.mirai.internal.utils.crypto.TEA.fail(TEA.kt:299) at net.mamoe.mirai.internal.utils.crypto.TEA.doOption$decrypt(TEA.kt:275) at net.mamoe.mirai.internal.utils.crypto.TEA.doOption(TEA.kt:295) at net.mamoe.mirai.internal.utils.crypto.TEA.decrypt(TEA.kt:319) at net.mamoe.mirai.internal.utils.crypto.TEA.decrypt$default(TEA.kt:318) at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLoginExt.analyzeTlv106(WtLoginExt.kt:623) at net.mamoe.mirai.internal.network.protocol.packet.login.WtLogin$Login.onLoginSuccess(WtLogin.kt:368) at net.mamoe.mirai.internal.network.protocol.packet.login.WtLogin$Login.decode(WtLogin.kt:231) at net.mamoe.mirai.internal.network.components.PacketCodecImpl.processBody(PacketCodec.kt:491) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$PacketDecodePipeline.processBody(CommonNetworkHandler.kt:157) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$PacketDecodePipeline.access$processBody(CommonNetworkHandler.kt:102) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$PacketDecodePipeline$1$3$1.invokeSuspend(CommonNetworkHandler.kt:126) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$PacketDecodePipeline$1$3$1.invoke(CommonNetworkHandler.kt) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$PacketDecodePipeline$1$3$1.invoke(CommonNetworkHandler.kt) at kotlinx.coroutines.intrinsics.UndispatchedKt.startCoroutineUndispatched(Undispatched.kt:55) 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 kotlinx.coroutines.BuildersKt__Builders_commonKt.launch$default(Builders.common.kt:47) at kotlinx.coroutines.BuildersKt.launch$default(Unknown Source) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$PacketDecodePipeline$1.invokeSuspend(CommonNetworkHandler.kt:126) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500) at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.base/java.lang.Thread.run(Thread.java:833) 2023-03-04 17:50:46 I/Bot.1328387967: Bot cancelled: Bot closed 2023-03-04 17:50:46 I/main: mirai-console started successfully.

是这样的，我这个机器人服务两个群，然后我设置了两个小号，都有点问题，一个机器人问题是隔段时间收不到A群信息，但是B群都好好的，私聊好友什么的都正常的，但是A群他死活坚挺不到任何消息了
第二个机器人是我为了防止第一个被爆破所以加的，但是问题是不能发送一种特定消息，比如发送抽签指令，控制台有回复但是qq死活发不出来回复，但是其他功能都正常。
想请问一下各位大佬有什么方法可以修改或者解决这个问题，谢谢了

idea: 2022.2.3
jdk: 试了1.8和17 都会发生

java.lang.NoSuchMethodError at java.base/jdk.internal.reflect.GeneratedConstructorAccessor457.newInstance(Unknown Source) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480) at java.base/java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:564) at java.base/java.util.concurrent.ForkJoinTask.reportException(ForkJoinTask.java:591) at java.base/java.util.concurrent.ForkJoinTask.join(ForkJoinTask.java:672) at com.intellij.concurrency.JobLauncherImpl.processQueue(JobLauncherImpl.java:357) at com.intellij.codeInsight.daemon.impl.InspectionRunner.processInOrder(InspectionRunner.java:293) at com.intellij.codeInsight.daemon.impl.InspectionRunner.visitElements(InspectionRunner.java:268) at com.intellij.codeInsight.daemon.impl.InspectionRunner.lambda$inspect$5(InspectionRunner.java:121) at com.intellij.codeInspection.InspectionEngine.withSession(InspectionEngine.java:226) at com.intellij.codeInsight.daemon.impl.InspectionRunner.inspect(InspectionRunner.java:109) at com.intellij.codeInsight.daemon.impl.LocalInspectionsPass.collectInformationWithProgress(LocalInspectionsPass.java:131) at com.intellij.codeInsight.daemon.impl.ProgressableTextEditorHighlightingPass.doCollectInformation(ProgressableTextEditorHighlightingPass.java:97) at com.intellij.codeHighlighting.TextEditorHighlightingPass.collectInformation(TextEditorHighlightingPass.java:57) at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.lambda$doRun$1(PassExecutorService.java:400) at com.intellij.openapi.application.impl.ApplicationImpl.tryRunReadAction(ApplicationImpl.java:1154) at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.lambda$doRun$2(PassExecutorService.java:393) at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$12(CoreProgressManager.java:608) at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:683) at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:639) at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:607) at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:60) at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.doRun(PassExecutorService.java:392) at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.lambda$run$0(PassExecutorService.java:368) at com.intellij.openapi.application.impl.ReadMostlyRWLock.executeByImpatientReader(ReadMostlyRWLock.java:174) at com.intellij.openapi.application.impl.ApplicationImpl.executeByImpatientReader(ApplicationImpl.java:215) at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.run(PassExecutorService.java:366) at com.intellij.concurrency.JobLauncherImpl$VoidForkJoinTask$1.exec(JobLauncherImpl.java:184) at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373) at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182) at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655) at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622) at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165) Caused by: java.lang.NoSuchMethodError: 'org.jetbrains.kotlin.psi.KtExpression org.jetbrains.kotlin.resolve.calls.util.CallUtilKt.getCalleeExpressionIfAny(org.jetbrains.kotlin.psi.KtElement)' at net.mamoe.mirai.console.intellij.diagnostics.UsingStringPlusMessageInspection$Visitor.visitBinaryExpression(UsingStringPlusMessageInspection.kt:88) at org.jetbrains.kotlin.psi.KtVisitorVoid.visitBinaryExpression(KtVisitorVoid.java:721) at org.jetbrains.kotlin.psi.KtVisitorVoid.visitBinaryExpression(KtVisitorVoid.java:21) at org.jetbrains.kotlin.psi.KtBinaryExpression.accept(KtBinaryExpression.java:35) at org.jetbrains.kotlin.psi.KtElementImpl.accept(KtElementImpl.java:51) at com.intellij.codeInsight.daemon.impl.InspectionRunner.lambda$processInOrder$10(InspectionRunner.java:317) at com.intellij.openapi.application.impl.ApplicationImpl.tryRunReadAction(ApplicationImpl.java:1154) at com.intellij.codeInsight.daemon.impl.InspectionRunner.lambda$processInOrder$11(InspectionRunner.java:325) at com.intellij.openapi.application.impl.ReadMostlyRWLock.executeByImpatientReader(ReadMostlyRWLock.java:174) at com.intellij.openapi.application.impl.ApplicationImpl.executeByImpatientReader(ApplicationImpl.java:215) at com.intellij.codeInsight.daemon.impl.InspectionRunner.lambda$processInOrder$12(InspectionRunner.java:331) at com.intellij.util.AstLoadingFilter.forceAllowTreeLoading(AstLoadingFilter.java:159) at com.intellij.util.AstLoadingFilter.forceAllowTreeLoading(AstLoadingFilter.java:151) at com.intellij.codeInsight.daemon.impl.InspectionRunner.lambda$processInOrder$13(InspectionRunner.java:294) at com.intellij.util.AstLoadingFilter.disallowTreeLoading(AstLoadingFilter.java:130) at com.intellij.util.AstLoadingFilter.disallowTreeLoading(AstLoadingFilter.java:119) at com.intellij.codeInsight.daemon.impl.InspectionRunner.lambda$processInOrder$14(InspectionRunner.java:294) at com.intellij.concurrency.JobLauncherImpl$1MyProcessQueueTask.lambda$call$0(JobLauncherImpl.java:297) at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$12(CoreProgressManager.java:608) at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:683) at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:639) at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:607) at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:60) at com.intellij.concurrency.JobLauncherImpl$1MyProcessQueueTask.call(JobLauncherImpl.java:282) at com.intellij.concurrency.JobLauncherImpl$1MyProcessQueueTask.call(JobLauncherImpl.java:270) at java.base/java.util.concurrent.ForkJoinTask$AdaptedCallable.exec(ForkJoinTask.java:1428) ... 5 more

就是无论换了多少个账号，都是出现此类情况,不知道是因为那个的问题，还是因为我有问题
以下是报错内容===>

Login failed: Error(bot=Bot(不愿意透露QQ号), code=45, title=禁止登录, message=登录失败，建议升级最新版本后重试，或通过问题反馈与我们联系。, errorInfo=) 2023-02-25 12:04:12 E/console: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(不愿意透露QQ号), code=45, title=禁止登录, message=登录失败， 建议升级最新版本后重试，或通过问题反馈与我们联系。, errorInfo=) net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(不愿意透露QQ号), code=45, title=禁止登录, message=登录失败，建议升级最新版本后重试，或通过问题反馈与我们联系。, errorInfo=) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:331) 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) 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) 2023-02-25 12:04:12 I/Bot.不愿意透露QQ号: Bot cancelled: Bot closed >

我也不知道怎么办，看样子也只能等

输入mcl -u后无效
989f0129-3fc0-4fba-8616-4c5182b62121-image.png

前段时间还好，最近几天突然这样报错

2023-02-22 09:31:42 I/main: Backend: version 2.14.0, built on 2023-02-06 07:25:21. 2023-02-22 09:31:42 I/main: Frontend Terminal: version 2.14.0, provided by Mamoe Technologies 2023-02-22 09:31:42 I/main: Welcome to visit https://mirai.mamoe.net/ 2023-02-22 09:31:42 I/tech.kokona.mirai-automatic-slider-captcha-solver: 正在加载 Mirai Automatic Slider Captcha Solver v0.3 By 溯洄w4123 2023-02-22 09:31:42 I/plugin: Successfully loaded plugin tech.kokona.mirai-automatic-slider-captcha-solver v0.3 2023-02-22 09:31:42 I/MiraiNative: 当前系统: Windows 10 2023-02-22 09:31:42 I/MiraiNative: 当前架构: amd64 2023-02-22 09:31:42 I/plugin: Successfully loaded plugin MiraiNative v2.0.5-cp 2023-02-22 09:31:42 I/plugin: Successfully loaded plugin MCL Addon v2.1.1 2023-02-22 09:31:42 I/main: Prepared built-in commands: autoLogin, help, login, logout, permission, status, stop 2023-02-22 09:31:43 I/MiraiNative: 正在加载 Mirai Native Bridge C:\Users\wme005\OneDrive - UiT Office 365\hobby\DICE\data\org.itxtech.mirainative\CQP.dll 2023-02-22 09:31:43 I/MiraiNative: 插件 Dice.Driver.CQ.dll 已被加载，返回值为 0 。 2023-02-22 09:31:43 I/MCL Addon: iTXTech MCL Version: 2.1.2-61c8bd8 2023-02-22 09:31:43 W/MCL Addon: iTXTech Soyuz 未安装，Soyuz MCL Handler 特性已禁用 2023-02-22 09:31:43 I/main: 3 plugin(s) enabled. 2023-02-22 09:31:43 I/main: Auto-login 3122104389, protocol: ANDROID_PHONE, heartbeatStrategy: STAT_HB 2023-02-22 09:31:48 I/Bot.3122104389: Calculating type 2 PoW, it can take some time.... 2023-02-22 09:31:48 I/Bot.3122104389: Got PoW result, cost: 144 ms 2023-02-22 09:31:48 I/stdout: [AutomaticLoginSolver] Captcha URL: https://ssl.captcha.qq.com/template/wireless_mqq_captcha.html?style=simple&aid=16&uin=3122104389&sid=5400986891828187891&cap_cd=NOpeaHT1hX0hxAiwXPTBkfbQ2n_-aKjfWE-_e0HWqFzoV5nbR6ALOA**&clientype=1&apptype=2 2023-02-22 09:31:48 I/stdout: 正在自动进行滑块验证，此步骤最多需要大概1分钟 2023-02-22 09:31:48 I/stdout: 请注意: 如果显示滑块验证成功但登录时却显示网络异常，可能是由于服务器进行了过多滑块验证而被限制。这种情况可以尝试稍后再试或采用其他滑块验证方式。 2023-02-22 09:31:48 E/main: java.net.UnknownHostException: 不知道这样的主机。 (slider.kokona.tech) java.net.UnknownHostException: 不知道这样的主机。 (slider.kokona.tech) at java.base/java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) at java.base/java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:52) at java.base/java.net.InetAddress$PlatformResolver.lookupByName(InetAddress.java:1059) at java.base/java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1673) at java.base/java.net.InetAddress$NameServiceAddresses.get(InetAddress.java:1003) at java.base/java.net.InetAddress.getAllByName0(InetAddress.java:1663) at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1528) at legacy-compatibility-layer//okhttp3.Dns$Companion$DnsSystem.lookup(Dns.kt:49) at legacy-compatibility-layer//okhttp3.internal.connection.RouteSelector.resetNextInetSocketAddress(RouteSelector.kt:164) at legacy-compatibility-layer//okhttp3.internal.connection.RouteSelector.nextProxy(RouteSelector.kt:129) at legacy-compatibility-layer//okhttp3.internal.connection.RouteSelector.next(RouteSelector.kt:71) at legacy-compatibility-layer//okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.kt:205) at legacy-compatibility-layer//okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.kt:106) at legacy-compatibility-layer//okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.kt:74) at legacy-compatibility-layer//okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:255) at legacy-compatibility-layer//okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32) at legacy-compatibility-layer//okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) at legacy-compatibility-layer//okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95) at legacy-compatibility-layer//okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) at legacy-compatibility-layer//okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83) at legacy-compatibility-layer//okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) at legacy-compatibility-layer//okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76) at legacy-compatibility-layer//okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) at legacy-compatibility-layer//okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201) at legacy-compatibility-layer//okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:517) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1589) 2023-02-22 09:31:48 I/Bot.3122104389: Bot cancelled: Bot closed 2023-02-22 09:31:48 I/main: mirai-console started successfully.

登录的话没有太大问题
但现在骰娘不授权就不会在群内响应，不论是指令还是回复词都没有反应，不知道是为什么
webui的参数也没有动过，设置的是公骰，退群重加会好一会没过多久又这样了

1.png
这个是报错的日志截图
我的win10系统，JDK 64-Bit Server VM 17.0.5(64位的)
mirai版本如截图：2.png 3.png