Skip to content

Admin panel does not support sub-path deployments #54

Description

@glebovmaksim

Static assets are always requested from the domain root (/assets/...), so deploying the admin panel behind a reverse proxy at a path like /chat/admin results in 404s for all JS/CSS bundles.

For comparison, the main LibreChat application handles this fine — setting DOMAIN_CLIENT and DOMAIN_SERVER to something like https://example.com/chat is enough. The admin panel has no equivalent.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions