19

When we open a website, we usually expect to see HTTPS in the browser address bar. HTTPS keeps the connection between the visitor and the website secure. It is especially important when a website handles login details, personal information, or other sensitive data.

Setting up HTTPS manually can take some time. You need to get an SSL/TLS certificate, configure the web server, and remember to renew the certificate before it expires.

Caddy makes this process much easier with its automatic HTTPS feature.

What Is Automatic HTTPS?

Automatic HTTPS is a feature in Caddy that can automatically set up HTTPS for a website.

For example, suppose you have a domain called:

example.com

You can use a simple Caddy configuration such as:

example.com {

    root * /var/www/html

    file_server

}

After Caddy starts, it can automatically request a TLS certificate for the domain. Once the certificate is available, Caddy uses it to provide HTTPS for the website.

This means you do not normally have to manually create a certificate and add a large amount of configuration.

How Does Caddy Get the Certificate?

Caddy uses the ACME protocol to communicate with a certificate authority.

A certificate authority, such as Let’s Encrypt, provides certificates after checking that you control the domain.

The process is fairly simple:

1. Caddy sees a domain in its configuration.
2. It requests a certificate for that domain.
3. The certificate authority checks the domain.
4. Caddy completes the verification.
5. The certificate is issued.
6. Caddy starts serving the website over HTTPS.

The whole process happens automatically when the required conditions are met.

What Does Caddy Need for This to Work?

Automatic HTTPS is convenient, but the server still needs to be configured correctly.

The domain should point to the server where Caddy is running. The necessary ports should also be accessible.

For a normal website, port 80 and port 443 are commonly involved.

If the domain does not point to the correct server or a firewall blocks the required traffic, Caddy may not be able to obtain the certificate.

What Happens to HTTP Requests?

Caddy can also redirect visitors from HTTP to HTTPS.

For example, if someone enters:

http://example.com

Caddy can redirect the visitor to:

https://example.com

The visitor can then access the secure version of the website.

This is useful because some people may still type the website address without https://.

Does Caddy Renew the Certificate?

Yes. This is another useful part of automatic HTTPS.

TLS certificates have an expiration date. If you manage certificates manually, you need to remember when they expire and renew them.

Caddy takes care of the renewal process automatically.

This can save a lot of time, especially when one server is hosting multiple websites. Instead of checking every certificate yourself, Caddy handles the renewal in the background.

What If Automatic HTTPS Does Not Work?

Sometimes Caddy cannot obtain a certificate. This does not necessarily mean there is a problem with Caddy itself.

A few common things to check are:

• Is the domain pointing to the correct server?
• Is port 80 accessible?
• Is port 443 accessible?
• Is a firewall blocking the connection?
• Is another application already using the required port?
• Are the DNS records configured correctly?

Checking the Caddy logs can also help identify what went wrong.

Why Is Caddy’s Automatic HTTPS Useful?

The biggest benefit is that it reduces manual work.

With a traditional setup, you may need to request a certificate, install it, configure the web server, and later renew it.

Caddy handles most of these routine tasks automatically.

This makes it a convenient choice for developers and system administrators who want to set up HTTPS without spending too much time on certificate management.

A Simple Example

Imagine you have a small website running on a Linux server.

Without automatic HTTPS, you might need to:

Get certificate → Configure certificate → Configure web server → Renew certificate later

With Caddy, much of this can be handled automatically:

Configure domain → Start Caddy → Caddy handles HTTPS

You still need to make sure that your DNS and network settings are correct, but the certificate management becomes much easier.

Conclusion

Caddy’s automatic HTTPS is one of the features that makes the web server easy to use. It can obtain TLS certificates, configure HTTPS, redirect HTTP traffic, and renew certificates automatically.

For beginners, this means less time spent managing certificates and more time focusing on the website or application itself.

If you are learning web server administration, Caddy is a good tool to experiment with. Start with a simple website and a test domain, and you can quickly see how Caddy handles HTTPS for you.