Skip to main content

Nginx Proxying

As Strapi does not handle SSL directly and hosting a Node.js service on the "edge" network is not a secure solution it is recommended that you use some sort of proxy application such as Nginx, Apache, HAProxy, Traefik, or others. The following documentation provides some sample configurations for Nginx, naturally these configs may not suit all environments and you will likely need to adjust them to fit your needs.


The following configuration is based on Nginx virtual hosts, this means that you create configurations for each domain to allow serving multiple domains on the same port such as 80 (HTTP) or 443 (HTTPS). It also uses a central upstream file to store an alias to allow for easier management, load balancing, and failover in the case of clustering multiple Strapi deployments.

Strapi server

In order to take full advantage of a proxied Strapi application, Strapi should be configured so it's aware of the upstream proxy. Like with the below configurations there are 3 matching examples. Additional information can be found in the server configuration and admin configuration documentations.

✏️ Note

These examples use the default API Prefix of /api. This can be changed without the need to directly modify the Nginx configuration (see the API prefix documentation).


If the url key is changed in the ./config/admin.js or ./config/server.js files, the admin panel needs to be rebuilt with yarn build or npm run build.

Subdomain Strapi configuration

  • Example domain:
  • Example admin:
  • Example API:
  • Example uploaded files (local provider):
path: ./config/server.js

module.exports = ({ env }) => ({
host: env('HOST', ''),
port:'PORT', 1337),
url: '',

Nginx Upstream

Upstream blocks are used to map an alias such as strapi to a specific URL such as localhost:1337. While it would be useful to define these in each virtual host file, Nginx currently doesn't support loading these within the virtual host if you have multiple virtual host files. Instead, configure these within the conf.d directory as this is loaded before any virtual host files.

In the following configuration the localhost:1337 is mapped to the Nginx alias strapi:

# path: /etc/nginx/conf.d/upstream.conf

# Strapi server
upstream strapi {

Nginx Virtual Host

Virtual host files are what store the configuration for a specific app, service, or proxied service. For usage with Strapi this virtual host file is handling HTTPS connections and proxying them to Strapi running locally on the server. This configuration also redirects all HTTP requests to HTTPs using a 301 redirect.

In the following examples you will need to replace your domain and likewise your paths to SSL certificates will need to be changed based on where you place them or, if you are using Let's Encrypt, where your script places them. Please also note that while the following path shows sites-available you will need to symlink the file to sites-enabled in order for Nginx to enable the config.

The following are 2 example Nginx configurations:

  • subdomain based such as
  • subfolder based with both the API and Admin on the same subfolder such as and
✏️ Subfolder split is not supported

Using subfolder split (eg: and are not supported nor recommended with Strapi. It's advised that you either use subdomains (eg: or subfolder unified (eg: and


This configuration is using the subdomain that is dedicated to Strapi only. It will redirect normal HTTP traffic over to SSL and proxies all requests (both API and admin) to the Strapi server running on the upstream alias configured above.

  • Example domain:
  • Example admin panel:
  • Example API:
  • Example uploaded Files (local provider):
# path: /etc/nginx/sites-available/strapi.conf

server {
# Listen HTTP
listen 80;

# Redirect HTTP to HTTPS
return 301 https://$host$request_uri;

server {
# Listen HTTPS
listen 443 ssl;

# SSL config
ssl_certificate /path/to/your/certificate/file;
ssl_certificate_key /path/to/your/certificate/key;

# Proxy Config
location / {
proxy_pass http://strapi;
proxy_http_version 1.1;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $http_host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_pass_request_headers on;

Redirecting landing page to admin panel

If you do not wish to have the default landing page mounted on / you can create a custom middleware using the sample code below to automatically redirect to your admin panel.


This sample configuration expects that the admin panel is accessible on /admin. If you used one of the above configurations to change this to /dashboard you will also need to adjust this sample configuration.

module.exports = ({ env }) => [
// ...
{ resolve: '../src/middlewares/admin-redirect' },

module.exports = (_config, { strapi }) => {
const redirects = ['/', '/index.html'].map((path) => ({
method: 'GET',
handler: (ctx) => ctx.redirect('/admin'),
config: { auth: false },