Serving a Solara app with an existing FastAPI application using jupyter-server-proxy

[edan-bainglass]

The Solara documentation suggests one can serve a Solara app from an existing FastAPI application.
https://solara.dev/documentation/getting_started/deploying/self-hosted#fastapi

Not sure if this is expected behavior, but some Jupyter static files aren't served properly this way (see below). Running the documented command (via uvicorn) directly yields the output below, but it is still successful (app is up and running). However, serving the same command by way of jupyter-server-proxy fails the WebSocker part as well.

Any ideas as to what is happening and how to fix it?

INFO:     Uvicorn running on http://127.0.0.1:9005 (Press CTRL+C to quit)
INFO:     Started reloader process [166856] using WatchFiles
INFO:     Started server process [166860]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     127.0.0.1:42754 - "GET / HTTP/1.1" 200 OK
INFO:     127.0.0.1:42770 - "GET /jupyter/base/js/namespace.js HTTP/1.1" 404 Not Found
INFO:     127.0.0.1:42754 - "GET /jupyter/jquery.js HTTP/1.1" 404 Not Found
INFO:     127.0.0.1:42754 - "GET /jupyter/base/js/events.js HTTP/1.1" 404 Not Found
INFO:     127.0.0.1:42770 - "GET /jupyter/base/js/dialog.js HTTP/1.1" 404 Not Found
INFO:     127.0.0.1:42754 - "GET /jupyter/base/js/utils.js HTTP/1.1" 404 Not Found
INFO:     127.0.0.1:42784 - "WebSocket /jupyter/api/kernels/66d06f26-a808-4e82-8187-2ec6e67f20f0/channels?session_id=1a720398-2c7e-44c6-813f-516c57bc1bdc" [accepted]
INFO:     connection open