paszczakus91 0 Posted March 8, 2018 Share Posted March 8, 2018 Hi, I,m trying to install standalone MDM core on Debian 9 Every time when i start installation script, after accept of ERA Certificate, I get error: Peer certificate checked successfully Checking HTTPS certificate... ./mdmcore-linux-x86_64.sh: Provided HTTPS certificate file could not be validated. This is probably caused by wrong password or missing private key. I was checked password 10 times and tryed to use old certificate and created new for ERA Server / Agent / Mobile Device Connector (every created and exported from ERA) I'm using bellow parameters: ./mdmcore-linux-x86_64.sh \ --https-cert-path="./ERAServerCert.pfx" \ --cert-password=****************** \ --port=2222 \ --db-type="MySQL" \ --db-driver="MySQL" \ --db-admin-username="root" \ --db-admin-password=************************* \ --db-user-password=****************************** \ --db-hostname=***************************** \ --hostname=ERA IP Address \ --webconsole-user=************************** \ --webconsole-password=***************************** \ --mdm-hostname=MDM.DOMAIN.COM Link to comment Share on other sites More sharing options...
ESET Staff MartinK 370 Posted March 8, 2018 ESET Staff Share Posted March 8, 2018 I would recommend to follow documentation for MDM manual installation which describes command line parameters and possible installation scenarios. From parameters you provided I think problem is with parameter: --cert-password which should have actually been: --https-cert-password Link to comment Share on other sites More sharing options...
paszczakus91 0 Posted March 9, 2018 Author Share Posted March 9, 2018 Thank you for your replay. Yes, i did it like is described in manual I did certificate with simple password, too I recive this output from installer: Do you accept the license? [y/N]: y Creating directories... Creating 'install' directory path: /opt/eset/RemoteAdministrator/MDMCore Creating 'config' directory path: /etc/opt/eset/RemoteAdministrator/MDMCore Creating 'config' directory path: /etc/opt/eset/RemoteAdministrator/MDMCore/Agent Creating 'data' directory path: /var/opt/eset/RemoteAdministrator/MDMCore Creating 'logs' directory path: /var/log/eset/RemoteAdministrator/MDMCore Creating 'libs' directory path: /opt/eset/RemoteAdministrator/MDMCore Creating 'Modules' directory path: /var/opt/eset/RemoteAdministrator/MDMCore/Modules/ Creating 'setup tmp' directory path: /tmp/tmp.dsdfsdfs3/setup/tmp Directories created Starting install sequence. Checking OpenSSL ... Found: OpenSSL 1.0.2l 25 May 2017 Checking installed version ... Status of current installation is: NEW Getting certificate from server... Received Server certificate details: Subject: **********; Issuer: ***************************; Fingerprint: *************************************** Do you accept server certificate? [y/N]: y product_guid was not passed as parameter or in config-file, generating new product_guid... Generating product guid... Generating product guid was successful (new product_guid = 9********************************) Checking peer certificate... Peer certificate checked successfully Checking HTTPS certificate... ./mdmcore-linux-x86_64.sh: Provided HTTPS certificate file could not be validated. This is probably caused by wrong password or missing private key. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 370 Posted March 9, 2018 ESET Staff Share Posted March 9, 2018 Just to be sure, have you fixed wrong installation parameter with password I mentioned in my previous post? Link to comment Share on other sites More sharing options...
paszczakus91 0 Posted March 9, 2018 Author Share Posted March 9, 2018 Oh, ok, I didn't change it, this change solved the problem. Thank you and sorry Link to comment Share on other sites More sharing options...
Recommended Posts