-
Notifications
You must be signed in to change notification settings - Fork 5
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
Plugin Error #5
Comments
So you can git clone the repo from cli on the MC server via the https clone address (not ssh)? |
You are correct. |
I know you said:
From looking at the https://github.com/Ylianst/MeshCentral/blob/master/sample-config-advanced.json , there are several locations for a proxy to be configured, and "plugins" does NOT have a proxy attribute listed in the sample (I don't know why it wouldn't just have one place, or use the system settings, but oh well), however, looking at MC's code at this line: https://github.com/Ylianst/MeshCentral/blob/3c03bd3b0785a925bc51ae5a82682d80431ab0e5/pluginHandler.js#L246 shows that plugins [can] have their own proxy set. |
This is what I have in the config file to produce the error regarding the certificate. If I remove the proxy config I get the timeout error. |
Is there a way to install plugins from the cli? |
I am trying to install plugins for MeshCentral, but I keep getting the following error:
"Plugin Error: Error getting plugin config: connect ETIMEOUT 185.199.109.133:443"
That IP address resolves to github. I am behind a corporate proxy, but I do not have any problems regarding the proxy from the console of the server. For example, I am able to execute git clone commands without any issues.
If I enable the proxy in the MeshCentral config file, I get the following error:
"Plugin Error: Error getting plugin config: self signed certificate in certificate chain"
Has anyone seen this before? I am not sure what else I can try at this point. Maybe there is a method to manually install the plugins.
Thanks,
Brian
The text was updated successfully, but these errors were encountered: