-
Notifications
You must be signed in to change notification settings - Fork 16.4k
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
Fails to start with a non-UI error #3333
Comments
pls delete the config(gui-config.json) file and try again. |
Moved This message showed up at the very start and then appeared with the 'Edit server' window. After putting in server settings, the app connected to the server and worked fine, a new However, the same error messages shows up upon:
Clicking 'Help' -> 'Show Logs…' crashes the app with an UI error message: |
Off-topic (?)I looked at the original Its last modification date is July 9, 2022, 23:40:49 (UTC+3), same as Last events in
Weirdly enough, the app doesn't fill this log anymore, despite connecting to the server now. Don't if any of this would be relevant to the issue at hand but sharing it just in case. |
This may related to NLog.config, check it. |
You may try this version https://github.com/eebssk1/shadowsocks-windows/releases/tag/4.4.1.1 |
Yeah, it's empty and edited on the same as
This version works fine but I'd rather wait for an update of this repository with your PR. |
FYI: deleting the app entirely and installing it again seemed to eliminate the problem for now, but I'd prefer to keep the issue open until #3335 is included in a release. |
Describe the bug
The app suddenly gives a non-UI error each time I try to start it:
Environment
Steps you have tried
ss_win_temp
What did you expect to see?
The app running as normal.
What did you see instead?
The error message quoted in the description.
Config and error log in detail (with all sensitive info masked)
shadowsocks.log
has not been filled since the last time shadowsocks worked as normal.The error message:
The text was updated successfully, but these errors were encountered: