jks

Yeah, if you move too far vertically while dragging and cross one of the invisible canvas elements the dragging will stop prematurely. Fix in today's update..

Yeah, if you move too far vertically while dragging and cross one of the invisible canvas elements the dragging will stop prematurely. Fix in today's update..

Yeah, if you move too far vertically while dragging and cross one of the invisible canvas elements the dragging will stop prematurely. Fix in today's update..

Yeah, if you move too far vertically while dragging and cross one of the invisible canvas elements the dragging will stop prematurely. Fix in today's update..

Okay, I've looked at this for a long time now and I think I see what's happening.

I first disabled the Kiwi built-in DUC client on both Arctic and Kong and made sure there was no DUC process running on the Kiwis.
Then I went to noip and manually set the target ip to 213.161 ... (via the "modify" button) for both Arctic and Kong and observed that the "last update" time shown on that page (the last time noip received an update request from any DUC client with the proper credentials) was 21:00 CET.
So far, so good.
But at 21:19 someone sent an update to noip for Kong with an ip of 77.222 ... The 21:00 update for Arctic remained from before.

So the issue is who is doing this? A check of the Kiwis again showed no DUC clients running.

Did you ever download from noip a DUC client to run on a Windows or Linux box that might still be running with the 77.222 address configured?