-
-
Notifications
You must be signed in to change notification settings - Fork 770
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem when use .com instead of .localhost #102
Comments
Is your server publicly exposed on the internet? It's mandatory for Caddy to generate the TLS certificate using Let's Encrypt. |
No i just work locally to upgrade my skills, i search to use another host to my actual caddy server I can make that with nginx or apache, but i can't do it with caddy Actually caddy give this followings url => https://monsite.localhost/ |
Ok i solve my problem with this followings instruction I change my SERVER_NAME env var in my .env.local file to monsite.com into http://monsite.com, to "disabling" ssl and its work ! I find Thanks for your help, i close this issue |
Alternatively, you can use a self-signed TLS certificate: https://caddyserver.com/docs/caddyfile/directives/tls To generate a valid certificate for a real domain, Caddy must be exposed publicly on the internet. |
Hello, does this means that starting the container on a produciton server will not be enough ? What do you mean by " exposed publicly " ? |
When is use this following command
SERVER_NAME="monsite.com, caddy:80" docker-compose up --build
Application not display on "monsite.com", its make an SSL error =>
SSL_ERROR_INTERNAL_ERROR_ALERT
but when i use this
SERVER_NAME="monsite.localhost, caddy:80" docker-compose up --build
The application be display on "monsite.localhost"
I think its obvious issu, but I can't solve the problem
Someone else can help me ?
The text was updated successfully, but these errors were encountered: