Kjetil

The platform is Ubuntu. By a mistake, I installed apache2 togheter with certbot. Apache took precedence over Tomcat. When I removed apache2, and restarted tomcat, everything was fine again 🙂

Ah, Thanks for the clarification. I have replaced the peer certificate I downloaded from ESMC with a new pfx certificate from Letsencrypt.com. The mdmcore-linux-x86_64.sh script completes without errors. If I go to https://"myserver":9980 I get the message "MDC Server up and running!" Still I can not select any Mobile Device connector in ESMC ? It's like if the ESMC and the MDM is not connected with eachother. In the trace.log, I find the output below. Any idéa how to troubleshoot this ?

I wanted to replace my self-signed certificate for ESMC with an SSL certificate from "Let's Encrypt". So I installed and run "certbot". I got a new certificate, but I guess Apache tomcat settings was modified as well, so I can no longer access eraserver. By doing a "sudo service eraserver status", I can see that the service is running. So I guess I just need to restore configs in Apache, but how ?

If others have the same problem, I found out how: 1. Log in to ESMC 2. Choose "More->Peer certificates" 3. Left click on "agent certificate for server assisted installation" and "Export" 4. Copy the cert to a location on the server, and rename it, like /etc/ssl/certs/agentcertcopy.pfx 5. use that path in the script: --https-cert-path="/etc/ssl/certs/agentcertcopy.pfx"

I have read the documentation in the link. I says that for "Server assisted installation", the installer will download required certificates automatically. I can see in ESMC under "Peer certificates" that there is an "agent certificate for server assisted installation". Still, I need to know the path for this in order to provide the installation command parameters. So, how do I find --https-cert-path= to the "agent certificate for server assisted installation" ?

Hi, I want to run the installation script mdmcore-linux-x86_64.sh on my server, but have no clue what to set for the "--https-cert-path" option ? I can understand from the thread https://forum.eset.com/topic/5814-mdm-webserver-does-not-use-full-cert-chain/ that the agent cert found in the Security Management Center can be used, but how do I specify the path to that ?