2026-09-08 12:34:00 -04:00
---
2026-09-29 20:13:02 -04:00
title : How to use Apache as a reverse proxy with Let's Encrypt
2026-09-08 12:34:00 -04:00
---
2023-02-16 07:50:18 +03:00
## Requirements
2026-10-15 11:24:40 -04:00
1. Start a Coder deployment and be sure to set the following [configuration values ](../admin/setup/index.md ):
2023-02-16 07:50:18 +03:00
2026-07-15 14:07:09 -04:00
```dotenv
2023-02-16 07:50:18 +03:00
CODER_HTTP_ADDRESS=127.0.0.1:3000
CODER_ACCESS_URL=https://coder.example.com
CODER_WILDCARD_ACCESS_URL=*coder.example.com
` ``
2026-10-15 11:24:40 -04:00
Throughout the guide, be sure to replace ` coder.example.com` with the domain you intend to use with Coder.
2023-02-16 07:50:18 +03:00
2026-10-15 11:24:40 -04:00
2. Configure your DNS provider to point your coder.example.com and ` *.coder.example.com` to your server's public IP address.
2023-02-16 07:50:18 +03:00
2026-10-15 11:24:40 -04:00
> For example, to use ` coder.example.com` as your subdomain, configure ` coder.example.com` and ` *.coder.example.com` to point to your server's public ip.
> This can be done by adding A records in your DNS provider's dashboard.
2023-02-16 07:50:18 +03:00
3. Install Apache (assuming you're on Debian/Ubuntu):
2026-07-15 14:07:09 -04:00
` ``sh
2023-02-16 07:50:18 +03:00
sudo apt install apache2
` ``
4. Enable the following Apache modules:
2026-07-15 14:07:09 -04:00
` ``sh
2023-02-16 07:50:18 +03:00
sudo a2enmod proxy
sudo a2enmod proxy_http
sudo a2enmod ssl
sudo a2enmod rewrite
` ``
5. Stop Apache service and disable default site:
2026-07-15 14:07:09 -04:00
` ``sh
2023-02-16 07:50:18 +03:00
sudo a2dissite 000-default.conf
sudo systemctl stop apache2
` ``
## Install and configure LetsEncrypt Certbot
2026-10-15 11:24:40 -04:00
1. Install LetsEncrypt Certbot: Refer to the [CertBot documentation](https://certbot.eff.org/instructions?ws=apache&os=ubuntufocal&tab=wildcard).
2026-10-26 20:43:38 -04:00
2026-10-15 11:24:40 -04:00
Be sure to pick the wildcard tab and select your DNS provider for instructions to install the necessary DNS plugin.
2023-02-16 07:50:18 +03:00
## Create DNS provider credentials
2026-10-15 11:24:40 -04:00
This example assumes you're using CloudFlare as your DNS provider.
For other providers, refer to the [CertBot documentation](https://eff-certbot.readthedocs.io/en/stable/using.html#dns-plugins).
2023-02-16 07:50:18 +03:00
2026-10-23 22:27:18 -07:00
1. Create an API token for the DNS provider you're using, for example, [CloudFlare](https://developers.cloudflare.com/fundamentals/api/get-started/create-token) with the following permissions:
2023-02-16 07:50:18 +03:00
- Zone - DNS - Edit
2026-10-15 11:24:40 -04:00
2. Create a file in ` .secrets/certbot/cloudflare.ini` with the following content:
2023-02-16 07:50:18 +03:00
` ``ini
dns_cloudflare_api_token = YOUR_API_TOKEN
` ``
2026-07-15 14:07:09 -04:00
` ``sh
2023-02-16 07:50:18 +03:00
mkdir -p ~/.secrets/certbot
touch ~/.secrets/certbot/cloudflare.ini
nano ~/.secrets/certbot/cloudflare.ini
` ``
3. Set the correct permissions:
2026-07-15 14:07:09 -04:00
` ``sh
2023-02-16 07:50:18 +03:00
sudo chmod 600 ~/.secrets/certbot/cloudflare.ini
` ``
## Create the certificate
1. Create the wildcard certificate:
2026-07-15 14:07:09 -04:00
` ``sh
2023-02-16 07:50:18 +03:00
sudo certbot certonly --dns-cloudflare --dns-cloudflare-credentials ~/.secrets/certbot/cloudflare.ini -d coder.example.com -d *.coder.example.com
` ``
## Configure Apache
2026-10-15 11:24:40 -04:00
This example assumes Coder is running locally on ` 127.0.0.1:3000` and that you're using ` coder.example.com` as your subdomain.
2023-02-16 07:50:18 +03:00
1. Create Apache configuration for Coder:
2026-07-15 14:07:09 -04:00
` ``sh
2023-02-16 07:50:18 +03:00
sudo nano /etc/apache2/sites-available/coder.conf
` ``
2. Add the following content:
` ``apache
# Redirect HTTP to HTTPS
<VirtualHost *:80>
ServerName coder.example.com
ServerAlias *.coder.example.com
Redirect permanent / https://coder.example.com/
</VirtualHost>
<VirtualHost *:443>
ServerName coder.example.com
ServerAlias *.coder.example.com
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
2023-02-22 22:51:51 +03:00
ProxyPass / http://127.0.0.1:3000/ upgrade=any # required for websockets
2023-02-16 07:50:18 +03:00
ProxyPassReverse / http://127.0.0.1:3000/
ProxyRequests Off
ProxyPreserveHost On
RewriteEngine On
# Websockets are required for workspace connectivity
RewriteCond %{HTTP:Connection} Upgrade [NC]
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:3000/$1 [P,L]
SSLCertificateFile /etc/letsencrypt/live/coder.example.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/coder.example.com/privkey.pem
</VirtualHost>
` ``
2026-10-23 16:36:44 +00:00
> Do not forget to change: ` coder.example.com` by your (sub)domain
2023-02-16 07:50:18 +03:00
3. Enable the site:
2026-07-15 14:07:09 -04:00
` ``sh
2023-02-16 07:50:18 +03:00
sudo a2ensite coder.conf
` ``
4. Restart Apache:
2026-07-15 14:07:09 -04:00
` ``sh
2023-02-16 07:50:18 +03:00
sudo systemctl restart apache2
` ``
## Refresh certificates automatically
1. Create a new file in ` /etc/cron.weekly`:
2026-07-15 14:07:09 -04:00
` ``sh
2023-02-16 07:50:18 +03:00
sudo touch /etc/cron.weekly/certbot
` ``
2. Make it executable:
2026-07-15 14:07:09 -04:00
` ``sh
2023-02-16 07:50:18 +03:00
sudo chmod +x /etc/cron.weekly/certbot
` ``
3. And add this code:
2026-07-15 14:07:09 -04:00
` ``sh
2023-02-16 07:50:18 +03:00
#!/bin/sh
sudo certbot renew -q
` ``
2026-10-23 22:27:18 -07:00
And that's it, you should now be able to access Coder at your sub(domain), for example, ` https://coder.example.com`.