After running script to launch containers in ubuntu, some containers are started well but some containers status is showing Restarting, even after 20 mins also same status, I tried restarting that container using container ID, and also tried docker service restart, still issue persists, can anyone help me on this issue?
When a container is restarting that means the process inside the container stops and the restart policy starts it again. What you need to do is find out why the process stops. You can check the container logs and share it if you don’t recognize the reason. Make sure your container runs processes in the foreground, otherwise it will just stop immediately since ther is no process manager to keep it alive in the container and you won’t even see an error log if it just finishes successfully.
Hi rimelek,
thanks for your response, in error log it is showing config file related, how to setup config file?
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685674608.239218,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685674671.6474895,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685674735.0872633,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685674800.5551887,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685674863.5056224,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685674926.4797566,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685674990.7611911,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685675053.7639039,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685675117.4960165,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685675182.2427483,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685675245.6414137,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685675310.3733556,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685675373.3328967,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685675438.1471696,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685675502.0494344,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685675565.1011064,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685675630.080243,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685675692.5298996,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685675757.4853666,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685675823.870249,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685675889.695286,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685675954.1951118,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685676018.1514401,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685676082.4842422,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685676146.5843196,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685676210.6528497,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
{"level":"info","ts":1685676273.8636196,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
I don’t use Caddy. For proper Caddy configuration you can about Caddy from the official documentation: Welcome — Caddy Documentation
or try the Caddy community: https://caddy.community/
In this specific case you can also serch for the error message:
Error: adapting config using caddyfile: server listening on [:443] is configured for HTTP and cannot natively multiplex HTTP and HTTPS: :443
on Google to find out what other Caddy users did to solve this.
I tried it for you:
hi,
When i call the public IP in browser im getting below output
Client sent an HTTP request to an HTTPS server.
Can you help me with any solution?
can you help me where we need to configure hostname and ports in docker
It means you tried to access the website using HTTP and not HTTPS in the url, but the server (caddy) expects HTTPS. The solution is using HTTPS in the url. IF you don’t want to, that is a caddy configuration which I don’t use. When a server expects HTTPS it is common practice to also let the server handle HTTP requests as well only for redirecting the request to HTTPS. That is also different in each server/proxy configuration.
If you mean ports where the servicdes inside the container are listening, that is not a Docker configuration. If you mean the port that can be used from another machine forwarded from the host to a container, you can use the “ports” section in Docker Compose or the -p option with docker run
but that doesn’t help with the HTTPS issue. Regarding hostnames, the question is similar. A website can be accessible on a hostname (virtual host) which is a server configuration, so I am not really sure what you mean.
Please show us more context. If you can share the compose file or docker run commands how you start the containers, we might be able to help you. If it turnes out that everthing a matter of caddy configuration, you can have more luck on the caddy forum or you should wait for someone here who uses caddy.
What dhasboard? Again, I don’t use Caddy, I don’t know if it has a dashboard. If it doesn’t, I don’t know what dashboard you are referring to. Unfortunately a screenshot will not help me to help you. I asked for more context that you did not provide. Unless you can tell us exactly what you would like to know, we can’t help you. And if it is a question about caddy, I will not be able to help you and I have very little time to do the research which you probably realized as I respond slowly.