Proxifyre doesn't work without logs folder and "" mask doesn't work

[Ekoeden]

I really like this program, but in version 2.0.1 I encountered a problem.
I set the log level to "Error" and nothing worked (even though the old version worked). But then at some point during the experimentation I set the logs to All and the connection worked.
After that I returned the logs to "Error", but left the "logs" folder - the program works. If I delete the folder, the connection breaks again.

Also, the mask "appNames": [""] for socksify all application traffic doesn't work for me. And at the same time, chr works for chrome.exe.

P.S. I reinstalled Windows Packet Filter and Visual Studio Runtime Libraries before trying the new version.

[wiresock]

Thanks for your feedback and for the detailed description — much appreciated.

I tried to reproduce the issue you described using the following configuration (credentials redacted):

{
    "logLevel": "Error",
    "proxies": [
        {
            "appNames": [""],
            "socks5ProxyEndpoint": "your.proxy.server:port",
            "username": "yourUsername",
            "password": "yourPassword",
            "supportedProtocols": ["TCP", "UDP"]
        }
    ]
}

In my tests with version 2.0.1, proxification worked as expected even with "logLevel": "Error", although no log file was created (as intended at that level). Once I set logLevel to "Info", the log file was created and everything continued to function normally.

One thing I recommend is to try running the program as Administrator — this is important for process lookup functionality and may also influence whether log folders can be created properly.

Regarding the "appNames": [""] mask — that should match all processes by default. If it’s not working on your setup but does for others like "chrome.exe", please double-check that the program has sufficient permissions to monitor the target applications.

Let me know if you’re still seeing the issue even with elevated privileges.

[Ekoeden]

Thank you for your reply.
I double-checked everything and ran it as administrator, but the problem persists.
Since everything works as expected for you, I think the problem may be in my operating system. I have made many settings and, for example, many Windows services are disabled.
Are there any important settings or Windows services that are likely to affect the operation of the program?

[wiresock]

Thanks for the follow-up.

Given the system modifications, it’s possible that a disabled service (e.g., WFP, BFE, NLA, or IP Helper) is interfering. If possible, set "logLevel": "All" in the config, reproduce the issue, and share both the log and pcap files. If a log file is generated, it might provide useful clues.

Also, if you can, try running the app on a clean Windows setup or VM to see if the issue persists.