Error on Medic Web Certificate Renewal

Technical Support
1

Is this part of the medic also?

I am struggling with medic web certification renewal.

I am renewing the certificate to access the web medic, I do some steps like

  • accessing the ssh
  • login the ubuntu account
  • login as super user
  • docker stop medic-os
  • renew certificate via git bash
  • replace certificate via git bash
  • docker start medic-os

But still, there was some error like this one:

image

I tried on other laptop, even cellphone but still cannot access.

Is someone can help me on this thing.

Thank you very much.

2

Hey @Marcelo_De_Guzman, it sounds like you’re using CHT 3.x. Have you had a look at this link?

3

What you see in that link should be enough for taking care of the cert upgrades. i.e. you don’t need to stop the containers. You just need to copy the certs over to the container via docker cp and restart nginx via the command specified here.

1 Like
4

@henok, Thank you for the information. I have ssl.crt, but I don’t know where to find the ssl.key.

5

@Marcelo_De_Guzman the key file is what you received when you were generating the certificate signing request (csr). That file is supposed to only be with you and installed on your server and it’s not to be shared with others.

6

If you are using Letsencrypt for example, the private key could be located under /etc/letsencrypt/live/example.com/privkey.pem, where “example.com” is your domain name.

7

@Marcelo_De_Guzman - checking the domain in your screenshot (chc.caremin.com), it looks like you maybe were able to resolve the issue? Just checking back with you in case you need any more help!

8

hi @henok followed the steps and restarted the services and web request are being refused, need further support on this. @gaarimasharma

9

@sanjay could you provide some more detail? Assuming you’re using docker-compose, could you also provide some logs of the error?

2 Likes
10

we followed this thread Nginx not running after SSL certificate update - #7 by sanjay we have been able to turn on the server back. The issue was with the SSL some how we missed the default configuration overridden. Thank you for your support.

3 Likes