MeshCentral LE production cert
-
@JaredBusch said in MeshCentral LE production cert:
@scottalanmiller said in MeshCentral LE production cert:
Oh weird, it was flawless transitioning for us. Did you let it restart on its own or did you manually restart the service?
You have to restart the service anytime you change a setting in the config file.
You aren't supposed to have to. Or at least you weren't supposed to have to in the past. It was supposed to detect changes and reload on its own.
-
@scottalanmiller said in MeshCentral LE production cert:
@JaredBusch said in MeshCentral LE production cert:
@scottalanmiller said in MeshCentral LE production cert:
Oh weird, it was flawless transitioning for us. Did you let it restart on its own or did you manually restart the service?
You have to restart the service anytime you change a setting in the config file.
You aren't supposed to have to. Or at least you weren't supposed to have to in the past. It was supposed to detect changes and reload on its own.
Maybe I misread something in the guide.
-
@scottalanmiller said in MeshCentral LE production cert:
@JaredBusch said in MeshCentral LE production cert:
@scottalanmiller said in MeshCentral LE production cert:
Oh weird, it was flawless transitioning for us. Did you let it restart on its own or did you manually restart the service?
You have to restart the service anytime you change a setting in the config file.
You aren't supposed to have to. Or at least you weren't supposed to have to in the past. It was supposed to detect changes and reload on its own.
Did you try removing the letsencrypt folder prior to restarting for production mode? I had to do that too, along a couple other things that are now fixed.
-
@pmoncho said in MeshCentral LE production cert:
@scottalanmiller said in MeshCentral LE production cert:
@JaredBusch said in MeshCentral LE production cert:
@scottalanmiller said in MeshCentral LE production cert:
Oh weird, it was flawless transitioning for us. Did you let it restart on its own or did you manually restart the service?
You have to restart the service anytime you change a setting in the config file.
You aren't supposed to have to. Or at least you weren't supposed to have to in the past. It was supposed to detect changes and reload on its own.
Did you try removing the letsencrypt folder prior to restarting for production mode? I had to do that too, along a couple other things that are now fixed.
Doing that forced it to generate a new one.
-
@pmoncho said in MeshCentral LE production cert:
@scottalanmiller said in MeshCentral LE production cert:
@JaredBusch said in MeshCentral LE production cert:
@scottalanmiller said in MeshCentral LE production cert:
Oh weird, it was flawless transitioning for us. Did you let it restart on its own or did you manually restart the service?
You have to restart the service anytime you change a setting in the config file.
You aren't supposed to have to. Or at least you weren't supposed to have to in the past. It was supposed to detect changes and reload on its own.
Did you try removing the letsencrypt folder prior to restarting for production mode? I had to do that too, along a couple other things that are now fixed.
Yup, that's a requirement in the docs.
-
@JaredBusch said in MeshCentral LE production cert:
@pmoncho said in MeshCentral LE production cert:
@scottalanmiller said in MeshCentral LE production cert:
@JaredBusch said in MeshCentral LE production cert:
@scottalanmiller said in MeshCentral LE production cert:
Oh weird, it was flawless transitioning for us. Did you let it restart on its own or did you manually restart the service?
You have to restart the service anytime you change a setting in the config file.
You aren't supposed to have to. Or at least you weren't supposed to have to in the past. It was supposed to detect changes and reload on its own.
Did you try removing the letsencrypt folder prior to restarting for production mode? I had to do that too, along a couple other things that are now fixed.
Doing that forced it to generate a new one.
I missed that umpteen times in the docs, until I didn't.
-
@pmoncho said in MeshCentral LE production cert:
@scottalanmiller said in MeshCentral LE production cert:
@JaredBusch said in MeshCentral LE production cert:
@scottalanmiller said in MeshCentral LE production cert:
Oh weird, it was flawless transitioning for us. Did you let it restart on its own or did you manually restart the service?
You have to restart the service anytime you change a setting in the config file.
You aren't supposed to have to. Or at least you weren't supposed to have to in the past. It was supposed to detect changes and reload on its own.
Did you try removing the letsencrypt folder prior to restarting for production mode? I had to do that too, along a couple other things that are now fixed.
This was the fix??
-
@FATeknollogee said in MeshCentral LE production cert:
@pmoncho said in MeshCentral LE production cert:
@scottalanmiller said in MeshCentral LE production cert:
@JaredBusch said in MeshCentral LE production cert:
@scottalanmiller said in MeshCentral LE production cert:
Oh weird, it was flawless transitioning for us. Did you let it restart on its own or did you manually restart the service?
You have to restart the service anytime you change a setting in the config file.
You aren't supposed to have to. Or at least you weren't supposed to have to in the past. It was supposed to detect changes and reload on its own.
Did you try removing the letsencrypt folder prior to restarting for production mode? I had to do that too, along a couple other things that are now fixed.
This was the fix??
Yes.
-
@JaredBusch said in MeshCentral LE production cert:
@FATeknollogee said in MeshCentral LE production cert:
@pmoncho said in MeshCentral LE production cert:
@scottalanmiller said in MeshCentral LE production cert:
@JaredBusch said in MeshCentral LE production cert:
@scottalanmiller said in MeshCentral LE production cert:
Oh weird, it was flawless transitioning for us. Did you let it restart on its own or did you manually restart the service?
You have to restart the service anytime you change a setting in the config file.
You aren't supposed to have to. Or at least you weren't supposed to have to in the past. It was supposed to detect changes and reload on its own.
Did you try removing the letsencrypt folder prior to restarting for production mode? I had to do that too, along a couple other things that are now fixed.
This was the fix??
Yes.
:thumbs_up: :thumbs_up:
-
@scottalanmiller I have set all as described in manual. Port 80 is open port 444 for SLL is also open
letsdebug.net shows green. But no certificate is created. Is there any log?
BTW: i have windows installation -
@alesribic said in MeshCentral LE production cert:
@scottalanmiller I have set all as described in manual. Port 80 is open port 444 for SLL is also open
letsdebug.net shows green. But no certificate is created. Is there any log?
BTW: i have windows installationShould be port 443 not 444
-
@IRJ said in MeshCentral LE production cert:
@alesribic said in MeshCentral LE production cert:
@scottalanmiller I have set all as described in manual. Port 80 is open port 444 for SLL is also open
letsdebug.net shows green. But no certificate is created. Is there any log?
BTW: i have windows installationShould be port 443 not 444
And SSL, not SLL...
-
Also Windows and IIS is a different ballgame. I would look at this guide
https://weblog.west-wind.com/posts/2016/Feb/22/Using-Lets-Encrypt-with-IIS-on-Windows
-
Anyone? I went thru manuals evrything seems ok but no success. LetsEncrypt subfolder is not created even if production is false
This is my config.json
{
"settings": {
"cert": "MyDomain",
"wanonly": true,
"_minify": true,
"letsencrypt": {
"email": "MyEmail",
"names": "MyDomain",
"rsaKeySize": 3072,
"production": true
},
"webrtc": true,
"allowhighqualitydesktop": true },
"domains": {
"": {
"title": "RDP support"
}
}
}
