Does Logto support ENDPOINT and ADMIN_ENDPOINT under the same domain?

[zdzym]

I have tested the following config:
ENDPOINT = https://auth.example.com
ADMIN_ENDPOINT = https://auth.example.com/logto

And nginx is configured to forward requests on /logto to port 3002.

when I visited https://auth.example.com/logto, it returned a 404 page.

I'd like to know if there's something wrong with my configuration, or if this configuration isn't currently supported? Thanks.

[mg1986jp]

I don't think Logto supports path-based routing for the admin endpoint. The admin console and the main auth endpoints are separate services (port 3001 vs 3002), and they expect to be at the root of their respective origins.

You'd probably need to use a subdomain instead:

ENDPOINT=https://auth.example.com
ADMIN_ENDPOINT=https://admin-auth.example.com

And configure nginx to proxy admin-auth.example.com to port 3002 and auth.example.com to port 3001.

The 404 you're getting on /logto is likely because Logto's admin app serves its routes from / and doesn't understand a path prefix. You'd need something like --basePath support which I don't think exists yet.