MiraiForum
    • 注册
    • 登录
    • 搜索
    • 热门
    • 最新
    • 未解决
    • 标签
    • 群组
    • 友情链接

    机器人登录成功，但是无论什么消息都没反应怎么解决

    使用交流
    3
    18
    941
    正在加载更多帖子
    • 从旧到新
    • 从新到旧
    • 最多赞同
    回复
    • 在新帖中回复
    登录后回复
    此主题已被删除。只有拥有主题管理权限的用户可以查看。
    • I
      InsistJun666 最后由 编辑

      机器人登录成功，但是无论什么消息都没反应怎么解决
      [17:12:00] [Craft Scheduler Thread - 0/INFO]: [MiraiMC] 登录新的机器人账号: 798802921, 协议: ANDROID_PHONE
      [17:12:01] [Craft Scheduler Thread - 1/INFO]: [MiraiMC] 已找到新的插件更新，最新版本: 1.5
      [17:12:01] [Craft Scheduler Thread - 1/INFO]: [MiraiMC] 从Github下载更新: https://github.com/DreamVoid/MiraiMC/releases/latest
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: java.security.NoSuchProviderException: JCE cannot authenticate the provider BC
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at java.base/javax.crypto.JceSecurity.getInstance(JceSecurity.java:131)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at java.base/javax.crypto.KeyAgreement.getInstance(KeyAgreement.java:240)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.utils.crypto.ECDH$Companion.calculateShareKey(ECDHJvmDesktop.kt:89)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.utils.crypto.ECDH.lambda-3$testECDH(ECDHJvmDesktop.kt:49)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.utils.crypto.ECDH.<clinit>(ECDHJvmDesktop.kt:61)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.utils.crypto.ECDHKt.adjustToPublicKey(ECDH.kt:141)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.utils.crypto.ECDHKt.adjustToPublicKey(ECDH.kt:136)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.utils.crypto.ECDHInitialPublicKey.<init>(ECDH.kt:125)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.utils.crypto.ECDHInitialPublicKey.<init>(ECDH.kt:123)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.utils.crypto.ECDHKt$defaultInitialPublicKey$2.invoke(ECDH.kt:132)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.utils.crypto.ECDHKt$defaultInitialPublicKey$2.invoke(ECDH.kt:132)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.utils.crypto.ECDHKt.getDefaultInitialPublicKey(ECDH.kt:132)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.network.components.AccountSecretsManagerKt.AccountSecretsImpl(AccountSecretsManager.kt:146)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.network.components.AccountSecretsManagerKt.getSecretsOrCreate(AccountSecretsManager.kt:154)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.network.components.BotClientHolderImpl.createClient(BotClientHolder.kt:36)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.network.components.BotClientHolderImpl.access$createClient(BotClientHolder.kt:24)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.network.components.BotClientHolderImpl$client$2.invoke(BotClientHolder.kt:28)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.network.components.BotClientHolderImpl$client$2.invoke(BotClientHolder.kt:28)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.utils.LateinitMutableProperty.getValue(LateinitMutableProperty.kt:38)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.network.components.BotClientHolderImpl.getClient(BotClientHolder.kt:28)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.getClient(SsoProcessor.kt:97)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.login(SsoProcessor.kt:111)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at net.mamoe.mirai.internal.network.impl.netty.NettyNetworkHandler$StateConnecting$1.invokeSuspend(NettyNetworkHandler.kt:257)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: Caused by: java.util.jar.JarException: The JCE Provider file:/C:/Users/Administrator/Desktop/Spigot/plugins/MiraiMC/MiraiBot/libs/mirai-core-all-2.8.0.jar is not signed.
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at java.base/javax.crypto.JarVerifier.verifySingleJar(JarVerifier.java:464)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at java.base/javax.crypto.JarVerifier.verifyJars(JarVerifier.java:317)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at java.base/javax.crypto.JarVerifier.verify(JarVerifier.java:260)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at java.base/javax.crypto.ProviderVerifier.verify(ProviderVerifier.java:130)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at java.base/javax.crypto.JceSecurity.verifyProvider(JceSecurity.java:190)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at java.base/javax.crypto.JceSecurity.getVerificationResult(JceSecurity.java:218)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: at java.base/javax.crypto.JceSecurity.getInstance(JceSecurity.java:128)
      [17:12:08] [DefaultDispatcher-worker-1/WARN]: ... 29 more
      [17:12:08] [DefaultDispatcher-worker-1/INFO]: [MiraiMC] ECDH key is invalid, start to fetch ecdh public key from server.
      [17:12:09] [DefaultDispatcher-worker-1/INFO]: [MiraiMC] Successfully fetched ecdh public key from server.
      [17:12:10] [DefaultDispatcher-worker-1/INFO]: [MiraiMC] Login successful
      [17:12:10] [DefaultDispatcher-worker-1/INFO]: [MiraiMC] Saved account secrets to local cache for fast login.
      [17:12:10] [nioEventLoopGroup-4-3/INFO]: [MiraiMC] Server time updated, serverTime: 1636708330, diff: 0ms=0.0s
      [17:12:10] [DefaultDispatcher-worker-1/INFO]: [MiraiMC] Login successful.
      [17:12:10] [DefaultDispatcher-worker-1/INFO]: [MiraiMC] Start loading stranger list...
      [17:12:10] [DefaultDispatcher-worker-2/INFO]: [MiraiMC] Syncing friend message history...
      [17:12:10] [DefaultDispatcher-worker-1/INFO]: [MiraiMC] Start loading friend list...
      [17:12:10] [DefaultDispatcher-worker-1/INFO]: [MiraiMC] Successfully loaded stranger list: 0 in total
      [17:12:10] [DefaultDispatcher-worker-1/INFO]: [MiraiMC] No OtherClient online.
      [17:12:10] [DefaultDispatcher-worker-2/INFO]: [MiraiMC] Start loading group list...
      [17:12:10] [DefaultDispatcher-worker-1/INFO]: [MiraiMC] Successfully loaded friend list: 3 in total
      [17:12:10] [DefaultDispatcher-worker-1/INFO]: [MiraiMC] Syncing friend message history: Success.
      [17:12:11] [DefaultDispatcher-worker-1/INFO]: [MiraiMC] Successfully loaded group list: 1 in total.
      [17:12:11] [DefaultDispatcher-worker-1/INFO]: [MiraiMC] Bot login successful.
      [17:12:11] [DefaultDispatcher-worker-1/INFO]: [MiraiMC] Scheduled key refresh in 23h 55min 0.0s.
      [17:12:11] [DefaultDispatcher-worker-1/INFO]: [MiraiMC] Scheduled refresh login session in 19d 23h 55min 0.0s.
      [17:12:11] [Craft Scheduler Thread - 0/INFO]: [MiraiMC] 继君(798802921) 登录成功
      [17:12:13] [nioEventLoopGroup-4-4/INFO]: [MiraiMC] Server list: 180.102.111.105:8080, 42.81.184.206:80, 42.81.183.253:8080, msfwifi.3g.qq.com:8080, 42.81.184.82:8080, 49.7.253.214:14000, 14.22.9.53:443, 180.163.212.180:8080, 114.221.144.89:80, 113.96.12.27:443.

      1 条回复 最后回复 回复 引用 0
      • I
        InsistJun666 最后由 编辑

        感觉是机器人发不了消息

        1 条回复 最后回复 回复 引用 0
        • MrXiaoM
          MrXiaoM 童心未泯 最后由 编辑

          【喜报】你的机器人被风控了.jpg

          I 1 条回复 最后回复 回复 引用 0
          • I
            InsistJun666 @MrXiaoM 最后由 编辑

            @mrxiaom ???什么意思

            MrXiaoM 1 条回复 最后回复 回复 引用 0
            • MrXiaoM
              MrXiaoM 童心未泯 @InsistJun666 最后由 MrXiaoM 编辑

              @insistjun666 该发消息的时候发不出消息一律视为账号被风控了，至今没有准确的解除风控方法，有的人说在服务器上登录qq安全中心就行，有的人说用官方qq客户端在服务器上登录机器人账号聊一会天就行，有的人说在服务器上连续登录几天就行
              不要用新注册的qq号作为机器人来使用

              刚刚那个

              【喜报】你的机器人被风控了.jpg

              是一张表情包，我没找到图暂时先用文字代替（

              I 1 条回复 最后回复 回复 引用 0
              • I
                InsistJun666 @MrXiaoM 最后由 编辑

                @mrxiaom 但我直接用登录的机器人发消息能看见

                MrXiaoM 1 条回复 最后回复 回复 引用 0
                • MrXiaoM
                  MrXiaoM 童心未泯 @InsistJun666 最后由 编辑

                  @insistjun666 直接登录发信息当然看得见，mirai 是第三方客户端，而官方客户端除非出bug，没理由消息发不出去

                  1 条回复 最后回复 回复 引用 0
                  • I
                    InsistJun666 最后由 编辑

                    所以有解决方法吗

                    MrXiaoM 1 条回复 最后回复 回复 引用 0
                    • MrXiaoM
                      MrXiaoM 童心未泯 @InsistJun666 最后由 编辑

                      @insistjun666 我在上面说过了，没有准确的解决方法

                      1 条回复 最后回复 回复 引用 0
                      • I
                        InsistJun666 最后由 编辑

                        那你说的那些不准确的解决方法有用吗

                        MrXiaoM 1 条回复 最后回复 回复 引用 0
                        • MrXiaoM
                          MrXiaoM 童心未泯 @InsistJun666 最后由 编辑

                          @insistjun666 你试试不就知道了，我又没被风控过，我是听过被风控过的人的经验

                          I 1 条回复 最后回复 回复 引用 0
                          • I
                            InsistJun666 @MrXiaoM 最后由 编辑

                            @mrxiaom 好的，那请问
                            要怎么在服务器上登录qq安全中心呢

                            MrXiaoM 1 条回复 最后回复 回复 引用 0
                            • MrXiaoM
                              MrXiaoM 童心未泯 @InsistJun666 最后由 编辑

                              @insistjun666 https://aq.qq.com/

                              I 1 条回复 最后回复 回复 引用 0
                              • I
                                InsistJun666 @MrXiaoM 最后由 编辑

                                @mrxiaom 在服务器上访问这个网站登录qq就可以了？

                                MrXiaoM 1 条回复 最后回复 回复 引用 0
                                • MrXiaoM
                                  MrXiaoM 童心未泯 @InsistJun666 最后由 编辑

                                  @insistjun666 我怎么知道

                                  我又没被风控过，我是听过被风控过的人的经验

                                  自己试。能开mc服就要有自主能动性 这个词不是这么用的吧 XD

                                  1 条回复 最后回复 回复 引用 0
                                  • L
                                    ls148478 最后由 编辑

                                    为什么你两聊天 会一直给我发邮件通知 太离谱了

                                    MrXiaoM 1 条回复 最后回复 回复 引用 0
                                    • MrXiaoM
                                      MrXiaoM 童心未泯 @ls148478 最后由 编辑

                                      @ls148478 可能是你给“综合讨论”或者“使用交流”板块点了 Subscribe 的缘故吧，或者关注了这个帖子

                                      L 1 条回复 最后回复 回复 引用 0
                                      • L
                                        ls148478 @MrXiaoM 最后由 编辑

                                        @mrxiaom 恍然大悟 谢大哥指引

                                        1 条回复 最后回复 回复 引用 0
                                        • 1 / 1
                                        • First post
                                          Last post
                                        Powered by Mamoe Technologies & NodeBB | 友情链接 | 服务监控 | Contact