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
{{ message }}
This repository has been archived by the owner on Mar 28, 2022. It is now read-only.
Hi, I have a question regarding the Encrypt LETS certificates.My Server is running about Ubuntu 20.04 Specifically Docker, in a Docker-Compose file Now I already have my local domain created in my DNS, to the same I have generated the valid certificates Let's Encrypt My doubt is how I declare him in the .yaml fileLocation of the certificate for q use it behind probe according to the reports of Bug q I saw here but I did not have a good result please if you could tell me I would appreciate it a lot.By the way, the project is excellent a great job boys congratulations.
I need to know how to declare in a Docker Compose file LET's Encrypt certificates already generated
Describe why this feature is needed:
To use certs Let's Encrypt
Scope of feature:
TRASA codebase
dashboard
server
mobile app
browser extension
device agent
website/docs
The text was updated successfully, but these errors were encountered:
Describe the feature:
Hi, I have a question regarding the Encrypt LETS certificates.My Server is running about Ubuntu 20.04 Specifically Docker, in a Docker-Compose file Now I already have my local domain created in my DNS, to the same I have generated the valid certificates Let's Encrypt My doubt is how I declare him in the .yaml fileLocation of the certificate for q use it behind probe according to the reports of Bug q I saw here but I did not have a good result please if you could tell me I would appreciate it a lot.By the way, the project is excellent a great job boys congratulations.
I need to know how to declare in a Docker Compose file LET's Encrypt certificates already generated
Describe why this feature is needed:
To use certs Let's Encrypt
Scope of feature:
The text was updated successfully, but these errors were encountered: