# Let's Encrypt server certificate & recent update (6.7.4 build 1760)

**URL:** <https://forums.interworx.com/t/lets-encrypt-server-certificate-recent-update-6-7-4-build-1760/19208>\
**Category:** General Discussion\
**Tags:** certificate, server-ssl, lets-encrypt-le\
**Created:** [May 9, 2020, 7:43am UTC](https://forums.interworx.com/t/lets-encrypt-server-certificate-recent-update-6-7-4-build-1760/19208 "2020-05-09T07:43:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sysnop](https://forums.interworx.com/letter_avatar_proxy/v4/letter/s/cdc98d/32.png) [@sysnop](https://forums.interworx.com/u/sysnop)\
**Post date:** [May 9, 2020, 7:43am UTC](https://forums.interworx.com/t/lets-encrypt-server-certificate-recent-update-6-7-4-build-1760/19208/1 "2020-05-09T07:43:20Z")

</div>

The changelog says:

[New] Ability to specify a domain when creating service level Let’s Encrypt certificates in NodeWorx  
Domain must resolve to the server, and must not be a SiteWorx account

If we’re currently using a Siteworx account for the server’s hostname in order to validate a server certificate, does this update mean we can now remove the hostname’s Siteworx account, point its FQDN to /var/www/html/ as we used to do, and LE will validate the server certificate using DNS as it used to do?

---

<div class="post-metadata">

**Author:** ![d2d4j](https://forums.interworx.com/user_avatar/forums.interworx.com/d2d4j/32/16_2.png) [@d2d4j](https://forums.interworx.com/u/d2d4j)\
**Post date:** [May 10, 2020, 12:37pm UTC](https://forums.interworx.com/t/lets-encrypt-server-certificate-recent-update-6-7-4-build-1760/19208/2 "2020-05-10T12:37:02Z")

</div>

Hi Sysnop

Good catch and I am sorry, I am not sure myself

There is one thing which comes to mind though if true, and that is to have it as described, you cannot have a siteworx account with same FQDN. So what do you do for emails for the FQDN unless the plan is to have them as alises - if so, to which domain

Many thanks and stay safe

John

---

<div class="post-metadata">

**Author:** ![sysnop](https://forums.interworx.com/letter_avatar_proxy/v4/letter/s/cdc98d/32.png) [@sysnop](https://forums.interworx.com/u/sysnop)\
**Post date:** [May 11, 2020, 8:12am UTC](https://forums.interworx.com/t/lets-encrypt-server-certificate-recent-update-6-7-4-build-1760/19208/3 "2020-05-11T08:12:10Z")

</div>

Thanks, John. I don’t need or want a Siteworx account for the server’s hostname, it’s just there for LE to issue SSL. When I get a chance I’ll give the other method another a try.

---

<div class="post-metadata">

**Author:** ![IWorx-Jenna](https://forums.interworx.com/user_avatar/forums.interworx.com/iworx-jenna/32/41_2.png) [@IWorx-Jenna](https://forums.interworx.com/u/IWorx-Jenna)\
**Post date:** [May 12, 2020, 9:47am UTC](https://forums.interworx.com/t/lets-encrypt-server-certificate-recent-update-6-7-4-build-1760/19208/4 "2020-05-12T09:47:27Z")

</div>

Hello–

With the update, you are able to generate a Let’s Encrypt cert directly for the hostname from the SSL page in NodeWorx. The hostname just has to be a domain that is real and resolves to the server. It can’t be a SiteWorx account, so you’ll want to delete that first.

I don’t believe there are any other steps or settings that would need to be made. Just:

-not a SiteWorx account  
-live domain  
-must resolve to server

Let me know if you have any other questions! 🙂

---

<div class="post-metadata">

**Author:** ![sysnop](https://forums.interworx.com/letter_avatar_proxy/v4/letter/s/cdc98d/32.png) [@sysnop](https://forums.interworx.com/u/sysnop)\
**Post date:** [May 13, 2020, 7:38am UTC](https://forums.interworx.com/t/lets-encrypt-server-certificate-recent-update-6-7-4-build-1760/19208/5 "2020-05-13T07:38:18Z")

</div>

Thanks Jenna. I see more clearly how this works after a few dry runs.