The reason every variant sends you to the create-database screen is that dbfilter doesn't map "domain → database" the way the names suggest. Odoo takes the incoming hostname, substitutes it into the pattern, and matches the result against your database names:

• %h = the full hostname (e.g. mydomain1.com)
• %d = the first label of the hostname, i.e. everything before the first dot (e.g. mydomain1)

So dbfilter = ^%d$ on a request to mydomain1.com resolves to ^mydomain1$ and looks for a database literally named mydomain1. Your databases are named DatabaseA and DBossB, which match none of these patterns, Odoo finds zero eligible databases and falls through to the manager.

The easiest way to fix this would be to rename DatabaseA → mydomain1.com and DBossB → myurl2.com, then:

[options]
proxy_mode = True
dbfilter = ^%h$
list_db = False

%h$ now resolves to the full hostname per request and matches the identically-named DB. proxy_mode = True is required so Odoo trusts the Host/X-Forwarded-* headers from your proxy instead of seeing localhost. This is the easiest setup.

The reverse proxy setup for Nginx or Apache would look like this:

Nginx

upstream odoo { server 127.0.0.1:8069; }

server {
    listen 80;
    server_name mydomain1.com;
    location / {
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_redirect off;
        proxy_pass http://odoo;
    }
}

Duplicate that block with server_name myurl2.com;

If you're using Apache as your Reverse Proxy:

<VirtualHost *:80>
    ServerName mydomain1.com
    ProxyPreserveHost On
    RequestHeader set X-Forwarded-Proto "http"
    ProxyPass / http://127.0.0.1:8069/
    ProxyPassReverse / http://127.0.0.1:8069/
</VirtualHost>

ProxyPreserveHost On is the Apache counterpart to nginx's proxy_set_header Host.

Hello, 

This is usually caused by the dbfilter pattern not matching your actual database names.

The configuration dbfilter = ^%d$ works only when the database name matches the domain name (for example, mydomain1 → mydomain1.com).

If your databases are named differently (e.g., DatabaseA and DBossB), Odoo will not find a matching database and may redirect to the database manager page.

Please verify:

• The database names match your dbfilter rule.
• proxy_mode = True is enabled if you are using Nginx/Apache as a reverse proxy.
• The domains are correctly pointing to the Odoo instance and sending the proper Host header.

In cases where database names differ from domain names, you may need a custom dbfilter expression or rename the databases to align with the domain pattern.

Hope this works for you! If you need any help implementing this or want a more optimized approach, feel free to reach out for further discussion.

Regards,

Zehntech Technologies Inc.

santosh.sekwadia@zehntech.com

The issue is that dbfilter = ^%d$ relies on the subdomain matching the database name exactly. When your domain is mydomain1.com, Odoo extracts the hostname and tries to match it against the regex pattern — but mydomain1.com does not match DatabaseA because there is no subdomain to extract.

The production-safe solution is to use %h with nginx rewriting the Host header per domain.

Step 1 — odoo.conf

dbfilter = ^%h$
list_db = False

Step 2 — nginx config for each domain

For mydomain1.com:

server {
    server_name mydomain1.com;
    location / {
        proxy_pass http://127.0.0.1:8069;
        proxy_set_header Host DatabaseA;
        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;
    }
}

For myurl2.com:

server {
    server_name myurl2.com;
    location / {
        proxy_pass http://127.0.0.1:8069;
        proxy_set_header Host DBossB;
        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;
    }
}

Why this works:

proxy_set_header Host DatabaseA rewrites the Host header Odoo receives to match your database name exactly. The dbfilter ^%h$ then matches the rewritten host against your database name and connects automatically with no selector shown.

Why your current setup fails:

^%d$ extracts only the subdomain portion. On a root domain like mydomain1.com there is no subdomain — %d returns empty, the filter matches nothing, and Odoo falls back to the database creation screen.

After updating nginx:

sudo nginx -t && sudo systemctl reload nginx
sudo systemctl restart odoo

Muhammad Gharis Javed — Odoo v17/18/19 Backend Engineer