-
Notifications
You must be signed in to change notification settings - Fork 559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default config.json cannot be parsed due to invalid entry #4896
Comments
Syntax on line 9 isn’t right. "sessionKey": " Can’t have two sets of “quotes” etc. Not sure what your wanting session key but it should be "sessionKey": "WhateverYourWantingKeyToAcruallyBe", |
Thank you @blaine07, making that change allows the config to be parsed and I should be able to get everything working beyond that; I appreciate your help. I guess I understated my 'expected behavior' in the OP. The expected behavior would be one of the following, in order of preference:
I am not particularly knowledgeable in git(hub) but if it is determined that we just want to edit the readme I'd be willing to submit that PR myself. I would, however, prefer to see a more robust solution implemented. |
If you simply remove this key This
isn't default value (you can verify it by cloning meshcontrol repository to your computer to check). I can't see this issue as
Its already robust and documented |
Just ran into this myself after running the example docker-compose file. Looks like a bug or mistake in the documentation? |
The error is self explanatory, it can't read the json because it's invalid Can you share ur Also which docker image are you using? As i know there is 2 and the unofficial one is on docker hub and the one we made is on github |
So I was just able to recreate the problem. Went straight to this page https://hub.docker.com/r/typhonragewind/meshcentral and copied/pasted the "docker-compose.yml example" and spun it up after changing the hostname to be my IP address. Looks like it is using the "latest" tag. Here is the resulting config.json (sensitive info removed):
|
https://hub.docker.com/r/typhonragewind/meshcentral is a third party docker image, P.S: if you just copied and pasted the output of |
Right, I totally forgot I was using tphonragewind's image. Oops. I'll switch over to the official image. I fixed this issue hours ago, just wanted to give a heads up here but I guess it wasn't needed. Thanks! |
no worries! the repo for the third party seems to be here - https://github.com/Typhonragewind/meshcentral-docker P.S we dont add any environment values to change P.S.S: oh wow i lied sorry my bad! we do change the sessionkey value but im guessing the regex for generating the key is including invalid characters? |
Are you able to reproduce the issue yourself on the official image? I'll give it a go here in a few min. |
@natechoiniere i do think i found a bug however tho? |
This is not correct JSON record. It should be in form: "key":"value" or "key":12345 where value only numbers, but in your case, value has extra |
ooo the is a boo boo in the docker image! i got it to do the same thing! |
I tried the exact same steps I did earlier to recreate this issue with the latest official image. It worked just fine, no issue w/ the sessionKey. |
can you create a new issue for me plz @natechoiniere as i was about to reproduce it. |
I'll see if I can reproduce this on the official image a bit later today once I get off work, and if I can, I'll open an issue. |
@natechoiniere no worries i already created a PR #5333 which fixes the issue for the moment, |
Exactly, there's no reason this should be in the default config.json. Bug fixed after 8 months! Thanks @si458 |
Greetings. Can you show me what the config should look like if I want to deploy it in Docker on a white IP without certificates. docker-compose-example-2.yaml version: '2' This is example 2 from the documentationservices: networks: |
@ssTibaltss, meshcentral requires the use of certificates for security like the intel AMT
|
Describe the bug
Attempting to start a Mesh Central docker container with an unedited config.json file fails with error: "ERROR: Unable to parse /opt/meshcentral/meshcentral-data/config.json."
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A successful build of the docker container
Server Software (please complete the following information):
Additional context
Pasting the json into DuckDuckGo's json validator returns:
Error: Parse error on line 9:
... "sessionKey": "`xc"_sessionKey": "MyRea
-----------------------^
Expecting 'EOF', '}', ':', ',', ']', got 'undefined'
Your config.json file
The text was updated successfully, but these errors were encountered: