Yes, this was already reported by a couple of other users on this forum and Github.
A fix was merged a couple of hours ago and is available in the candidate channel (on top of LXD 4.6). This should sort it out and will be in stable on Monday/Tuesday.
If you’re in a hurry, you can switch to candidate in the meantime with snap refresh lxd --candidate, note that you should remember to do snap refresh lxd --stable later next week to get back to stable.