Welcome, Petrus, and thanks for adding your servers.
If you refresh the page, I think you’ll see your “net speed” (really relative weights) has changed as soon as you selected the new value. It’s just a minor UI bug that the reported value above the dropdown isn’t updated.
It was a long time ago I had servers here, but a long time ago I haven’t give them to the pool
About the UI bug, I think it’s only related to Firefox… I’ve tried with a Chrome-like, it’s ok (my bad, I haven’t thought to test before making noise here… sry).
It does not update for me either. I also use Firefox. It did in the past. I tried reloading the page after setting the speed and it still just displayed the old speed.
When that happens to me, it usually means the loaded page has become stale. Reloading the page, and then not too long thereafter making the change has so far always worked for me.
Good point, @MagicNTP. Whenever I want to change the net speed, I’m now in the habit of refreshing the page first, as I tend to have it on an open tab that could be days old.
Hmm, I am just having the issue described in this thread myself, and for the first time I remember, the “refresh-before-change”-trick does not work for me, either.
I.e., the value shown on the non-extended drop-down menu (don’t know the technical name for it, the one that normally reads “Set connection speed”) shows the desired updated value, but that is not reflected in the value shown next to the “Net speed:” text.
Page refresh before the update doesn’t change the behavior. Page refresh afterwards does not show the updated value, either (could have been that the updated value is actually registered, just the immediate feedback not working).
Last night I tried the refresh-before-change and it made it work on the beta site, but not the production site. This morning it works on both. I don’t know if something changed or the server side, or if Firefox was caching something even through the refresh.
I haven’t changed anything since last weekend (been traveling). I’ll have to do another round of debugging with not-Safari or Chrome; or maybe redo again how those interactions work since the setup I had made obviously is way flakier than I intended.