letsencrypt-siteextension | Azure Web App Site Extension for easy installation | Azure library

by sjkp C# Version: 1.0.6 License: No License

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | letsencrypt-siteextension Summary

letsencrypt-siteextension is a C# library typically used in Cloud, Azure applications. letsencrypt-siteextension has no vulnerabilities and it has low support. However letsencrypt-siteextension has 20 bugs. You can download it from GitHub.

Azure Web App Site Extension for easy installation and configuration of Let's Encrypt issued SSL certifcates for custom domain names.

Support

Quality

Security

License

Reuse

Support

letsencrypt-siteextension has a low active ecosystem.

It has 737 star(s) with 80 fork(s). There are 42 watchers for this library.

It had no major release in the last 12 months.

There are 100 open issues and 254 have been closed. On average issues are closed in 97 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of letsencrypt-siteextension is 1.0.6

Quality

letsencrypt-siteextension has 20 bugs (0 blocker, 0 critical, 14 major, 6 minor) and 0 code smells.

Security

letsencrypt-siteextension has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

letsencrypt-siteextension code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

letsencrypt-siteextension does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

letsencrypt-siteextension releases are available to install and integrate.

Installation instructions are available. Examples and code snippets are not available.

letsencrypt-siteextension saves you 88544 person hours of effort in developing the same functionality from scratch.

It has 96869 lines of code, 0 functions and 91 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of letsencrypt-siteextension

Get all kandi verified functions for this library.

letsencrypt-siteextension Key Features

No Key Features are available at this moment for letsencrypt-siteextension.

letsencrypt-siteextension Examples and Code Snippets

No Code Snippets are available at this moment for letsencrypt-siteextension.

Community Discussions

Trending Discussions on letsencrypt-siteextension

Azure LetsEncrypt cannot access .well-known/acme-challenge for my function

Let's Encrypt: ClientID reqistered under application settings differs from what I entered?

QUESTION

Azure LetsEncrypt cannot access .well-known/acme-challenge for my function

Asked 2019-May-28 at 14:29

I am trying to enable SSL for my azure function using the letsencrypt site-extension for azure as described here. I was following the instructions in that wiki and on this website.

However, I get an error when it tries to verify the website.

The error indicates that the acme-challenge page cannot be accessed (404).

This is my web.config under .well-known/:

...

ANSWER

Answered 2019-May-28 at 06:36

Here's how you can do that.

In your function app, create a new proxy for the challenge directory (this is required as the challenge will be a http get to /.well-known/acme-challenge/, and per default a function in a function app will only answer on /api/.

You can setup the proxy in the following way.

proxies.json

Source https://stackoverflow.com/questions/56333957

QUESTION

Let's Encrypt: ClientID reqistered under application settings differs from what I entered?

Asked 2018-Feb-19 at 10:38

So I am trying to get Let's Encrypt working on Windows Azure through the web extension but I am getting a error that I cannot solve or find any information about.

I am following this tutorial on how to set ut Let's Encrypt on Azure:

https://github.com/sjkp/letsencrypt-siteextension/wiki/How-to-install#create-a-service-principal

When I use the extension wizard, fill in all the fields and press next this is the error I get:

My resourcegroup:

My serviceplan inside my resourcegroup (+ storage and app service):

My ClientID (application id):

My secret is also set, saved the value and pasted it into the wizard:

My connection strings are set (in the format mentioned in the tutorial/setup):

There is a webjob running, I did not create this, I think it was created by the wizard in some way(?):

And at last:

It seems to me that I have done everything the tutorial has asked me to do, I don't know why I get the error, I also don't understand the reference to "00000000-0000-0000-0000-000000000000". Does anyone know what I did wrong and how to solve this error?

Thanks in advance.

...

ANSWER

Answered 2017-Oct-13 at 12:16

The checkbox "Update Application Settings" must be checked if you want to modify the settings from the Let's Encrypt extension's pages.

Source https://stackoverflow.com/questions/46728797

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install letsencrypt-siteextension

With the semi-automated installation you manually add the site extension to your web app. Open the extension and manually click through the 3 step dialog. Once this process is complete your custom domain for the site is setup with a Let's Encrypt issued SSL certificate.
To use the Fully Automated Installation the following Web App settings must be added. As it can be seen from the list of App Settings a service principal is needed. The service principal must be assigned permissions to the web app, that is required as the extension use it for installing and updating the certificate. (If two resource groups are used, the app service principal must have access to both). Besides the App Settings, the two Azure Web Job required connection strings AzureWebJobsStorage and AzureWebJobsDashboard must also exists, as the extension relies on an internal Web Job to renew the certificates once they expire. To see an example of an ARM template installation look at azuredeploy.json.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: