everyx
Repos
40
Followers
76
Following
46

Events

Created at 1 day ago
Created at 1 day ago
started
Created at 1 day ago
pull request closed
fix: systemd service caps for process sniffing

Add capabilities for process name/path sniffing feature.

Created at 2 days ago
pull request opened
fix: systemd service caps for process sniffing

Add capabilities for process name/path sniffing feature.

Created at 2 days ago

fix: systemd service caps for process sniffing

Add capabilities for process name/path sniffing feature.

Created at 2 days ago
create branch
everyx create branch fix/systemd
Created at 2 days ago

Fix shadowtls server detection

Cleanup gun conn code

Remove connect packet conn

Cleanup code

Fix listen packet on address

Fix cancel on start

Remove test on pull request

Fix dockerfile

Update documentation

Created at 2 days ago
pull request closed
fix: docker build failed
Created at 2 days ago
Navicat16 is supported.

Navicat16 is supported.

Created at 2 days ago
Navicat16 is supported.

Navicat16 is supported.

There are currently two navicat16 packages in the AUR, you can install them. I'll delete this repo here.

Created at 2 days ago

fix: update to v0.2.4

Created at 5 days ago
pull request opened
fix: docker build failed
Created at 6 days ago

fix: docker build failed

Created at 6 days ago
delete branch
everyx delete branch dev-daemon
Created at 6 days ago
delete branch
everyx delete branch dev-ech
Created at 6 days ago
delete branch
everyx delete branch dev-tls
Created at 6 days ago
delete branch
everyx delete branch dev-hysteria-tcpraw
Created at 6 days ago
delete branch
everyx delete branch dev
Created at 6 days ago
delete branch
everyx delete branch docs
Created at 6 days ago
create branch
everyx create branch improve/systemd
Created at 6 days ago
create branch
everyx create branch fix/docker-build
Created at 6 days ago
closed issue
Cannot connect after using beta16 with shadowTLS + VMESS

Welcome

  • [X] Yes, I'm using the latest major release. Only such installations are supported.
  • [X] Yes, I'm using the latest Golang release. Only such installations are supported.
  • [X] Yes, I've searched similar issues on GitHub and didn't find any.
  • [X] Yes, I've included all information below (version, FULL config, FULL log, etc).

Description of the problem

Cannot connect after using beta16 with shadowTLS + VMESS

Version of sing-box

$ sing-box version
sing-box version 1.1-beta16

Environment: go1.19.3 linux/amd64
Tags: with_clash_api,with_quic,with_wireguard,with_acme
Revision: afa7831e6f21d7c2f7196ae629130bd6fa671596

Server and client configuration file

{
  "log": {
    "level": "warn",
    "timestamp": false
  },
  "inbounds": [
    {
      "type": "shadowtls",
      "listen": "::",
      "listen_port": 4434,
      "version": 2,
      "password": "password",
      "handshake": {
        "server": "cloud.tencent.com",
        "server_port": 443
      },
      "detour": "vmess-in"
    },
    {
      "tag": "vmess-in",
      "type": "vmess",
      "listen": "127.0.0.1",
      "users": [
        {
          "name": "user@example.com",
          "uuid": "e850559d-a0c4-4f22-b0db-466c0a32f708",
          "alterId": 0
        }
      ]
    }
  ],
  "outbounds": [
    {
      "tag": "direct",
      "type": "direct"
    }
  ]
}
{
  "log": { "level": "warn", "timestamp": false },
  "inbounds": [{ "type": "mixed", "listen": "::", "listen_port": 1080 }],
  "outbounds": [
    {
      "tag": "proxy",
      "detour": "proxy-out",
      "type": "vmess",
      "uuid": "e850559d-a0c4-4f22-b0db-466c0a32f708",
      "multiplex": { "enabled": true, "max_connections": 10 }
    },
    {
      "tag": "proxy-out",
      "type": "shadowtls",
      "version": 2,
      "password": "password",
      "server": "xxx.xxx.xxx.xxx",
      "server_port": 4434,
      "tls": { "enabled": true, "server_name": "cloud.tencent.com" }
    }
  ],
  "route": {
    "geoip": { "path": "/usr/share/sing-geoip/geoip.db" },
    "geosite": { "path": "/usr/share/sing-geosite/geosite.db" },
    "final": "proxy"
  },
  "experimental": {
    "clash_api": {
      "external_controller": "127.0.0.1:9090",
      "external_ui": "/usr/share/yacd"
    }
  }
}

Server and client log file

2022-11-21T07:24:05.678462000Z fuckgfw_sing-box.0.i4emc9cxvmn1@cloudcone01    | WARN[0189] [819752469] inbound/shadowtls[0]: fallback connection
ERROR[0111] [2294925898] inbound/mixed[0]: process connection from 127.0.0.1:35638: upload: read tcp 127.0.0.1:1080->127.0.0.1:35638: use of closed network connection | download: cipher: message authentication failed
ERROR[0116] [4206704684] inbound/mixed[0]: process connection from 127.0.0.1:41440: download: cipher: message authentication failed | upload: read tcp 127.0.0.1:1080->127.0.0.1:41440: use of closed network connection```
                                    
Created at 6 days ago
issue comment
Cannot connect after using beta16 with shadowTLS + VMESS

Try f8eea47

It works fine again.

Created at 6 days ago
opened issue
Cannot connect after using beta16 with shadowTLS + VMESS

Welcome

  • [X] Yes, I'm using the latest major release. Only such installations are supported.
  • [X] Yes, I'm using the latest Golang release. Only such installations are supported.
  • [X] Yes, I've searched similar issues on GitHub and didn't find any.
  • [X] Yes, I've included all information below (version, FULL config, FULL log, etc).

Description of the problem

Cannot connect after using beta16 with shadowTLS + VMESS

Version of sing-box

$ sing-box version
sing-box version 1.1-beta16

Environment: go1.19.3 linux/amd64
Tags: with_clash_api,with_quic,with_wireguard,with_acme
Revision: afa7831e6f21d7c2f7196ae629130bd6fa671596

Server and client configuration file

{
  "log": {
    "level": "warn",
    "timestamp": false
  },
  "inbounds": [
    {
      "type": "shadowtls",
      "listen": "::",
      "listen_port": 4434,
      "version": 2,
      "password": "password",
      "handshake": {
        "server": "cloud.tencent.com",
        "server_port": 443
      },
      "detour": "vmess-in"
    },
    {
      "tag": "vmess-in",
      "type": "vmess",
      "listen": "127.0.0.1",
      "users": [
        {
          "name": "user@example.com",
          "uuid": "e850559d-a0c4-4f22-b0db-466c0a32f708",
          "alterId": 0
        }
      ]
    }
  ],
  "outbounds": [
    {
      "tag": "direct",
      "type": "direct"
    }
  ]
}
{
  "log": { "level": "warn", "timestamp": false },
  "inbounds": [{ "type": "mixed", "listen": "::", "listen_port": 1080 }],
  "outbounds": [
    {
      "tag": "proxy",
      "detour": "proxy-out",
      "type": "vmess",
      "uuid": "e850559d-a0c4-4f22-b0db-466c0a32f708",
      "multiplex": { "enabled": true, "max_connections": 10 }
    },
    {
      "tag": "proxy-out",
      "type": "shadowtls",
      "version": 2,
      "password": "password",
      "server": "xxx.xxx.xxx.xxx",
      "server_port": 4434,
      "tls": { "enabled": true, "server_name": "cloud.tencent.com" }
    }
  ],
  "route": {
    "geoip": { "path": "/usr/share/sing-geoip/geoip.db" },
    "geosite": { "path": "/usr/share/sing-geosite/geosite.db" },
    "final": "proxy"
  },
  "experimental": {
    "clash_api": {
      "external_controller": "127.0.0.1:9090",
      "external_ui": "/usr/share/yacd"
    }
  }
}

Server and client log file

2022-11-21T07:24:05.678462000Z fuckgfw_sing-box.0.i4emc9cxvmn1@cloudcone01    | WARN[0189] [819752469] inbound/shadowtls[0]: fallback connection
ERROR[0111] [2294925898] inbound/mixed[0]: process connection from 127.0.0.1:35638: upload: read tcp 127.0.0.1:1080->127.0.0.1:35638: use of closed network connection | download: cipher: message authentication failed
ERROR[0116] [4206704684] inbound/mixed[0]: process connection from 127.0.0.1:41440: download: cipher: message authentication failed | upload: read tcp 127.0.0.1:1080->127.0.0.1:41440: use of closed network connection```
                                    
Created at 6 days ago
Created at 1 week ago
issue comment
多屏时应使用最大分辨率的屏幕来生成壁纸

好的,我先安装一下 git 版本,下次有问题再来提交

日志有了

JS ERROR: shuzhi: Error
_execute@/usr/share/gnome-shell/extensions/shuzhi@tuberry/extension.js:285:42
async*_getMotto@/usr/share/gnome-shell/extensions/shuzhi@tuberry/extension.js:304:51
async*_setMotto@/usr/share/gnome-shell/extensions/shuzhi@tuberry/extension.js:318:18
set refresh/this._refreshId<@/usr/share/gnome-shell/extensions/shuzhi@tuberry/extension.js:257:62
Created at 1 week ago
issue comment
多屏时应使用最大分辨率的屏幕来生成壁纸

另外还有一个问题,经常会出现如图中的这样不显示诗词的情况,但是我运行脚本输出又是正常的,journalctl /usr/bin/gnome-shell -r 查看日志也没有什么和本插件相关报错的,不知道是什么原因。

没有复现。现在加了 log 下次出现 journalctl -fo cat /usr/bin/gnome-shell 应该就有报错了。如果问题和上游今日诗词 API 相关可考虑使用离线数据,参考_shuzhi.fish.

好的,我先安装一下 git 版本,下次有问题再来提交

Created at 1 week ago
opened issue
多屏时应使用最大分辨率的屏幕来生成壁纸

目前好像是根据主显示器的分辨率设置的,我的外接显示器就会出现黑边。

另外还有一个问题,经常会出现如图中的这样不显示诗词的情况,但是我运行脚本输出又是正常的,journalctl /usr/bin/gnome-shell -r 查看日志也没有什么和本插件相关报错的,不知道是什么原因。

主屏填充完好 图片

副屏上下有黑边 图片

Created at 1 week ago
started
Created at 1 week ago