Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] Add support for SOCKS proxy #859

Open
thanhminh-vht opened this issue Nov 28, 2024 · 1 comment
Open

[Feature request] Add support for SOCKS proxy #859

thanhminh-vht opened this issue Nov 28, 2024 · 1 comment

Comments

@thanhminh-vht
Copy link

Thanks for the fantastic work on MQTT Explorer—it’s such a handy tool!

I’d like to request support for SOCKS proxies. This feature would make it easier to use MQTT Explorer in setups where a SOCKS proxy is required, such as in restricted networks, for enhanced privacy, or when accessing brokers through specific routing.

From what I’ve seen, the MQTT.js library used by MQTT Explorer already supports SOCKS proxies. There’s a closed issue in the library with an example of how to configure it, so implementation should be straightforward.

Adding this feature would make the tool more flexible and capable in diverse network environments.

Thanks for considering this!

@thanhminh-vht
Copy link
Author

Following up on the SOCKS proxy feature request, I’d like to propose some implementation details for consideration:

  • Proxy settings should be configurable globally and per MQTT connection profile.
  • In the connection profile settings, there should be a radio buttons to select the proxy type:
    • None (direct connection).
    • Global proxy settings (default).
    • Specified proxy (override global settings for this profile).

This approach would make the feature flexible for users with diverse network needs while keeping the configuration straightforward.

Let me know your thoughts!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant