Host on a Server?

[vicatcu]

Is it possible to run this software on a headless server so that it exposes itself on a particular port using some kind of authentication / login scheme?

[thomasnordquist]

Related to #171, #172 and #64.
In theory yes, but it would take quite some time to do it in a feature-complete and secure manner.

Necessary changes

• I already started once replacing the electron IPC interface with socket.io (websockets).
• The application currently has a few points where it depends on electron, these can, of course, be refactored (mostly the SSL certificate selection).
• Security: The backend and frontend need some kind of "login" which secure the websocket.
• Browser compatibility: a few polyfills are required for Support other Browser engines #64

Nice to have

• Feature: app state restoration (server would need to maintain a copy of the tree)
• Security: Browser should have no access to the broker PSK / client certificates

https://github.com/thomasnordquist/MQTT-Explorer/compare/mqtt-explorer-as-a-module

[Maintraxx]

+1

[klejejs]

Any updates on this? Is there still a plan to implement this?

[cyrilphoenix71]

Any updates ? :)

[Maintraxx]

Any updates ? :)

[MaxVRAM]

I run my home server headless and I was hoping this would be a web interface, not a desktop app. I don't like to install anything server related on my desktops, so I'll hold off until it gets a web UI. Sounds like a great MQTT solution though!

[jsternadel]

What about pushing the authentication mechanism off to something like Authelia? It wont be a turn key solution for the end user but its secure and works with common reverse proxy providers. Personally, I would be quite pleased if more apps required a mfa auth provider with at least TOTP as a prerequisite.

Even home environments are starting to become quite complex with several services open to the public internet. The ability to shutdown a single bad actor across all services is probably an eventual reality.

[Smeagolworms4]

For information

#306 (comment)