You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Idea is to use let's encrypt in yoda-webhook (and probably also yoda-restapi and yoda-graphserver) nodejs server parts in order to be able to have https based communications (without paying for real certificates).
Note that the servers (yoda-xxx) are already setup to run over https, i.e. use certificates. It is the automatic generation and renewal logic of let's encrypt that is the missing piece.
It is perfectly possible (and not so difficult) to set automatic letsencrypt certificates, even possibly grouped with DuckDNS dynamic DNS registration.
It's pretty much all in the subject.
Idea is to use let's encrypt in yoda-webhook (and probably also yoda-restapi and yoda-graphserver) nodejs server parts in order to be able to have https based communications (without paying for real certificates).
Maybe study https://itnext.io/node-express-letsencrypt-generate-a-free-ssl-certificate-and-run-an-https-server-in-5-minutes-a730fbe528ca
Note that the servers (yoda-xxx) are already setup to run over https, i.e. use certificates. It is the automatic generation and renewal logic of let's encrypt that is the missing piece.
Reading https://advancedweb.hu/how-to-use-lets-encrypt-with-node-js-and-express/, seems that maybe
certbot
can do the stuff... See https://github.com/certbot/certbot. It really would be preferably to keep the generation/renewal outside the yoda-xxx servers. The certificate renewal can even be shared.The text was updated successfully, but these errors were encountered: