Running Karrio Dashboard and API under a URL Subpath

[Flo-Ride (flo-ride)]

I am attempting to run Karrio (Dashboard and API) behind an Apache reverse proxy, specifically hosting the services under non-root subpaths:

• Dashboard: https://mydomain.com/karrio
• API: https://mydomain.com/karrio/api (or /karrioapi i've tried too)

I have successfully configured the Docker environment to remove Caddy and exposed the internal ports (3002 and 5002). However, I am encountering issues with the Dashboard being unable to reach the API, suggesting the application may not be handling the subpath prefixes correctly, or redirect me to the / subpath (where my main app is)

Configuration Details

I have configured the Dashboard's public environment variables to reflect the desired subpaths:
docker-compose.yaml

# ... other config
dashboard:
     # ...
    environment:
      # ...
      NEXT_PUBLIC_DASHBOARD_URL: https://mydomain.com/karrio
      NEXT_PUBLIC_KARRIO_PUBLIC_URL: https://mydomain.com/karrio/api
      KARRIO_URL: http://api:5002 #  I also tested where i set the same as NEXT_PUBLIC_KARRIO_PUBLIC_URL
# ... other config

2. Apache Reverse Proxy

    # ... other config
    # --- Karrio API and Dashboard ---
    # Proxy WebSockets for Dashboard
    ProxyPass /karrio/ws ws://localhost:3002/ws
    ProxyPassReverse /karrio/ws/ ws://localhost:3002/ws
    # Proxy the main Karrio application and API routes
    ProxyPass /karrio http://127.0.0.1:3002/karrio
    ProxyPassReverse /karrio http://127.0.0.1:3002
    ProxyPass /karrio/api http://127.0.0.1:5002/karrio/api
    ProxyPassReverse /karrio/api http://127.0.0.1:5002/karrio/api
    # ... other config

Question

• Is running the Karrio Dashboard and API under different, non-root subpaths officially supported?

Thank you for any guidance you can provide on deploying Karrio in a subdirectory structure :).

[Dan (danh91)]

Hi Flo-Ride (@flo-ride) ,
To be honest with you, we stopped maintaining the subpaths setup for the dashboard since we moved to Nextjs app router 😅.

If anyone else had a working deployment with that, I'd be surprised. Let us know