You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating to Beta 2.2.0 and 2.2.1, both of my docks were no longer accessible. Unfortunately, the attempt to reconfigure them according to the recommendations (RC version 2) with the now required port number failed. Since it was not possible to configure the two docks via the UI.
It was possible to set up a new dock. To keep track of the docks and their correct configurations, I deleted the ones that no longer worked.
How to Reproduce
no idea
Expected behavior
During the migration to version 2.2.0, the existing ones were apparently not adopted correctly and the wrong rights were bound to the configuration items.
System version
2.2.1
What part of the system affected by the problem?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is this still an issue?
Since you mentioned port number, I assume you tried a manual configuration, or did the automatic configuration with discovery not work?
There is an open dock configuration issue in the web-configurator, from #438 (comment):
We have an open issue in the Dock configuration of the new web-configurator: the custom IP field shows the currently resolved Dock address. This field should only be set if a custom address was provided. This will soon be fixed in an update.
At the moment you could use this as a "feature", if the custom IP field already shows an URL with an IP address (e.g. ws://192.168.1.234:946/): click into the field and press enter. This will save the resolved address as a custom address.
To revert: delete the URL to make the field empty and press enter. The field will be updated with the local mDNS address (e.g. ws://uc-dock-8c4b14aa0c78.local:946/)
As part of the update process (update to beta 2.2.0), I lost communication due to a change in the dock configuration. After deleting the docks, the automatic configuration with Discovery then worked.
Immediately after the software update, I was unable to change the configuration manually. So I deleted the entire dock configuration and reconfigured my two docks.
Is there an existing issue for this?
Description
After updating to Beta 2.2.0 and 2.2.1, both of my docks were no longer accessible. Unfortunately, the attempt to reconfigure them according to the recommendations (RC version 2) with the now required port number failed. Since it was not possible to configure the two docks via the UI.
It was possible to set up a new dock. To keep track of the docks and their correct configurations, I deleted the ones that no longer worked.
How to Reproduce
no idea
Expected behavior
During the migration to version 2.2.0, the existing ones were apparently not adopted correctly and the wrong rights were bound to the configuration items.
System version
2.2.1
What part of the system affected by the problem?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: