I tested this with AP 4.2.0, 4.2.1, and an instance of 4.2.3 that had been upgraded to 4.2.4.
In each instance, when I add a new configured mount point, and click KNIME Serverspace, I see a brief flash of a window configuration that then leaves Credentials grayed out and mount ID blank, with Server Address: http://localhost:8080.
I started a server instance (4.11.2) and changed “localhost” to the IP address of the server, then clicked down to Mount ID, and it reached out to the server address and autopopulated the Mount ID. I clicked ‘OK’ and it took me back to the list of configured mount points. I clicked ‘apply and close’, and it then showed the new listing in the KNIME Explorer window.
I believe that the initial graphics “glitch” you’re seeing is the window defaulting to localhost:8080 as the server address, attempting to reach out automatically, the window shifts to the correct display boxes for that option, and then it fails to detect a server at localhost:8080 and shifts back, so fast that it looks like a visual glitch. The functionality of adding a server is working as expected.
That being said, I have created defect AP-16119 to track this issue and see what can be done to correct it going forward.
Please let me know if you have any additional questions or concerns.