Replies: 1 comment
-
|
ports: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone!
I'm hoping you can help me understand what I'm doing wrong. I'm working on integrating Logto into my application. Without a proxy server, everything works perfectly and was quite easy to set up. However, I've been struggling with the proxy setup for a week now and I'm completely stuck.
I've been following this guide as a base: https://docs.logto.io/logto-oss/deployment-and-configuration#reverse-proxy. I've found similar configurations in a couple of online posts, but couldn't find any other information on the topic. I also didn't find anything new for my situation in this discussion: https://github.com/orgs/logto-io/discussions/1779.
Here's the issue in detail:
When I run Logto behind the proxy server, everything starts up and there are no error messages in the logs. However, when I try to access the admin console on port 7778, I get a 302 Found response, which immediately redirects me to the Logto auth page on port 7777, where I see a "404 Session not found" message.
The strange part is that if I open the console URL directly in another tab, bypassing the proxy, on port 3002, it loads the welcome page just fine (i.d., http://localhost:3002/console/welcome).
I've created a repository with the docker-compose.yaml and nginx.conf files I'm using, and I'm also including them below for convenience.
https://github.com/Leonich77/logtonix
Could you please point me in the right direction or suggest what the problem might be?
Thanks in advance!
File docker-compose.yam
File nginx.conf
Beta Was this translation helpful? Give feedback.
All reactions