JSON Error


Recommended Posts

  • 1 month later...
6 hours ago, ChatNoir said:

Have you updated the plugin ? What version of Unraid are you using ?

 

UnRAID = 6.9.2

 

I didnt see that there was a  newer plugin version (when I originally raised issed I was using the latest version), so have upgraded MyServers to version 2022.05.10.1726 tonight and checked to see if there is JSON error still showing... there isnt - But it now says "Current Server Not Connected to Mothership" !!

 

Any ideas as it certainly looks connected as I can access it alright.

Link to comment

Sorry, I'm not sure how I missed this thread.

 

In general, the first step is to go to the Plugins page and confirm you are running the latest My Servers plugin. It sounds like you are, great!

 

For any error shown in the UPC, you'll want to open a web terminal and run:

unraid-api start

Give everything a minute or two to start up, then check the UPC again, hopefully all is good.

 

If not, please post a new screenshot. 

 

 

Note: if you see "Current Server Not Connected to Mothership", the command above should resolve it. But at this point it isn't going to cause you major issues either way.

Link to comment

Hi @ljm42

 

OK, at the moment there is no JSON error showing - but I do have this;

 

image.png.42a74040bb788de4666db322c3ca40cb.png

 

So, I ran the command from an SSH terminal;

 

image.png.79900876fdbc1577e474c01942d5b112.png

 

But still have the "not connected" error ?

 

Everything seems to work fine - just annoying seeing this error showing.

 

image.png

image.png

Link to comment
21 minutes ago, SliMat said:

But still have the "not connected" error ?

 

It can take a few minutes for the connection to happen, but if it hasn't happened by now it probably isn't going to.

 

Would you please show me the output of this?

unraid-api report

 

Link to comment
3 hours ago, ljm42 said:

Would you please show me the output of this?

unraid-api report

 

Yes, it still shows as not connected... here is the output;

 


<-----UNRAID-API-REPORT----->
SERVER_NAME: DL380p-Rack
ENVIRONMENT: production
UNRAID_VERSION: 6.9.2
UNRAID_API_VERSION: 2.46.3 (running)
NODE_VERSION: v14.15.3
API_KEY: valid
MY_SERVERS: authenticated
MY_SERVERS_USERNAME: SliMat
RELAY: connected
MOTHERSHIP: ok
ONLINE_SERVERS:
OFFLINE_SERVERS: DL380p-Rack
HAS_CRASH_LOGS: no
</----UNRAID-API-REPORT----->

 

  • Like 1
Link to comment
  • 5 months later...

@ljm42

 

I have the same error at the moment after upgrading both of my servers to the latest version as of today. 1 server is fine the other has this message.

 

Tried all the above. unraid-api restart etc.

 

SERVER_NAME: GALACTICA
ENVIRONMENT: production
UNRAID_VERSION: 6.11.2
UNRAID_API_VERSION: 2.53.0
UNRAID_API_STATUS: running
API_KEY: valid
MY_SERVERS: authenticated
MY_SERVERS_USERNAME: BelgarionNL
CLOUD:
        STATUS: [ok]  
RELAY:
        STATUS: [connected]  
MINI-GRAPH:
        STATUS: [connected]

 

 

Link to comment
On 11/5/2022 at 4:06 PM, BelgarionNL said:

@ljm42

 

I have the same error at the moment after upgrading both of my servers to the latest version as of today. 1 server is fine the other has this message.

 

Tried all the above. unraid-api restart etc.

 

SERVER_NAME: GALACTICA
ENVIRONMENT: production
UNRAID_VERSION: 6.11.2
UNRAID_API_VERSION: 2.53.0
UNRAID_API_STATUS: running
API_KEY: valid
MY_SERVERS: authenticated
MY_SERVERS_USERNAME: BelgarionNL
CLOUD:
        STATUS: [ok]  
RELAY:
        STATUS: [connected]  
MINI-GRAPH:
        STATUS: [connected]

 

 

 

There are a couple of different things mentioned in this thread. If you are seeing the message that says "JSON.parse: unexpected character..." then I'm guessing you are using a reverse proxy to access the webgui? Those are not currently supported.

 

If you run:

unraid-api report -vv

the section titled ALLOWED_ORIGINS will list the URLs that will work with your My Servers installation.

 

Link to comment