How to Install Free SSL Certificates for Windows Server 2022 IIS

Поділитися
Вставка
  • Опубліковано 17 жов 2024

КОМЕНТАРІ • 14

  • @Mikeyxb
    @Mikeyxb 3 місяці тому +2

    Thanks man that was so much easier than i thought it would be and you explained it well :)

    • @itgeared
      @itgeared  3 місяці тому

      That's great feedback, thank you! I can tell you that the first time I used this SSL service, I was impressed at how easy it was.

  • @RobertTheUser
    @RobertTheUser 5 місяців тому +2

    one of the best tutorials i've used. thanks for making this

    • @itgeared
      @itgeared  5 місяців тому

      Thanks for the comment. I’m very glad that this tutorial was helpful.

  • @mondaka
    @mondaka 3 місяці тому +2

    When creating the task do you have to provide all the options for the win-acme client?

    • @itgeared
      @itgeared  2 місяці тому

      The win-acme client has many command line parameters that can be used. You only need to use the ones that are applicable to your scenario. See here for documentation: www.win-acme.com/reference/cli

  • @TecnoSoftware-n2j
    @TecnoSoftware-n2j 2 місяці тому +1

    Hello thanks it looks really easy, I have a question, If I want to renew certificate every 60 days how can I make it automatic?

    • @itgeared
      @itgeared  2 місяці тому

      In this video, i demonstrated the use of the win-acme client. This client in particular is very easy to use and manage. The default installation of the client already automates this process for you. The default renewal period of 55 days can be changed in settings.json. So, it sounds like a default installation will address your desire to automatically renew the certificate every 60 days. However, you can change that.

  • @ussifhossny3795
    @ussifhossny3795 Місяць тому

    I have fortigate running on the default port 80 Iam changed it to 8080 and 8443 and my website to 80 and 443 and when iam trying to browse my website from iis with domain:80 I still see fortigate ?

    • @itgeared
      @itgeared  Місяць тому +1

      If you have a device such as a firewall in front of your webserver that is internal to your network, as you indicated, you do have to get the port translation done correctly on that perimeter device. If the device is still responding on port 80, it tells me that your NAT translation is not correctly configured. On the perimeter device, you need to configure it so that port 80 on the public IP translates back to 80 on your webserver at the private IP. If you need to configure your perimeter device's portal on another port such as 8080 or 8443, you would have to get that configuration correct as well. But again, if you want that perimeter device to listen on 80 and allow that traffic into your network, its all about port forwarding/NAT translation.

  • @shadowfax_ng
    @shadowfax_ng 7 місяців тому +1

    Thanks so much for this🤗🤗🤗

    • @itgeared
      @itgeared  7 місяців тому

      Very glad that you found it useful. thank you!

  • @iamprinceefe
    @iamprinceefe 3 місяці тому +1

    How do I get the domain name for my windows 😭

    • @itgeared
      @itgeared  3 місяці тому +1

      Domain name means different things depending on context. In the context of web hosting, you acquire a domain name by registering the name with a domain registrar such as Network Solutions, GoDaddy, or Namecheap to name a few. You use that domain name in the configuration of IIS to host the website. If the website is going to be used only internally meaning an internal network, there is no need to register the domain name. You can come up with your own name. For example, if I want to host an internal website called mywebsite.internal, i can most certainly do that without any registration. I would just use that name and host that name within my internal DNS zone (see my videos about DNS). Hope this helps...