Mirai-Setu - 在群里获取loliconapi的setu插件

cssxsh

@mr_null
这种一般是网络问题，特别是运营商移动的网，很容易自带墙中墙

shenmo

@cssxsh 我遇到了，链接有效，但是管道断开
需要log么

shenmo

@cssxsh ```
2021-07-11 01:35:16 V/Bot.1143816631: [SM-X 神末服务器交流群(913146678)] shenmo7192(1422953823) -> 请给我一张色图
2021-07-11 01:35:16 V/Bot.1143816631: Event: GroupMessagePreSendEvent(target=Group(913146678), message=[mirai:quote:[46645],[84569787]]Fetching setu...)
2021-07-11 01:35:16 V/Bot.1143816631: Group(913146678) <- [mirai:quote:[46645],[84569787]]Fetching setu...
2021-07-11 01:35:16 V/Bot.1143816631: Event: GroupMessagePostSendEvent(target=Group(913146678), message=[mirai:quote:[46645],[84569787]]Fetching setu..., exception=null, receipt=net.mamoe.mirai.message.MessageReceipt@47495135)
2021-07-11 01:35:16 V/Bot.1143816631: Event: GroupMessagePreSendEvent(target=Group(913146678), message=[mirai:quote:[46645],[84569787]]出现错误, 请联系管理员检查后台或重试
Connection reset)
2021-07-11 01:35:17 V/Bot.1143816631: Group(913146678) <- [mirai:quote:[46645],[84569787]]出现错误, 请联系管理员检查后台或重试\nConnection reset
2021-07-11 01:35:17 V/Bot.1143816631: Event: GroupMessagePostSendEvent(target=Group(913146678), message=[mirai:quote:[46645],[84569787]]出现错误, 请联系管理员检查后台或重试
Connection reset, exception=null, receipt=net.mamoe.mirai.message.MessageReceipt@1d141fcd)
2021-07-11 01:35:17 E/main: Exception in coroutine <unnamed>
java.net.SocketException: Connection reset
at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
at okio.InputStreamSource.read(JvmOkio.kt:90)
at okio.AsyncTimeout$source$1.read(AsyncTimeout.kt:129)
at okio.RealBufferedSource.indexOf(RealBufferedSource.kt:449)
at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.kt:333)
at okhttp3.internal.http1.HeadersReader.readLine(HeadersReader.kt:29)
at okhttp3.internal.http1.Http1ExchangeCodec.readResponseHeaders(Http1ExchangeCodec.kt:178)
at okhttp3.internal.connection.Exchange.readResponseHeaders(Exchange.kt:106)
at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.kt:79)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:34)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:82)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100)
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:197)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:502)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)

shenmo

@cssxsh at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:127)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:349)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:292)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:287)
at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:144)
at java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1418)
at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1324)
at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:440)
at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:411)
at okhttp3.internal.connection.RealConnection.connectTls(RealConnection.kt:367)
at okhttp3.internal.connection.RealConnection.establishProtocol(RealConnection.kt:325)
at okhttp3.internal.connection.RealConnection.connect(RealConnection.kt:197)
at okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.kt:249)
at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.kt:108)
at okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.kt:76)
at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:245)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:82)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100)
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:197)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:502)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Suppressed: java.net.SocketException: 断开的管道 (Write failed)
at java.base/java.net.SocketOutputStream.socketWrite0(Native Method)
at java.base/java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:110)
at java.base/java.net.SocketOutputStream.write(SocketOutputStream.java:150)
at java.base/sun.security.ssl.SSLSocketOutputRecord.encodeAlert(SSLSocketOutputRecord.java:81)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:380)
... 27 more
Caused by: java.net.SocketException: Connection reset
at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
at java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
at java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
at java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:110)

cssxsh

@shenmo
你用机器人在的PC端用浏览器打开 https://api.lolicon.app/#/setu 试试看能不能正常访问
如果是服务器的话用指令 curl -i https://api.lolicon.app

shenmo

@cssxsh ubuntu@VM-0-13-ubuntu:~$ curl -i https://api.lolicon.app
HTTP/2 200
date: Sat, 10 Jul 2021 17:42:47 GMT
content-type: text/html; charset=utf-8
last-modified: Fri, 25 Jun 2021 12:20:01 GMT
access-control-allow-origin: *
expires: Sat, 10 Jul 2021 17:49:51 GMT
cache-control: max-age=600
x-proxy-cache: MISS
x-github-request-id: CB46:04FE:2429EA6:323458A:60E9DB67
via: 1.1 varnish, 1.1 vegur
age: 32
x-served-by: cache-bwi5064-BWI
x-cache: HIT
x-cache-hits: 1
x-timer: S1625938968.638233,VS0,VE1
vary: Accept-Encoding
x-fastly-request-id: a77def50b43485d931ae1b7be7f01d57b2cc6fe7
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
report-to: {"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v2?s=MsBJMb%2BVt4EzT5UzLLpA%2BXtfzdicxsJRbseKlLwCJZl5wWJNKXme5ZAtFnA1EkWZalFx6OWokGkZPI0yI%2BTmhV9SXXDmMZbAaPpDVuCiLZECl8gFamO5feWNydJQ"}],"group":"cf-nel","max_age":604800}
nel: {"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 66cb9732e8840503-LAX
alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400, h3=":443"; ma=86400

<!DOCTYPE html>
<html lang="zh">
<head>
<meta charset="UTF-8">
<title>Lolicon API</title>
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
<meta name="description" content="Lolicon API">
<meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0">
<link href="https://cdn.jsdelivr.net/npm/docsify@4.12.1/themes/vue.css" rel="stylesheet" crossorigin="anonymous">
<link href="https://cdn.jsdelivr.net/npm/docsify-vuepress-theme@1.0.9/dist/style.min.css" rel="stylesheet" crossorigin="anonymous">
<link href="https://cdn.jsdelivr.net/npm/prismjs@1/themes/prism-tomorrow.min.css" rel="stylesheet" crossorigin="anonymous">
<link href="https://cdn.jsdelivr.net/combine/npm/purecss@2.0.6/build/grids-min.css,npm/purecss@2.0.6/build/grids-responsive-min.css" rel="stylesheet" crossorigin="anonymous" />
<link href="assets/css/index.min.css?v=20210618_1" rel="stylesheet">

Nambers

@唯黎维离这种一般不用管

Akane29

每隔一段时间，大约两到三天之间就会出现这样的错误“出现错误, 请联系管理员检查后台或重试
Failed to connect to api.lolicon.app/2606:4700:3034:0:0:0:ac43:d436:80
”请问是什么原因

Wdam

qq群聊中显示requestAPI错误
api填写如下
'requestApi: https://api.fantasyzone.cc/tu'

Oeed

尝试开VPN，直连访问。
并且插件配置设置成直连

错误提示：出现错误, 请联系管理员检查后台或重试
Connect timeout has expired [url=https://i.pximg.net/img-original/img/2020/10/02/21/00/47/84753806_p0.jpg, connect_timeout=unknown ms]

感觉是不是Header 不行？有点像头文件不清楚的时候被Ban的感觉

Oeed

This post is deleted!

Malg13

$curl  -v  "https://api.lolicon.app"
* About to connect() to api.lolicon.app port 443 (#0)
*   Trying 104.21.53.108...
* Connected to api.lolicon.app (104.21.53.108) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* NSS error -5961 (PR_CONNECT_RESET_ERROR)
* TCP connection reset by peer
* Closing connection 0
curl: (35) TCP connection reset by peer

我这是已经被ban了吗。。。。

Simple

本群尚未开启插件,请联系管理员

未来のミライ

@simple config\mirai-setu中setting.yml设置管理员，并使用管理员在群里面开启权限

未来のミライ

2021-07-22 16:13:53 V/Bot.71*****: Event: GroupMessagePostSendEvent(target=Group(799******), message=[mirai:quote:[28212],[2055720215]]出现错误, 请联系管理员检查后台或重试
Connect timeout has expired [url=https://api.fantasyzone.cc/tu?type=json&class=pc&r18=0, connect_timeout=unknown ms], exception=null, receipt=net.mamoe.mirai.message.MessageReceipt@4746fa51)
2021-07-22 16:13:53 E/main: Exception in coroutine <unnamed>
io.ktor.network.sockets.ConnectTimeoutException: Connect timeout has expired [url=https://api.fantasyzone.cc/tu?type=json&class=pc&r18=0, connect_timeout=unknown ms]
at io.ktor.client.features.HttpTimeoutKt.ConnectTimeoutException(HttpTimeout.kt:183)
at io.ktor.client.engine.okhttp.OkUtilsKt.mapOkHttpException(OkUtils.kt:75)
at io.ktor.client.engine.okhttp.OkUtilsKt.access$mapOkHttpException(OkUtils.kt:1)
at io.ktor.client.engine.okhttp.OkHttpCallback.onFailure(OkUtils.kt:39)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:510)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.base/java.net.PlainSocketImpl.waitForConnect(Native Method)
at java.base/java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:107)
at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:399)
at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:242)
at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:224)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.base/java.net.Socket.connect(Socket.java:609)
at okhttp3.internal.platform.Platform.connectSocket(Platform.kt:119)
at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.kt:283)
at okhttp3.internal.connection.RealConnection.connect(RealConnection.kt:195)
at okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.kt:249)
at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.kt:108)
at okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.kt:76)
at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:245)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:82)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:100)
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:197)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:502)
... 3 more
出现这种情况时怎么回事？

Simple

@未来のミライ要发什么?

Simple

@未来のミライ群主可以吗

Kallen

@simple

在.\config\mirai-setu目录下找到Settings.yml之后在图示的地方填写自己的QQ号

重启框架之后在想开启的群里发送图中红字任选指令

Simple

@kallen 重启后没反应了

Kallen

@simple
我赌你是用记事本改的