Ix-apps deleted, need help restoring/resetting

i have 2 pools, data and backup. i was removing some old user folders from when i was on core (the ones that are auto generated for every user that logs in) via cli from data and also backup (backup is replication target), and idk what the hell i did but somehow cleaned out the ix-apps dataset even though 1) data is my apps pool and 2) my path was 100% inside backup (i was cd’d into /mnt/backup). either way everything including apps were running fine despite this until i rebooted, now i cant refresh the catalogue:

failed to sync TRUENAS catalog: [EFAULT] Failed to clone 'https://github.com/truenas/apps' repository at '/mnt/.ix-apps/truenas_catalog

and trying to do it via cli using

cd /mnt/.ix-apps
sudo git clone https://github.com/truenas/apps.git truenas_catalog

just results in

fatal: unable to access 'https://github.com/truenas/apps.git/': Could not resolve host: github.com

which makes no sense since ive changed literally nothing network wise on anything. unsetting or changing the apps pool does not help, and neither does restoring snapshots of the ix-apps folder and its subfolders. i also have all of my apps in individual datasets on the data pool rather than the default. most of the apps still start successfully and apparently work, but scrutiny crashes and tailscale stays on deploying forever which does hint at a network problem im guessing, but again ive changed literally nothing. ive also made sure to check and my network settings including dns servers are as they were, nothing has changed on my router, and a vm is able to go online without issue.

anyone have any ideas???

well i dont think i did anything that i havent already described, but the system decided that the last power cycle i did was in fact the correct length or timing or something, because now everything is all good now and my apps situation is back to normal. :person_shrugging:. ill post again if this becomes not the case yet again…

Seems you had a temporary DNS failure.

more than likely i suppose, but like i said i changed literally nothing and no other device on my network was affected including a vm running on the server, so if it was a dns issue it was exceedingly strange.

apparently this was an issue caused by the bridge for my vm or just good ol realcrap screwery™ with bridging because removing the bridge and just assigning the vm its own nic (i have dual onboard) has completely fixed the issue.