I had this issue with the previous version of firmware, it was fixed by a reboot, oddly enough...