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

[bug] After updating to Beta 2.2.0, the docks are no longer configurable. #416

Open
1 task done
jensm-sys opened this issue Dec 14, 2024 · 2 comments
Open
1 task done
Labels
bug Something isn't working

Comments

@jensm-sys
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

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

@jensm-sys jensm-sys added the bug Something isn't working label Dec 14, 2024
@github-project-automation github-project-automation bot moved this to Reported in Bug reports Dec 14, 2024
@zehnm
Copy link

zehnm commented Jan 20, 2025

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/)

@jensm-sys
Copy link
Author

jensm-sys commented Jan 20, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Reported
Development

No branches or pull requests

2 participants