¶ Fix: Connection issue between the background service and the user interface after an application restart
An issue has been fixed where, after restarting the Weble Connect application, the link between the background service and the user interface could become inconsistent.
When the application was restarted from within the interface, the previous session was not fully released. Parts of the old session kept running in the background and continued to hold the internal communication channel used to talk to the background service.
As a result, after a restart:
- The interface could stop being notified when the background service reconnected. The service appeared as disconnected in the interface, even though it was actually running and communicating normally.
- Each successive restart made the situation worse, as more leftover sessions accumulated and competed for the same communication channel.
- Only a full close and relaunch of the application restored normal behavior.
The restart procedure now properly shuts down the internal communication layer before reloading the application. The communication channel is cleanly released, so the new session takes over immediately and exclusively.
After this fix:
- The interface correctly reflects the live state of the background service at all times, including after one or several restarts.
- Service reconnections are detected and displayed reliably.
- No leftover sessions remain in the background after a restart.
No action is required. The fix is included in this release and applies automatically. If you previously worked around the issue by fully closing and relaunching the application, this is no longer necessary.
- feat: Adding new menu "settings". The settings menu lets you select the server and the server connection mode.
- fix:
Group dashboards did not display the host name correctly.
- fix: OTP request was not made correctly.
- fix: When a tunnel was ready, the static IP address was not displayed correctly in DHCP mode (bridge).
- fix: When the static ip address of a tunnel is already in use, an error is now displayed and the tunnel is closed.
- feat: You can now force a PLC's web page to be opened via the proxy by clicking on the node's id in the list of nodes.
- fix: Websocket headers are now set correctly on
Weble Connect Proxy
- feat:
HTTP connection (group dashboard / dashboard / host connection / host) are now open on default browser instead of Weble Connect Proxy
- feat: Possibility to open session on browser allowing the user to auto-login into the cloud platform.
- feat: Adding VPN on demand vpn-on-demand for dashboards / group dashboards and hosts
- fix: Filter in hosts table
- fix: Removing
resend code button when OTP is selected
- fix: Filter in dashboards and group dashboards table
- fix: 2FA request was hiding header making the windows non-movable and non-closable
- feat: UI improvements
- feat: Adding support for service connection (RDP/SSH/VNC) allowing dashboards / group dashboards access with native client weble-connect
- fix: Adding 2FA modale when session expire