You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just wanted to recreate issue, maybe first one was obsolete but it still persists no matter what you are putting in process name (full path or just name itself) even in logs nothing is happening (although processes themselves are being recorded in logs) with process itself it's just there but no message regarding it's work. Program just detects an app but do nothing with it!!! On windows everything works as expected. Have somebody managed to fix an issue, may be there's some sort of custom config or something?
The text was updated successfully, but these errors were encountered:
That's truly interesting: I tried different client: v2rayN and faced the same issue on linux))) And then, out of curiosity, I compared sing-box-vpn.json config for windows and for linux and they actually differs in one json key. On windows there's no mentioning of process_name but on linux there it is (on windows and linux there's config file with all your processes listed, that's why I don't get why sing-box config differs). I don't understand why the same version of sing-box core has different implementation in linux and windows since this json is only wrapper for underlying mechanisms. Then I tried to delete this key from config and see what will happen. Spoiler allert: it changed nothing... which is strange. Maybe someone could explain why?
Just wanted to recreate issue, maybe first one was obsolete but it still persists no matter what you are putting in process name (full path or just name itself) even in logs nothing is happening (although processes themselves are being recorded in logs) with process itself it's just there but no message regarding it's work. Program just detects an app but do nothing with it!!! On windows everything works as expected. Have somebody managed to fix an issue, may be there's some sort of custom config or something?
The text was updated successfully, but these errors were encountered: