Open shinyboy opened 4 years ago
Application log:
default 21:30:23.809931+0800 lsd SecTranslocateCreateSecureDirectoryForURL: created /private/var/folders/j9/j5vk81hs6h11xlv435bf7tww0000gn/T/AppTranslocation/D0BAD042-0FE8-4EC7-BAD2-BBB842B3F098/d/ShadowsocksX-NG.app
default 21:30:23.853684+0800 Finder LAUNCHING:0x0-0x146146 ShadowsocksX-NG foreground=0 bringForward=0 seed=465 userActivityCount=0
default 21:30:23.919935+0800 loginwindow -[ApplicationManager checkInAppContext:eventData:] | ApplicationManager: Checked in app : ShadowsocksX-NG
default 21:30:23.929253+0800 runningboardd Resolved pid 6496 to [executable<ShadowsocksX-NG(501)>:6496]
default 21:30:23.933115+0800 runningboardd [executable<ShadowsocksX-NG(501)>:6496] This process will not be managed.
default 21:30:23.933660+0800 runningboardd Now tracking process: [executable<ShadowsocksX-NG(501)>:6496]
default 21:30:23.934978+0800 runningboardd Acquiring assertion targeting executable<ShadowsocksX-NG(501)> from originator [daemon
一样的问题,我也是链接超时
一样的问题,我也是链接超时 你也是升级前正常,升级后出问题了吗?
我刚开始用,第一次使用的美国线路,说的是现在用不了
------------------ 原始邮件 ------------------ 发件人: "shinyboy"<notifications@github.com>; 发送时间: 2020年4月3日(星期五) 上午10:43 收件人: "shadowsocks/ShadowsocksX-NG"<ShadowsocksX-NG@noreply.github.com>; 抄送: "838163739"<838163739@qq.com>; "Comment"<comment@noreply.github.com>; 主题: Re: [shadowsocks/ShadowsocksX-NG] 升级macOS后shadowsocksX-NG似乎不可用了 (#1297)
一样的问题,我也是链接超时 你也是升级前正常,升级后出问题了吗?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
同样的问题,PAC用不了,全局模式可以
我也发现同样的问题!但是,我发现是本地监听接口改为1086,改为1080就能正常使用.我很确信我没改过这个本地接口,就算我手戝改了,也不可能改为1086这个奇怪的接口.你们也可以检查下.如果同样的问题,大家就提出来
看样子每个人的问题不尽相同,一开始我是在mac上用ssr但网速很慢,切换成全局模式勉强能用,后面过了几天直接用不了了,对了,我是用wifi上网,所以我尝试了切换成手机热点,ssr又可以使用了。就在这几天,我的手机热点也不能使我的ssr生效了。但我的手机一直都可以使用,mac是更新了之后才不能用。我改了端口依然无效。 我进入我的vps后删除了原本的ssr,重新配置了一个后,恢复正常,大家可以试试这个方法。
同样的问题,PAC用不了,全局模式可以
mac用户是不是都不重启电脑?我昨天重启了下就好了😂
mac用户一直很好用,使用brew安装的trojan和ss+v2ray共存从未出现过问题
我的一直不行,体现在好像本地的1086或者1080端口不转发,一旦我关闭shadowsocksX的话,倒是立即失败了,不知道哪里有问题
看下端口是否被占用了,不行再换个端口试试
shinyboy notifications@github.com于2020年4月23日 周四16:16写道:
我的一直不行,体现在好像本地的1086或者1080端口不转发,一旦我关闭shadowsocksX的话,倒是立即失败了,不知道哪里有问题
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/shadowsocks/ShadowsocksX-NG/issues/1297#issuecomment-618253590, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABX3GI2RDJPJTRTZJMBFS3TRN72PFANCNFSM4L2N4DGQ .
看下端口是否被占用了,不行再换个端口试试 shinyboy notifications@github.com于2020年4月23日 周四16:16写道: 我的一直不行,体现在好像本地的1086或者1080端口不转发,一旦我关闭shadowsocksX的话,倒是立即失败了,不知道哪里有问题 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1297 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABX3GI2RDJPJTRTZJMBFS3TRN72PFANCNFSM4L2N4DGQ .
没占用,我换了1090http/https代理也是不行,不知道shadowsocksX为啥不转发请求了
没占用,我换了1090http/https代理也是不行,不知道shadowsocksX为啥不转发请求了
帮忙把上一条删除一下,暴露我的地址了,谢谢
没占用,我换了1090http/https代理也是不行,不知道shadowsocksX为啥不转发请求了
帮忙把上一条删除一下,暴露我的地址了,谢谢
好的,我以为你打广告了。。。
没占用,我换了1090http/https代理也是不行,不知道shadowsocksX为啥不转发请求了
帮忙把上一条删除一下,暴露我的地址了,谢谢
好的,我以为你打广告了。。。
这个还是谨慎点好,少惹麻烦。一个是看端口,另一个看防火墙,首先确认你要代理的ip是否可用,ping一下试试,另外看看是不是服务器的问题
没占用,我换了1090http/https代理也是不行,不知道shadowsocksX为啥不转发请求了
帮忙把上一条删除一下,暴露我的地址了,谢谢
好的,我以为你打广告了。。。
这个还是谨慎点好,少惹麻烦。一个是看端口,另一个看防火墙,首先确认你要代理的ip是否可用,ping一下试试,另外看看是不是服务器的问题
端口并没有问题,我用netstat看了,没被占用,服务器端也没问题,windows版本用的很好。。。shadowsocksX的配置很怪异,我不知道它保存在哪里,无法删除的样子
如果win下面没有问题,那应该就是客户端的问题,看下日志吧,不行删除重新安装试试,找不到问题不知道如何解决
遇到同样的问题,我现在系统是big sur 第2个测试版,pac上不了,全局可以上,下面带上错误:
Load failed: 5: Input/output error
2020-07-22 10:24:38.629 ShadowsocksX-NG[18459:51607] Start privoxy succeeded.
2020-07-22 10:24:38.629 ShadowsocksX-NG[18459:51607] run shadowsocks helper: /Library/Application Support/ShadowsocksX-NG/proxy_conf_helper
2020-07-22 10:24:38.674 ShadowsocksX-NG[18459:51607] pac proxy set to off
[INFO] GCDWebServer started on port 8090 and reachable at http://localhost:8090/
2020-07-22 10:24:38.674 ShadowsocksX-NG[18459:51607] run shadowsocks helper: /Library/Application Support/ShadowsocksX-NG/proxy_conf_helper
2020-07-22 10:24:38.707 ShadowsocksX-NG[18459:51607] pac proxy set to auto
切换到ACL模式可以用
遇到同样的问题,我现在系统是big sur 第2个测试版,pac上不了,全局可以上,下面带上错误
我是同一个系统, 只是ssX-NG是自己build的, 工作正常. (?)
遇到同样的问题,我现在系统是big sur 第2个测试版,pac上不了,全局可以上,下面带上错误
我是同一个系统, 只是ssX-NG是自己build的, 工作正常. (?)
刚发现我上面说pac模式不管用,不是当前这个软件的,这个仓库的pac是可以用的,上面那个不能用的,是另一个库,带订阅功能的:shadowsocksX-NG-R8
Describe the bug A clear and concise description of what the bug is.
打开日志看了下,全是timeout,升级macOS之前还是好的,而且其他平台(android,ipad,windows)上全部正常,服务器是自建的VPS,没啥问题。
MAC OS 10.15.4
2020-04-02 21:19:36 INFO: initializing ciphers... chacha20-ietf-poly1305 2020-04-02 21:19:36 INFO: listening at 127.0.0.1:1086 2020-04-02 21:19:36 INFO: tcp port reuse enabled 2020-04-02 21:19:49 INFO: connect to www.google.com:443 2020-04-02 21:19:59 INFO: TCP connection timeout 2020-04-02 21:20:30 INFO: connect to twitter.com:443 2020-04-02 21:20:30 INFO: connect to twitter.com:443 2020-04-02 21:20:40 INFO: TCP connection timeout 2020-04-02 21:20:40 INFO: TCP connection timeout 2020-04-02 21:21:40 INFO: connect to twitter.com:443 2020-04-02 21:21:41 INFO: connect to twitter.com:443 2020-04-02 21:21:43 INFO: connect to www.google.com:443 2020-04-02 21:21:50 INFO: TCP connection timeout 2020-04-02 21:21:51 INFO: TCP connection timeout 2020-04-02 21:21:53 INFO: TCP connection timeout
To Reproduce Steps to reproduce the behavior
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
System and Shadowsocksx-NG version: (please complete the following information):
- OS Version: [e.g. 10.13.1]
- Version [e.g. 22]
Diagnoisis file:
Please first upgrade to the latest version. Then export the diagnosis file and upload it to here.
ss-local.log
Please upload the ss-local.log file here the file is in
~/Library/Logs
- Open 'Advanced Settings -> enable Verbose Mode'
- Continue run
Shadowsocksx-NG
for 5 minutes- Upload the
~/Library/Logs/ss-local.log
here (with or without compress)Application log
Open the
Console.app
and searchShadowsocksx-NG
Copy paste the log hereCrash Log
If the app crashes and pop up a crash log, please copy and paste here
Additional context Add any other context about the problem here.
Describe the bug A clear and concise description of what the bug is.
打开日志看了下,全是timeout,升级macOS之前还是好的,而且其他平台(android,ipad,windows)上全部正常,服务器是自建的VPS,没啥问题。
MAC OS 10.15.4
2020-04-02 21:19:36 INFO: initializing ciphers... chacha20-ietf-poly1305 2020-04-02 21:19:36 INFO: listening at 127.0.0.1:1086 2020-04-02 21:19:36 INFO: tcp port reuse enabled 2020-04-02 21:19:49 INFO: connect to www.google.com:443 2020-04-02 21:19:59 INFO: TCP connection timeout 2020-04-02 21:20:30 INFO: connect to twitter.com:443 2020-04-02 21:20:30 INFO: connect to twitter.com:443 2020-04-02 21:20:40 INFO: TCP connection timeout 2020-04-02 21:20:40 INFO: TCP connection timeout 2020-04-02 21:21:40 INFO: connect to twitter.com:443 2020-04-02 21:21:41 INFO: connect to twitter.com:443 2020-04-02 21:21:43 INFO: connect to www.google.com:443 2020-04-02 21:21:50 INFO: TCP connection timeout 2020-04-02 21:21:51 INFO: TCP connection timeout 2020-04-02 21:21:53 INFO: TCP connection timeout
To Reproduce Steps to reproduce the behavior
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
System and Shadowsocksx-NG version: (please complete the following information):
- OS Version: [e.g. 10.13.1]
- Version [e.g. 22]
Diagnoisis file:
Please first upgrade to the latest version. Then export the diagnosis file and upload it to here.
ss-local.log
Please upload the ss-local.log file here the file is in
~/Library/Logs
- Open 'Advanced Settings -> enable Verbose Mode'
- Continue run
Shadowsocksx-NG
for 5 minutes- Upload the
~/Library/Logs/ss-local.log
here (with or without compress)Application log
Open the
Console.app
and searchShadowsocksx-NG
Copy paste the log hereCrash Log
If the app crashes and pop up a crash log, please copy and paste here
Additional context Add any other context about the problem here.
升级下ss-local和v2ray plugin就可以用了。 最简单就是brew装下shadowsocks-libev和v2ray-plugin(如果你使用它的话), brew list shadowsocks-libev 找到ss-local,替换掉ssX-NG的ss-local, brew list v2ray-plugin 找到v2ray-plugin,替换掉ssX-NG的v2ray-plugin。
Describe the bug A clear and concise description of what the bug is.
打开日志看了下,全是timeout,升级macOS之前还是好的,而且其他平台(android,ipad,windows)上全部正常,服务器是自建的VPS,没啥问题。
MAC OS 10.15.4
2020-04-02 21:19:36 INFO: initializing ciphers... chacha20-ietf-poly1305 2020-04-02 21:19:36 INFO: listening at 127.0.0.1:1086 2020-04-02 21:19:36 INFO: tcp port reuse enabled 2020-04-02 21:19:49 INFO: connect to www.google.com:443 2020-04-02 21:19:59 INFO: TCP connection timeout 2020-04-02 21:20:30 INFO: connect to twitter.com:443 2020-04-02 21:20:30 INFO: connect to twitter.com:443 2020-04-02 21:20:40 INFO: TCP connection timeout 2020-04-02 21:20:40 INFO: TCP connection timeout 2020-04-02 21:21:40 INFO: connect to twitter.com:443 2020-04-02 21:21:41 INFO: connect to twitter.com:443 2020-04-02 21:21:43 INFO: connect to www.google.com:443 2020-04-02 21:21:50 INFO: TCP connection timeout 2020-04-02 21:21:51 INFO: TCP connection timeout 2020-04-02 21:21:53 INFO: TCP connection timeout
To Reproduce Steps to reproduce the behavior
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
System and Shadowsocksx-NG version: (please complete the following information):
Diagnoisis file:
Please first upgrade to the latest version. Then export the diagnosis file and upload it to here.
ss-local.log
Please upload the ss-local.log file here the file is in
~/Library/Logs
1) Open 'Advanced Settings -> enable Verbose Mode' 2) Continue runShadowsocksx-NG
for 5 minutes 3) Upload the~/Library/Logs/ss-local.log
here (with or without compress)Application log
Open the
Console.app
and searchShadowsocksx-NG
Copy paste the log hereCrash Log
If the app crashes and pop up a crash log, please copy and paste here
Additional context Add any other context about the problem here.