Supervisor is dead - Questions

So, I have an instance of HomeAssistant running on an Intel NUC5, it’s currently on 2022.4.6 for HA and the OS is 2 upgrades behind. Right now, the HA web interface is up and currently all my integrations are apparently running.
Here’s my issue, I made some automation changes, reloaded automations a few times, and while going thru my configuration.yaml, I removed some old stale configs that were throwing errors and warnings in the logs. Prior to restarting HA, I checked the config with the button. It’s telling me I have an error in my config in the logging section. I can’t restart because of the error in the config. When I go to edit the config files, I can’t get to them because of " Unable to load the panel source: /api/hassio/app/entrypoint.js." So, I tried the Terminal. Same error - " Unable to load the panel source: /api/hassio/app/entrypoint.js."
Examining the logs reveals Client error on /core/info request Cannot connect to host 172.30.32.2:80 ssl:default [Connect call failed (‘172.30.32.2’, 80)]
10:39:05 AM – (ERROR) Home Assistant Supervisor - message first occurred at May 23, 2022, 7:33:49 PM and shows up 11382 times
Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:default [Connect call failed (‘172.30.32.2’, 80)]
10:38:53 AM – (ERROR) Home Assistant Supervisor - message first occurred at May 25, 2022, 2:47:02 PM and shows up 14 times
Failed (re-)subscribing to: uuid:25491ec2-d97a-11ec-8741-b75a17d4c611, reason: UpnpConnectionError(“Cannot connect to host 172.16.25.140:61251 ssl:default [Connect call failed (‘172.16.25.140’, 61251)]”, None)
May 22, 2022, 9:07:17 PM – (WARNING) /usr/local/lib/python3.9/site-packages/async_upnp_client/profiles/profile.py - message first occurred at May 21, 2022, 11:00:02 PM and shows up 7 times
After further investigation , nothing I do can contact the supervisor.

I CAN power cycle this box. I should mention that the box is 900 miles away and physically accessing it is impossible at this time. My question is, will the interface come back with a restart considering the logging misconfiguration? Also, is the supervisor involved in the configuration check - as in could the supervisor being unreachable cause the configuration ‘error’?
I’d really hate to power cycle this box and lose the functionality it currently has. I’d have to face the wrath of the wife!
Is there any other way to restart the docker processes?