lostbad.blogg.se - Shadowsocks for mac download

If the app crashes and pop up a crash log, please copy and paste hereĪdd any other context about the problem here. Open the Console.app and search Shadowsocksx-NG Upload the ~/Library/Logs/ss-local.log here (with or without compress).

Continue run Shadowsocksx-NG for 5 minutes.Open 'Advanced Settings -> enable Verbose Mode'.Please upload the ss-local.log file here the file is in ~/Library/Logs Version ShadowsocksX-NG 1.7.1(1)ĭyld: Library not loaded: from: /Users/USERNAME/Library/Application Support/ShadowsocksX-NG/ss-local-latest/ss-local.OS Version: macOS 10.14 Mojave Developer Beta 6.System and Shadowsocksx-NG version: (please complete the following information): If applicable, add screenshots to help explain your problem. 如题目，在 Mojave 中启用 ShadowsocksX-NG 后所有网络无法访问，Safari 显示无法连接到服务器Ī clear and concise description of what you expected to happen. The project is released under the terms of the GPLv3.Ī clear and concise description of what the bug is. ContributingĬontributions must be available on a separately named branch based on the latest version of the main branch develop. So after you quit the app, the ss-local might be still running.Īdded a manual mode which won't configure the system proxy settings, so that you could configure your apps to use the SOCKS5 proxy manually.

Ss-local is run as a background service through launchd, not as an in-app process.

Import server profile by scan QRCode on screen.

Import server profile urls from pasteboard.

Share your server profiles by qrcode or url.

Could update PAC by download GFW List from GitHub.

Embed kcptun, simple-obfs and v2ray-plugin. Then I have rewrited the GUI code in Swift. So there is only some source code related to GUI left. Run ss-local executable as a Launch Agent in the background. Now I just copied the ss-local from Homebrew. So it's hard to update the ss-local version. It's crazy to maintain dependencies of ss-local. It's hard to maintain the original implementation as there is too much unused code in it. Next Generation of ShadowsocksX Why a new implementation?