since the update the interface has been kind of messed up I have tried on several browsers it seem to work fine on machines that have the older interface cached
but on new machines or after clearing the cache this seems to be the case
I have tried edge, chrome and firefox on windows 11 all do the same
java install is upto date
it has also happen on linux mint 22 under firefox I have not had a chance to test much more on linux yet.
if there are any notification those have to be dismissed before any of the shortcuts can be used
I am also on 25.11. I tried with a new profile in abrowser (based on Firefox 143) and in icecat (based on Firefox 128.14 esr), so that it is not using cached data, and I did not notice anything changed like in your picture. Actually, your picture looks like what I sometimes saw when my cache was not refreshed after an upgrade.
Or could it have any relationship with installed apps, like Home Assistant (I also don’t have Deluge and Nextcloud)?
25.11 does not have any changes that could cause this issue. So, we can consider other possibilities too.
Using .lan TLD is not often tested. Could you try with the .local address of FreedomBox instead? Do you have addons that could effect this? Try safe mode of browsers without addons.
Does typing the failed URL into the browser address bar load the resource properly? If so, this could related to content security policy or content warning.
What reason does the Networks tab of developer tools show for this failed URLs?
I have a dns server on my network serving this domain
but I can try it it also doesn’t work well across my vpn so I’d prefer not use it if at all possible but it is worth testing
The .local domain is available in FreedomBox by default as freedombox.local this address will be resolved by mDNS queries on platform that support it (mostly non-Windows). This name can be changed in System → Name Services if desired.
ok I will try this when I get home as I can’t use anything .local over my vpn
but should it not resolve this stuff if it works with .local and not the full domain name doesn that not indicate a differnt problem
Further note it works fine with my public ip and domian with port forwarded through my firewall I am not to sure where the problem lies I am starting to think more along the lines firewall