SOLVED Debian 10 VM broken after upgrade to "TrueNAS TrueNAS-12.0-STABLE - Release Train for TrueNAS 12.0 [release]"

[Apollo]

I thought I was going to update within TrueNAS 12.0, but found out too late this was a TrueNAS 13 update.
Anyway, Upon restart (update) I no longer have access to my Debian 10 VM.
As a result I reverted to my previous TrueNAS 12 version and still can't start my VM by connecting to VNC.

This is quite of a stepdown as this VM is being used for my day to day work (as in making money for a living kind of thing).

Here is a screenshot of the issue:

 

[Apollo]

PS: When I created the Debian 10 VM, I knew the path of the dataset I had shared with the VM. Now, it is complete oblivion (meaning the VM or the TrueNAS settup doesn't provide details on which of the dataset is supposed to be accessible by the VM.

???

Number 13 seems to be the unlucky number. as in Friday 13th.

 

[Apollo]

Update: Out of curiosity, I tried accessing VNC with Chrome and I was able to start Debian without errors. So for some reason, Firefox or some other settings/update is causing this issue.