Activity for Ben Bucksch
-
Ben Bucksch modified a comment on ticket #927
Workaround, until the default config is fixed: Open the config.txt file with Notepad++ as administrator Select Edit | Format File ending | Unix (LF) Comment out the log file location setting, by adding a # at the start of the line: #logfile privoxy.log Save Start Privoxy
-
Workaround, until the default config is fixed: Open the config.txt file with Notepad++ as administrator Select Edit | Format File ending | Unix (LF) Comment out the log file location setting, by adding a # at the start of the line: #logfile privoxy.log Save Start Privoxy
-
Workaround, until the default config is fixed: Open the config.txt file with Notepad++ as administrator Select Edit | Format File ending | Unix (LF) Comment out the log file location setting, by adding a # at the start of the line: #logfile privoxy Save Start Privoxy
-
The problem are file permissions to the log file. Privoxy is installed by the Windows installer by default in the "C:\Programs (x86)\Privoxy\" folder, and files in that directory can only be changed by admins. By default, the log file location is privoxy.log in the same install directory. So, only applications running as admins can write to the log file. This is what is causing the bug. Privoxy logging isn't enabled by default That statement is not correct. If I install Privoxy on Windows with the...
-
The original problem here was caused by wrong file endings in the config file. If you see the error message: Privoxy Error: Fatal Error: init_error_log(): can't open logfile: '\privoxy.log' (without the +AA0- or similar) then you might be running into bug https://sourceforge.net/p/ijbswa/bugs/927/ Please see there for the solutions.
-
The original problem here was caused by wrong file endings in the config file. If you see the error message: Privoxy Error: Fatal Error: init_error_log(): can't open logfile: '\privoxy.log' (without the +AA0- or similar) then you might be running into bug https://sourceforge.net/p/ijbswa/bugs/927/ Please see there for the solutions.
-
The problem are file permissions to the log file. Privoxy is installed by the Windows installer by default in the "C:\Programs (x86)\Privoxy\" folder, and files in that directory can only be changed by admins. By default, the log file location is privoxy.log in the same install directory. So, only applications running as admins can write to the log file. This is what is causing the bug. Privoxy logging isn't enabled by default That statement is not correct. If I install Privoxy on Windows with the...
1