MeshCental 2 Config File Issues
-
@Dashrender said in MC config file issues:
@scottalanmiller said in MC config file issues:
I recommend WebRTC, it's the difference between being normal, and being insanely fast.
Is that another line - like
"WebRTC": true,
?Correct, another line.
-
@Dashrender said in MC config file issues:
@Dashrender said in MC config file issues:
@scottalanmiller said in MC config file issues:
I recommend WebRTC, it's the difference between being normal, and being insanely fast.
Is that another line - like
"WebRTC": true,
?OK I looked it up in the manual - yes it is.. I just haven't gotten that far yet, I'm still trying to get LE to work.
We moved to it early and really prefer it.
-
OK weirdness - I followed the instructions to make mcstart and mcstop.. yet mcstop doesn't work... but if I type it in by hand
sudo ./pkill -f node_modules/meshcentral
it does kill it.
here is the ls -l
-
-
@Obsolesce said in MC config file issues:
@Dashrender said in MC config file issues:
MC server
Minecraft?
It's meshcentral but i thought the same thing for a few seconds. Just messaged @Dashrender to tag
-
@wirestyle22 said in MeshCental 2 Config File Issues:
@Obsolesce said in MC config file issues:
@Dashrender said in MC config file issues:
MC server
Minecraft?
It's meshcentral but i thought the same thing for a few seconds. Just messaged @Dashrender to tag
I tagged and corrected the title.
-
@scottalanmiller said in MeshCental 2 Config File Issues:
@wirestyle22 said in MeshCental 2 Config File Issues:
@Obsolesce said in MC config file issues:
@Dashrender said in MC config file issues:
MC server
Minecraft?
It's meshcentral but i thought the same thing for a few seconds. Just messaged @Dashrender to tag
I tagged and corrected the title.
Too many acronyms in IT
-
@scottalanmiller said in MeshCental 2 Config File Issues:
@wirestyle22 said in MeshCental 2 Config File Issues:
@Obsolesce said in MC config file issues:
@Dashrender said in MC config file issues:
MC server
Minecraft?
It's meshcentral but i thought the same thing for a few seconds. Just messaged @Dashrender to tag
I tagged and corrected the title.
Thanks.
-
Here is my current config.json
Here is the directory listing from /opt/meshcentral/meshcentral-data
here is the error in /opt/meshcentral/stdout.txt when I load MC
ERROR: Unable to parse /opt/meshcentral/meshcentral-data/config.json.
-
@Dashrender Use cat, not tail, to show us the config.
-
@scottalanmiller said in MeshCental 2 Config File Issues:
@Dashrender Use cat, not tail, to show us the config.
Thanks
-
@Dashrender Extra comma at the end before the final brace.
-
@scottalanmiller said in MeshCental 2 Config File Issues:
@Dashrender Extra comma at the end before the final brace.
They look the same to me, in this case. But yeah, cat for this purpose 100%.
-
@scottalanmiller said in MeshCental 2 Config File Issues:
@Dashrender Extra comma at the end before the final brace.
Yep, that was it.. now I get
and error use --cert to setup the default server name ...
I notice it's commenting on LAN mode - but my config has WANonly listed
-
The WAN mode might be a case problem, from the manual
in looking through the documentation - I've now found this option referenced three ways
WANonly/wanonly/Wanonly
I'm wondering if it should be WANOnly - cap the whole acronym and the first letter of the second word. -
OK Changed the caps in WANonly to Wanonly and no change - still reports at LAN mode
-
@Dashrender said in MeshCental 2 Config File Issues:
OK weirdness - I followed the instructions to make mcstart and mcstop.. yet mcstop doesn't work... but if I type it in by hand
sudo ./pkill -f node_modules/meshcentral
it does kill it.
here is the ls -l
OK found my issue here - type-o, I had mode instead of node in my command. that's working now.
But I still have the cert error when starting MC. -
-
OK I think I know why WANOnly isn't working - because MC doesn't think I have a cert name specified.
I started the process manually adding a --cert command and this is what I get.
Notice the --cert error is still there - now the question is, WHY?
-
OK - FINALLY - it's working!!!!
As part of my troubleshooting, I added "Cert": "host.domainname.com", back to the config.json (which got rid of the associated error message) now to see if it will work without it.
