-
Notifications
You must be signed in to change notification settings - Fork 26
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
nyx Error: "Unable to save configuration ([551] Unable to write configuration to disk.)" #20
Comments
Hi T0rr0, sorry about the delay. This looks to be arising because your torrc has "%include" entries which would get overwritten. Tor raises this error at the following when we don't provide a 'force' flag... https://gitweb.torproject.org/tor.git/tree/src/feature/control/control_cmd.c#n436 I should change Nyx to do the following...
I won't get to this for a while. In the meantime I'd suggest managing your torrc by hand. Thanks for reporting this! |
I got the same error, but I don't have │ 244 ## Configuration options can be imported from files or folders using the %include
│ 245 ## option with the value being a path. This path can have wildcards. Wildcards are
│ 246 ## expanded first, using lexical order. Then, for each matching file or folder, the following
│ 247 ## rules are followed: if the path is a file, the options from the file will be parsed as if
│ 248 ## they were written where the %include option is. If the path is a folder, all files on that
│ 249 ## folder will be parsed following lexical order. Files starting with a dot are ignored. Files
│ 250 ## on subfolders are ignored.
│ 251 ## The %include option can be used recursively.
│ 252 #%include /etc/torrc.d/*.conf Here is the messaged printed to syslog when the error occur.
The same error happens on my other relay, in this relay, the error log is
Looks like my tor process is not running in root, so they couldn't write into the |
Got this error message when I want to save (as root) the torrc after editing the config in nyx.
The text was updated successfully, but these errors were encountered: