MeshCentral: Error: Too few bytes to read ASN.1 value.
Describe the bug Upgrade to version 1.0.36 throws this error
/opt/meshcentral/node_modules/node-forge/lib/asn1.js:508
throw error;
^
Error: Too few bytes to read ASN.1 value.
at _fromDer (/opt/meshcentral/node_modules/node-forge/lib/asn1.js:504:19)
at Object.asn1.fromDer (/opt/meshcentral/node_modules/node-forge/lib/asn1.js:458:15)
at openFile (/opt/meshcentral/node_modules/meshcentral/authenticode.js:294:39)
at Object.createAuthenticodeHandler (/opt/meshcentral/node_modules/meshcentral/authenticode.js:1289:13)
at Object.CreateMeshCentralServer.obj.updateMeshAgentsTable (/opt/meshcentral/node_modules/meshcentral/meshcentral.js:2908:75)
at Object.CreateMeshCentralServer.obj.StartEx4 (/opt/meshcentral/node_modules/meshcentral/meshcentral.js:1620:13)
at Object.CreateMeshCentralServer.obj.StartEx3 (/opt/meshcentral/node_modules/meshcentral/meshcentral.js:1568:17)
at /opt/meshcentral/node_modules/meshcentral/meshcentral.js:1480:21
at Object.obj.GetMeshServerCertificate (/opt/meshcentral/node_modules/meshcentral/certoperations.js:986:43)
at Object.CreateMeshCentralServer.obj.StartEx2 (/opt/meshcentral/node_modules/meshcentral/meshcentral.js:1477:35) {
available: 3084,
remaining: 3084,
requested: 3085
}
odd is that another server with same version seems running fine. They do not have the same certificate.
The certificate is valid and have not changed since a couple of month.
Server Software (please complete the following information):
- Virtualization: kubernetes
- Network: LAN/WAN, reverse proxy, ssl offload,
- Version: 1.0.36
- Node: 16.15
- Browser: Google Chrome
Additional context I use this docker image -> https://hub.docker.com/layers/vegardit/meshcentral/1.0.x/images/sha256-13042a89fb3e5da3dde8d0c2e6eae7c92642713f505a4bdf00fcec5ca90f1a8c?context=explore
Can you point me to the right direction of the error please ? I am aware it may not be meshcentral’s fault, I’m just investigating to debug the server.
Thank you very much
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 3
- Comments: 21 (8 by maintainers)
Commits related to this issue
- Improved authenticode.js error handling for #4134 — committed to Ylianst/MeshCentral by Ylianst 2 years ago
- Added more authenticode-js error handling, #4134 — committed to Ylianst/MeshCentral by Ylianst 2 years ago
@Ylianst This seems to be related to the “Title” section of the domain in the config.json using characters that are not allowed. Mine has the
®
and™
(Laptop Pitstop® Hyper Connect™) in my domain title so it is trying to put it into thefield which authenticode.js does not know how to handle.