How to setup subdomain for tenants in Django app running in droplet

Question

thanks in advance. I have a Django app using Django-tenants. The app runs well locally but I haven’t been able to solve the subdomain for tenants. So far:

I have a public and a test schema with superusers created.
I tried all combinations os allowed host, *.mydomain.com, ip, *.www.mydomain.com, now I’m testing with ‘.*’, ‘*’
I have a wildcard SSL certificate installed in the server.
Currently I have an A record with * pointing to my droplet ip, also tried CNAME.
So far I can only access to the top domain of the app, and not to subdmains.
Here is the relevant code/conf.

server {
    listen 80;
    server_name *.mydomain;
    location / {
        rewrite ^ http://mydomain;
    }
}

server {
    listen 443 ssl http2;
    server_name *.mydomain.com;

    ssl_certificate /etc/nginx/ssl/mydomain_com_chain.crt;
    ssl_certificate_key /etc/nginx/ssl/mydomain.com.key;

    # SSL/TLS security settings
    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    ssl_prefer_server_ciphers on;
    ssl_ciphers 'EECDxxxxxxxxxxxxxxxxxx';

    location = /favicon.ico {
        access_log off;
        log_not_found off;
    }

    location /staticfiles/ {
        root /root/project;
    }

    location / {
        include proxy_params;
        proxy_pass http://unix:/run/gunicorn.sock;
    }
}

Hope someone can help me out. Thanks!!

Bobby Iliev · Accepted Answer

Hello there!

The setup for the Django-tenants library using subdomains can be a bit tricky indeed.

You mentioned that you have already tried various configurations which sounds correct, what is the exact error that you currently get when you visit a tenant’s subdomain?

Let’s look at the configuration of Nginx and the Django settings:

Nginx Configuration: Make sure that the server_name directive in the Nginx configuration file correctly captures all subdomains:

server {
    listen 443 ssl http2;
    server_name *.mydomain.com mydomain.com;

    # ...
}

The server_name should be set to *.mydomain.com and mydomain.com so that it can serve both the root domain and any subdomains.

Django settings.py: For your ALLOWED_HOSTS in your settings.py file, try using ['.mydomain.com', 'mydomain.com']. The leading dot allows all subdomains.
Django-tenants: Make sure you have correctly set up the Django-tenants middleware. In your settings.py, you should have something like:

MIDDLEWARE = [
    ...
    'django_tenants.middleware.main.TenantMainMiddleware',
    ...
]

Ensure that your TENANT_MODEL is correctly set too.

Check your tenants: Make sure that your tenants have been set up correctly with the right domain_url value.

Lastly, consider checking your logs for any error messages. Django’s logs can be very helpful, and so can Nginx’s. You can view the Nginx error logs with sudo tail -f /var/log/nginx/error.log.

UPDATE: The issue was related to DNS propagation and it was working fine on the next day!

Let me know how it goes!

Best,

Bobby

Alejandro Arancibia V · Answer

thanks for the quick response. Today is working 😃, so I guess it was just a slowed dns propagation problem (just my thoughts on this). Just in case some has problems with this library I had to migrate all apps in shared apps and then move te tenants ones to tenant, otherwise I kept having migration problems. Thanks Bob!

Question

How to setup subdomain for tenants in Django app running in droplet

Try DigitalOcean for free

Popular Topics

Featured on Community

Get our biweekly newsletter

Hollie's Hub for Good

Become a contributor

Featured Tutorials

DigitalOcean Products

Welcome to the developer cloud