Connecting to Website via Socks5

Hello,

Thank you for reaching out to Devolution Support.

That’s a great question! I will contact the developers regarding your issue. In the meantime, would it be possible for your colleague to send you an export of the entries or grant you access to them if you are using an advanced data source and see if the issue reoccur?

Best regards,

Hello,

The developer has rewritten the web proxy to address several issues. These changes will be included in version 2024.3.9, which is scheduled for release shortly after the holiday.

Please note that the improvements require macOS 14 or later.

Best regards,

Thank you for your reply. I am very happy that you will come up with a solution. If you tell me what holiday you mean I would be really grateful.

Hi, another idea.
I would love to join in as beta tester for this version.

Hello

Thanks for your patience as the majority of our staff return from holidays this week.

First, to explain a bit of background: historically, Apple never offered a way to configure a proxy for an individual embedded web view, The only option they gave was to configure a system-wide proxy. We have a workarounds in RDM that "kind of" enables us to do this, but it's built on top of deprecated APIs and supports certain feature in the application to a limited extent, but it's definitely not a general purpose solution. This is the reason that RDM doesn't expose the "proxy" options for website entries, like RDM Windows does.

One of the ways we do enable a proxy for an embedded website is with an SSH tunnel, I've just tried this on my side:

• Create an SSH Tunnel entry pointing to a host that can access the website, with credentials properly filled and etc
• Set the outgoing tunnel settings to "Dynamic", using 127.0.0.1 as the local address and I left the port at default (which is 3390)
• Create a new website entry pointing at the website; in my case I used the IP address as I'm not sure how DNS functions in this scenario. This obviously required me to skip through the certificate warning on the site itself; we can look further at what's needed here if that's an issue
• In the website entry, under VPN/Tunnel/Gateway choose "Always connect" with type "SSH Link", and in "Settings", point to the SSH Tunnel entry you created earlier and ensure "Use secure gateway" is checked

Now launch the website entry. The SSH Tunnel should open first, and then the website entry should launch and connect via the tunnel.

Now: I just tried this on my side with an iLO5 management site and it didn't work, I just get a white screen. This is because of my original point - historically we had no good way to set a proxy for an individual embedded website and had to use a deprecated APIs which don't play nicely with the iLO site.

However, the 2024.3.9 update for RDM Mac has a rewritten proxy implementation. Assuming you have at least macOS 14, and ensure that in Settings > Types > Others > Web the setting "Use Legacy Engine" is set to no, I believe this should work.That update should be available later today all being well, and if not at some point later this week.

I'd encourage you to try it and let me know if it works, or what problems you encounter.

Given that we have a way to implement this properly now, we can likely investigate adding the proxy settings directly to the website entry like on RDM Windows and streamline this whole process.

Please let me know if something isn't clear or you have further questions

Kind regards,

Works wonderful! Thank you very very much! I am really happy with the solution.

Hello

Good news! Thank you for the follow up and don't hesitate if you have further questions or comments.

Kind regards,