你好,我这边有个问题
我是使用服务器搭建的bot
我想使用它给出的链接然后我服务器开端口进远程设置
但完全没用
并且我的端口通过查询是开启状态就是进不去
我开了tcp和udp,同时开了也没用
有什么解决方法吗?
Ours 发布的最佳帖子
-
RE: Console 自动定义回复插件
-
v2.15.0-RC + fix-protocol-version V1.8.0已经能被检测了吗?
Login failed: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below.
2023-06-22 19:20:49 E/console: 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:262)
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(114514), code=45, title=禁止登录, message=你的帐号涉嫌违规被限制在非常用设备登录,请更换常用设备后重新登 录并根据提示进行解封。, errorInfo=)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:489)
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
Suppressed: java.lang.IllegalStateException: Fast login failed: Error(bot=Bot(114514), code=40, title=安全提醒, message=请确认你输入了正确的帐号。该帐号存在被盗风险,已进入保护模 式,请前往安全中心恢复。, errorInfo=)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$FastLoginImpl.doLogin(SsoProcessor.kt:527)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$FastLoginImpl$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(114514), code=45, title=禁止登录, message=你的帐号涉嫌违规被限制在非常用设备登录,请更换常用 设备后重新登录并根据提示进行解封。, errorInfo=)]手机打开后是:
因涉嫌异常使用行为(如涉嫌批量登录等业务违规操作,传播违法违规信息或组织相关活动)被暂时冻结QQ客户端登录。
也有和我在同一时期被一样封禁的人,打电话给客服,客服说使用了外挂程序,第三方插件和程序,并且已经检测出违规行为,是因为qq号风控程度高被风控,还是因为新协议的问题? -
RE: 自定义调用API插件
能增加一个功能吗?我觉得很实用,比如你使用了指令但查错了他会直接返回$1 $2类似这样
所以能增加查询失败反馈失败吗?
我说的可能不是很清楚,大概意思是参考插件内的模板
未来天气 城市
如果填对了城市直接返回结果如果不填城市也返回结果但全是$1 $2如下,并且填错城市他查不出来也返回如下
所以能增加一个模块比如查询失败反馈自定义失败回复
或者不自定义也行,单纯回复查询失败,指令错误,或者查询对象有误
如果只使用未来天气 不填城市也会回复$1 $1 能添加模块回复无查询对象,请填写对象?
可能添加此类功能比较麻烦但还是希望添加一下,我觉得对于目前版本是一个很不错的想法 -
RE: 自定义调用API插件
使用时报错
2022-06-04 12:40:37 W/stderr: java.net.ConnectException: Connection refused (Connection refused)
2022-06-04 12:40:37 W/stderr: at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
2022-06-04 12:40:37 W/stderr: at java.base/java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/java.net.AbstractPlainSocketImpl.connect(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/java.net.SocksSocketImpl.connect(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/java.net.Socket.connect(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/sun.net.NetworkClient.doConnect(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/sun.net.www.http.HttpClient.openServer(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/sun.net.www.http.HttpClient.openServer(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(Unknown Source)
2022-06-04 12:40:37 W/stderr: at MiraiCallApiPlugin-v1.4.jar//org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:859)
2022-06-04 12:40:37 W/stderr: at MiraiCallApiPlugin-v1.4.jar//org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:829)
2022-06-04 12:40:37 W/stderr: at MiraiCallApiPlugin-v1.4.jar//org.jsoup.helper.HttpConnection.execute(HttpConnection.java:366)
2022-06-04 12:40:37 W/stderr: at MiraiCallApiPlugin-v1.4.jar//org.jsoup.helper.HttpConnection.get(HttpConnection.java:353)
2022-06-04 12:40:37 W/stderr: at MiraiCallApiPlugin-v1.4.jar//io.github.Kloping.mirai.p1.Worker.doc(Worker.java:170)
2022-06-04 12:40:37 W/stderr: at MiraiCallApiPlugin-v1.4.jar//io.github.Kloping.mirai.p1.Worker.call(Worker.java:92)
2022-06-04 12:40:37 W/stderr: at MiraiCallApiPlugin-v1.4.jar//io.github.Kloping.mirai.p1.CallApiPlugin$1.onMessage0(CallApiPlugin.java:61)
2022-06-04 12:40:37 W/stderr: at MiraiCallApiPlugin-v1.4.jar//io.github.Kloping.mirai.p1.CallApiPlugin$1.onMessage(CallApiPlugin.java:71)
2022-06-04 12:40:37 W/stderr: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2022-06-04 12:40:37 W/stderr: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
2022-06-04 12:40:37 W/stderr: at java.base/java.lang.reflect.Method.invoke(Unknown Source)
2022-06-04 12:40:37 W/stderr: at net.mamoe.mirai.internal.event.JvmMethodListenersInternalKt.registerEventHandler$callMethod$invokeWithErrorReport(JvmMethodListenersInternal.kt:140)
2022-06-04 12:40:37 W/stderr: at net.mamoe.mirai.internal.event.JvmMethodListenersInternalKt.access$registerEventHandler$callMethod$invokeWithErrorReport(JvmMethodListenersInternal.kt:1)
2022-06-04 12:40:37 W/stderr: at net.mamoe.mirai.internal.event.JvmMethodListenersInternalKt$registerEventHandler$callMethod$2.invokeSuspend(JvmMethodListenersInternal.kt:154)
2022-06-04 12:40:37 W/stderr: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
2022-06-04 12:40:37 W/stderr: at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
2022-06-04 12:40:37 W/stderr: at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
2022-06-04 12:40:37 W/stderr: at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
2022-06-04 12:40:37 W/stderr: at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
2022-06-04 12:40:37 W/stderr: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:749)
2022-06-04 12:40:37 W/stderr: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
2022-06-04 12:40:37 W/stderr: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
能看看是出什么问题了吗?
api用的是api.antisniper.net/findnick
一直会报错,看样子是用了cloudflare
难不成是这个问题吗?
如果是的话插件添加一个代理功能会好点(?)
Ours 发布的最新帖子
-
RE: QQ群bot官方接口,与使用体验
@Dituon 分私域和公域,公域个人的话,主动消息只有99条上线,但是私域有2亿,并且公域只能获取到@机器人后面的消息,公域不给所有消息侦听的权限,倒是私域能直接监听,包括私聊,私域能直接检测任意频道内所有人发的任何消息,不用@都能监听到
-
RE: 求助:9月13号发现,QQ账号登录不上,返回code=45,title=禁止登录, message=你当前使用的QQ版本过低,请前往QQ官网im.qq.com下载最新版QQ后重试。
@Anstiya
请看我发的贴子:
https://github.com/fuqiuluo/unidbg-fetch-qsign/discussions/247
这里发不了很长的logs
已经使用了换8.9.73
unidbg-fetch-qsign使用的java 8
android_pad.json也是对应的8.9.73版本
登录后提示:
2023-09-13 16:17:48 E/MAH Access: kotlinx.coroutines.JobCancellationException: StandaloneCoroutine was cancelled; job=StandaloneCoroutine{Cancelling}@290d89a8
kotlinx.coroutines.JobCancellationException: StandaloneCoroutine was cancelled; job=StandaloneCoroutine{Cancelling}@290d89a8
并且使用的Ariadne当机器人发消息后报logs:
2023-09-13 16:20:51.892 | INFO | graia.ariadne.model:log:82 - xxx: [SEND][xxx(xxx)] <- [图片]
2023-09-13 16:20:51.892 | WARNING | graia.ariadne.app:send_group_message:1788 - Failed to send message, your account may be blocked.
随便报可能被拉黑了,但是我在群内使用其他qq号依旧可以看到机器人发的消息。
我不知道等个2小时后会不会给我封掉。
unidbg-fetch-qsign的logs不到几分钟就很长,只截取了一部分:
https://github.com/fuqiuluo/unidbg-fetch-qsign/discussions/247 -
RE: v2.15.0-RC + fix-protocol-version V1.8.0已经能被检测了吗?
@cssxsh hhh,只是之前运行被冻结,风控没那么频繁,这段时间太频繁了😭
-
v2.15.0-RC + fix-protocol-version V1.8.0已经能被检测了吗?
Login failed: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below.
2023-06-22 19:20:49 E/console: 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:262)
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(114514), code=45, title=禁止登录, message=你的帐号涉嫌违规被限制在非常用设备登录,请更换常用设备后重新登 录并根据提示进行解封。, errorInfo=)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:489)
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
Suppressed: java.lang.IllegalStateException: Fast login failed: Error(bot=Bot(114514), code=40, title=安全提醒, message=请确认你输入了正确的帐号。该帐号存在被盗风险,已进入保护模 式,请前往安全中心恢复。, errorInfo=)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$FastLoginImpl.doLogin(SsoProcessor.kt:527)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$FastLoginImpl$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(114514), code=45, title=禁止登录, message=你的帐号涉嫌违规被限制在非常用设备登录,请更换常用 设备后重新登录并根据提示进行解封。, errorInfo=)]手机打开后是:
因涉嫌异常使用行为(如涉嫌批量登录等业务违规操作,传播违法违规信息或组织相关活动)被暂时冻结QQ客户端登录。
也有和我在同一时期被一样封禁的人,打电话给客服,客服说使用了外挂程序,第三方插件和程序,并且已经检测出违规行为,是因为qq号风控程度高被风控,还是因为新协议的问题? -
RE: 关于Mirai是否能够正常登录机器人
@起舞弄清影 如果你直接用java -D"file.encoding=utf-8" -cp "./libs/" net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader 启动的话
他是使用的电脑系统环境中的java,导致java报错,如果你之前用的mcl启动器,直接替换就行
用mcl里面的java就没事了
比如我的mcl整合包内的mcl文件信息:
@echo off
setlocal
set JAVA_BINARY="C:\Users\xxx\Desktop\mcl-test\java\bin\java.exe"
%JAVA_BINARY% -jar mcl.jar %set EL=%ERRORLEVEL%
if %EL% NEQ 0 (
echo Process exited with %EL%
pause
)
然后修改指令,把:
java -D"file.encoding=utf-8" -cp "./libs/" net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader
替换成:
C:\Users\xxx\Desktop\mcl-test\java\bin\java.exe -D"file.encoding=utf-8" -cp "./libs/" net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader
现在就能正常启动了 -
RE: 是不是目前手机客户端和mirai的ANDROID_PAD无法同时在线?
并且我拿着/bots/qq号,这个文件夹打包拿到2.14和2.15.0-M1里面都无法登录:
是因为版本不兼容吗?