Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug?]: Linux下似乎ipv6连接不上Lagrange Onebot #678

Open
4 tasks done
Threkork opened this issue Nov 4, 2024 · 1 comment
Open
4 tasks done

[Bug?]: Linux下似乎ipv6连接不上Lagrange Onebot #678

Threkork opened this issue Nov 4, 2024 · 1 comment
Labels
bug? Maybe it's a bug

Comments

@Threkork
Copy link

Threkork commented Nov 4, 2024

请确保您已阅读以上注意事项,并勾选下方的确认框。

  • 我已经仔细阅读上述内容
  • 我已经使用 最新构建 测试过,问题依旧存在。
  • 我已经在 Issue Tracker 中找过我要提出的问题,没有找到相同问题的ISSUE。
  • 我已知晓并同意,此处仅用于汇报程序中存在的问题。若这个 Issue 是关于其他非程序本身问题,则我的 Issue 可能会被无条件自动关闭或/并锁定。(其它疑问请考虑加入TG群询问或在discussions中提问)

Lagrange项目

OneBot

所使用/依赖的Lagrange项目对应的commit

86d39d3

运行环境

Linux

运行架构

x64

连接方式

正向 WebSocket

重现步骤

Linux下
配置host: "*"
启动Lagrange
使用任意工具连接

期望的结果是什么?

连接成功

实际的结果是什么?

没有连接成功,但是ipv4,或者域名可以。
图片

简单的复现代码/链接(可选)

No response

Trace 级别日志记录(可选)

❯ ./Lagrange.OneBot
Lagrange.OneBot Version: 0.0.3+86d39d3c908a841985042bc9be25e00a9fae4a63

warn: Lagrange.OneBot.Utility.MusicSigner[0]
      MusicSignServer is not available, sign may be failed
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
      Content root path: /home/threkork/.start/onebot/小可beta
info: Lagrange.OneBot.LagrangeApp[0]
      Lagrange.OneBot Implementation has started
info: Lagrange.OneBot.LagrangeApp[0]
      Protocol:  | 3.2.10-25765
info: Lagrange.Core.BotContext[0]
      [2024-11-04 23:09:30] [SocketContext] [VERBOSE]: Server: http://183.47.101.221:8080/ Latency: 10
info: Lagrange.Core.BotContext[0]
      [2024-11-04 23:09:30] [SocketContext] [VERBOSE]: Server: http://183.47.102.213:8080/ Latency: 12
info: Lagrange.Core.BotContext[0]
      [2024-11-04 23:09:30] [SocketContext] [VERBOSE]: Server: http://183.47.99.24:8080/ Latency: 13
info: Lagrange.Core.BotContext[0]
      [2024-11-04 23:09:30] [SocketContext] [VERBOSE]: Server: http://183.2.144.33:8080/ Latency: 13
info: Lagrange.Core.BotContext[0]
      [2024-11-04 23:09:30] [SocketContext] [VERBOSE]: Server: http://14.22.9.53:8080/ Latency: 11
info: Lagrange.Core.BotContext[0]
      [2024-11-04 23:09:30] [SocketContext] [VERBOSE]: Server: http://183.47.102.193:8080/ Latency: 12
info: Lagrange.Core.BotContext[0]
      [2024-11-04 23:09:30] [SocketContext] [VERBOSE]: Server: http://14.22.9.84:8080/ Latency: 12
info: Lagrange.Core.BotContext[0]
      [2024-11-04 23:09:30] [SocketContext] [VERBOSE]: Server: http://119.147.190.138:8080/ Latency: 13
info: Lagrange.Core.BotContext[0]
      [2024-11-04 23:09:30] [WtExchangeLogic] [INFORMATION]: Session has not expired, using session to login and register status
trce: Lagrange.Core.BotContext[0]
      [2024-11-04 23:09:30] [ServiceContext] [DEBUG]: Outgoing SSOFrame: trpc.qq_new_tech.status_svc.StatusService.Register
trce: Lagrange.Core.BotContext[0]
      [2024-11-04 23:09:30] [ServiceContext] [DEBUG]: Incoming SSOFrame: trpc.qq_new_tech.status_svc.StatusService.Register
info: Lagrange.Core.BotContext[0]
      [2024-11-04 23:09:30] [WtExchangeLogic] [INFORMATION]: Register Status: register success
info: Lagrange.Core.BotContext[0]
      [2024-11-04 23:09:30] [WtExchangeLogic] [INFORMATION]: AutoReLogin Enabled, session would be refreshed in 15 days period
info: Lagrange.OneBot.LagrangeApp[0]
      Bot Online: 1947375033
info: Lagrange.OneBot.Core.Network.LagrangeWebSvcCollection[1]
      [LagrangeWebSvcCollection]: Multi Connection has been configured
info: Lagrange.OneBot.Core.Network.Service.ForwardWSService[10]
      The server is started at http://*:60281/
trce: Lagrange.Core.BotContext[0]
      [2024-11-04 23:09:40] [ServiceContext] [DEBUG]: Outgoing SSOFrame: Heartbeat.Alive
trce: Lagrange.Core.BotContext[0]
      [2024-11-04 23:09:50] [ServiceContext] [DEBUG]: Outgoing SSOFrame: Heartbeat.Alive

补充说明(可选)

No response

@Threkork Threkork added the bug? Maybe it's a bug label Nov 4, 2024
@RTAkland
Copy link

RTAkland commented Nov 9, 2024

用的如果是正向ws的话只需要把Host的值改成*就行了, windows上需要使用管理员权限运行才能监听

@DarkRRb DarkRRb pinned this issue Nov 10, 2024
@DarkRRb DarkRRb unpinned this issue Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug? Maybe it's a bug
Projects
None yet
Development

No branches or pull requests

2 participants