Trying to figure out why I have this error near end of startup.

Jul 8 17:30:29 unraidserver avahi-daemon[2350]: Service "unraidserver" (/services/smb.service) successfully established.

Jul 8 17:30:30 unraidserver root: <anonymous_script>:1

Jul 8 17:30:30 unraidserver root:

Jul 8 17:30:30 unraidserver root:

Jul 8 17:30:30 unraidserver root: SyntaxError: Unexpected end of JSON input

Jul 8 17:30:30 unraidserver root: at JSON.parse (<anonymous>)

Jul 8 17:30:30 unraidserver root: at ApiStateConfig.parseConfig (file:///usr/local/unraid-api/dist/assets/plugin.module-_9apkWTJ.js:971:32)

Jul 8 17:30:30 unraidserver root: at async loadApiConfig (file:///usr/local/unraid-api/dist/assets/plugin.module-_9apkWTJ.js:1071:24)

Jul 8 17:30:30 unraidserver root: at async PluginService.listPlugins (file:///usr/local/unraid-api/dist/assets/plugin.module-_9apkWTJ.js:2253:34)

Jul 8 17:30:30 unraidserver root: at async PluginService.importPlugins (file:///usr/local/unraid-api/dist/assets/plugin.module-_9apkWTJ.js:2219:32)

Jul 8 17:30:30 unraidserver root: at async PluginCliModule.register (file:///usr/local/unraid-api/dist/assets/plugin.module-_9apkWTJ.js:12650:25)

Jul 8 17:30:30 unraidserver root:

Box is accessible and seems to be running but still trying to determine reason for extreme latency on Dockers in particular.

Now I am getting this for the webui:

I cannot click on dashboard or main.

Also, noticed GlutenVPN is auto starting even though auto start is set to OFF.

Logs show this:
Jul 8 17:51:54 unraidserver kernel: veth5b6058e: renamed from eth0

Jul 8 17:51:54 unraidserver kernel: docker0: port 1(veth6e829bd) entered disabled state

Jul 8 17:51:54 unraidserver kernel: veth6e829bd (unregistering): left allmulticast mode

Jul 8 17:51:54 unraidserver kernel: veth6e829bd (unregistering): left promiscuous mode

Jul 8 17:51:54 unraidserver kernel: docker0: port 1(veth6e829bd) entered disabled state

Edited July 8, 2025Jul 8 by SkepticalOptimist
added context.

Try booting in safe mode.

I stand corrected. This is not solved. In fact, I restarted as I suspected I was still in safe and the same error and double Unraid logo appears.

Gluetunvpn is still self starting even with set to off in docker.

Edited July 9, 2025Jul 9 by SkepticalOptimist

Post the diagnostics in safe mode.

Don't see anything obvious logged, try accessing the GUI with a different browser, or even a different device like a phone or tablet.

2 hours ago, JorgeB said:

Don't see anything obvious logged, try accessing the GUI with a different browser, or even a different device like a phone or tablet.

I tested another browser and same results (Edge vs Brave)

I don't understand what you have proved? The error only occurs ( in subject) in normal No GUI boot mode. It doesn't appear in safe mode as mentioned. Therefore, there is something in regular boot mode which is causing both the Java error and double Unraid logo. I also see this: (attached)

Something is clearly wrong.

This all began following either 7.1.4 upgrade and/or 2 power failures (UPS didn't hold) and/or both.

I researched a bit further and I am seeing no license key associated with my account when I own 2. What is going on?

Edited July 10, 2025Jul 10 by SkepticalOptimist
more info

23 minutes ago, SkepticalOptimist said:

It doesn't appear in safe mode as mentioned.

You said:

20 hours ago, SkepticalOptimist said:

I stand corrected. This is not solved.

So I assumed safe mode didn't help, if it doesn't happen in safe mode it's likely a plugin, most likely Connect. Look for an update

I went online and my license seems to be completely gone. I opened a support ticket to find out what is going on...

I confirmed with Unraid support that my license was indeed removed. I don't have an explanation as to why as of yet.

The implications or results of losing my license:

1. You will likely lose Unraid Connect and have a big red ! with no explanation. As soon as I restarted array, I was prompted to install UConnect which re-established itself and ! disappeared.

2. Potentially the Java script error documented above. I am not validating this is fixed right away. Will do so on next reboot.

3. Potentially double Unraid logo. Corrected itself right after Unraid Connect re-applied.