bug: Deployment with nginx reverse proxy about logto HOT 7 CLOSED

This is an aside.

I have been using Logto, and based on my experience,
I recommend using port 443 for reverse proxy and employing subdomains rather than running it on ports other than 443...
That will probably work better.

from logto.

It seems to be a mismatch with the ADMIN_ENDPOINT. Could you try using http or localhost first?

from logto.

You don't have the environment variables listed in the app service of the docker compose.

from logto.

@hades200082
The environment variables are listed in the .env file and are transferred to the container on this line ./.env:/etc/logto/.env.
I think the logto app has access to them because if their values are different, the app's behavior also changes.

from logto.

I have access to logto locally, tested with curl localhost:3002. I thought that ADMIN_ENDPOINT specifies a URL to my custom domain for production. What is the logic to set it to http or localhost? Is it possible the problem to be with the headers that I set in the proxy server?

from logto.

@calloc134 Thank you very much! For some reason it only works with subdomains.

from logto.

@calloc134 Thank you very much! For some reason it only works with subdomains.

is this a official result? i use subdomain but a port as 8443 nor 443 can not work.

from logto.