Open 0XC7R opened 1 day ago
I don't think it really has much to do with proxychains however I thought I would mention it just in case including anyone who may encounter this in the future.
that's a known issue - search for sandbox in the issues. though it's nice that you document a workaround, which may be useful for some.
that's a known issue - search for sandbox in the issues. though it's nice that you document a workaround, which may be useful for some.
Interesting. Kind of a flaw but is nothing really.
The work around doesn't always work for some apps like I said which means you would need to find an additional work around if you cannot use flatpak to install the same application. Theyre the only two workarounds I have really found. I have no clue why the deb install of apps like discord works differently compared to flatpak installation.
Up to you but you could add this issue to the read me or I can make a pull request to add it.
Config and other information has not changed since my last issue post which is here: https://github.com/rofl0r/proxychains-ng/issues/585
I will add new config and other edits if needed in the future.
Not sure if it is either electrum or proxychains related issue. When running an app that uses electrum like discord, signal etc you will be required to add
--no-sandbox --in-process-gpu
at the end of the target if you want to route its traffic through proxychains and have it boot successfully. If you do not parse the workaround above then the process will just throw an error and exit which is supplied at the bottom and in the screenshot belowAlthough this work around does not always work with some applications like discord as I had to flatpak install it for it to work compared to the debian install.
I will provide a screenshot below to help show the issue: The second time I had run signal with proxychains and also parsing the workaround mentioned above is a successful start and run. The above is pretty obvious.
Console output in event of error: