Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bug: Unable to access the admin panel in ARM64 #6933

Closed
2 of 4 tasks
AlexMa2011 opened this issue Jan 11, 2025 · 13 comments
Closed
2 of 4 tasks

bug: Unable to access the admin panel in ARM64 #6933

AlexMa2011 opened this issue Jan 11, 2025 · 13 comments
Labels
bug Something isn't working

Comments

@AlexMa2011
Copy link

AlexMa2011 commented Jan 11, 2025 •
edited
Loading

Describe the bug

Unable to access the admin panel {ADMIN_ENDPOINT}
When accessing the admin panel, automatically redirected to {ENDPOINT}unknown-session
And prompt that the '404 page does not exist. Session not found, please return and log in again.'

Expected behavior

Normal login, and can create an account

How to reproduce?

Download this compose file compose.yaml.txt
Run command docker compose up

Context

OrangePi5 Plus(ARM64)

  • Logto Cloud
  • Self-hosted, Logto version = 1.23
    • Container (Docker image)
    • Raw Node.js

Screenshots

截屏2025-01-11 14 00 52

Log

log1.txt
@AlexMa2011 AlexMa2011 added the bug Something isn't working label Jan 11, 2025
@AlexMa2011 AlexMa2011 changed the title bug: bug: Unable to access the admin panel Jan 11, 2025
@AlexMa2011
Copy link
Author

I use Nginx Proxy Manager to reverse proxy services

@AlexMa2011
Copy link
Author

admin-panel-nginx.conf.txt
core-nginx.conf.txt
These are the nginx configuration files

@iamsee
Copy link

iamsee commented Jan 13, 2025

same error

@JoeChen2me
Copy link

I can log in the admin UI but the admin account display is not correct and I can log in in my application!
image

@AlexMa2011
Copy link
Author

I have tried the following:
Accessing Logto directly via IP address
Downgrading postgres:17-alpine to postgres:14-alpine
Resetting postgres
Perhaps arm64 is not supported, I will try and64

I can log in the admin UI but the admin account display is not correct and I can log in in my application! image
What architecture are you using? Can you show me the configuration file (without secrets)?

@JoeChen2me
Copy link

JoeChen2me commented Jan 14, 2025 •
edited
Loading

I have tried the following: Accessing Logto directly via IP address Downgrading postgres:17-alpine to postgres:14-alpine Resetting postgres Perhaps arm64 is not supported, I will try and64

I can log in the admin UI but the admin account display is not correct and I can log in in my application! image
What architecture are you using? Can you show me the configuration file (without secrets)?

My architecture is ARM64, and the configuration is as follow:

name: lobe-chat-database
services:
  postgresql:
    image: pgvector/pgvector:pg16
    container_name: lobe-postgres
    ports:
      - '5432:5432'
    volumes:
      - './data:/var/lib/postgresql/data'
    environment:
      - 'POSTGRES_DB=lobe'
      - 'POSTGRES_PASSWORD=uWNZugjBqixf8dxC'
    healthcheck:
      test: ['CMD-SHELL', 'pg_isready -U postgres']
      interval: 5s
      timeout: 5s
      retries: 5
    restart: always

  minio:
    image: minio/minio
    container_name: lobe-minio
    ports:
      - '9000:9000'
      - '9001:9001'
    volumes:
      - './s3_data:/etc/minio/data'
    environment:
      - 'MINIO_ROOT_USER=YOUR_MINIO_USER'
      - 'MINIO_ROOT_PASSWORD=YOUR_MINIO_PASSWORD'
      - 'MINIO_DOMAIN=lobe-s3-api.xxx.top'
      - 'MINIO_API_CORS_ALLOW_ORIGIN=https://lobe.xxx.top' # Your LobeChat's domain name.
    restart: always
    command: >
      server /etc/minio/data --address ":9000" --console-address ":9001"


  logto:
    image: svhd/logto
    container_name: lobe-logto
    ports:
      - '3001:3001'
      - '3002:3002'
    depends_on:
      postgresql:
        condition: service_healthy
    environment:
      - 'TRUST_PROXY_HEADER=1'
      - 'DB_URL=postgresql://postgres:uWNZugjBqixf8dxC@postgresql:5432/logto'
      - 'ENDPOINT=https://lobe-auth-api.xxx.top'
      - 'ADMIN_ENDPOINT=https://lobe-auth-ui.xxx.top'
    entrypoint: ['sh', '-c', 'npm run cli db seed -- --swe && npm start']

  lobe:
    image: lobehub/lobe-chat-database
    container_name: lobe-chat
    ports:
      - '3210:3210'
    depends_on:
      - postgresql
      - minio
      - logto
    env_file:
      - .env
    restart: always

volumes:
  data:
    driver: local
  s3_data:
    driver: local

and the .env file is :

AUTH_LOGTO_ID=92356u9vvwjm82lrd4b6l
AUTH_LOGTO_SECRET=YP56HvYUaVXpeaPh6uU96exkjeaTNLDz
AUTH_LOGTO_ISSUER=https://lobe-auth-api.xxx.top/oidc

and the file tree is

root@xxxxx:~/lobe-chat-db# ls
data  docker-compose.yml    s3_data  .env

with configuration above ,I run docker compose up -d and visit ip:3002, sometimes I can log in . But even if I can log in, the admin account display is not correct as I mentioned in the comment above.

@AlexMa2011

This comment has been minimized.

Sign in to view
@AlexMa2011

This comment has been minimized.

Sign in to view
@AlexMa2011
Copy link
Author

我将compose.yaml文件转移到了我的x86主机上，并且成功启动了。所以这是一个基于ARM64的特特定问题
I transferred the compose.yaml file to my x86 host and it started successfully. So this is a specific ARM64 based issue

@AlexMa2011 AlexMa2011 changed the title bug: Unable to access the admin panel bug: Unable to access the admin panel in ARM64 Jan 17, 2025
@AlexMa2011
Copy link
Author

AlexMa2011 commented Jan 20, 2025 via email

@charIeszhao
Copy link
Member

我将compose.yaml文件转移到了我的x86主机上，并且成功启动了。所以这是一个基于ARM64的特特定问题 I transferred the compose.yaml file to my x86 host and it started successfully. So this is a specific ARM64 based issue

Are you using the exact same configs on your new x86 machine?

From my point of view, your initial issue might be caused by the additional port number :100 in your endpoints.

@AlexMa2011
Copy link
Author

From my point of view, your initial issue might be caused by the additional port number :100 in your endpoints.

是的，这是一个关于反向代理的问题。
如何在 Nginx 代理管理器中正确配置？
Yes, this is a question about reverse proxies.
How to configure the correct configuration in Nginx Proxy Manager, please?

@charIeszhao
Copy link
Member

From my point of view, your initial issue might be caused by the additional port number :100 in your endpoints.

是的，这是一个关于反向代理的问题。 如何在 Nginx 代理管理器中正确配置？ Yes, this is a question about reverse proxies. How to configure the correct configuration in Nginx Proxy Manager, please?

I'm not an expert but I think if you use port number, you should use $http_host instead of $host in nginx.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Milestone
No milestone
Development

No branches or pull requests
4 participants
@iamsee @charIeszhao @JoeChen2me @AlexMa2011