Now the problem is, that all modern browsers have a mechanism in place, which, after starting of the application forks away a browser instance in then immediately terminates the started program. RoyalTS therefore then immediately closes the session again and the browser ends up in a 127.0.0.1:xyz URL, but RoyalTS does not provide the port forward on that port.
How to solve that one?
Right now I use a cmd script which starts the browser and does not terminate itself. Not a nice workaround, but it works for now. Any suggestions?
yes, I’ve also disabled the process tracking. Unfortunately without success.
Can you try to configure any modern web browser (Firefox, Chrome, Edge) as external application with SSH forwarding and share a working configuration? I did not succeed.
One quick question though: is there a reason you can’t just use the Chromium based web page plugin with Secure Gateway / Proxy configuration? Setting this up will essentially direct all browser traffic through the SSH tunnel.