On 2026-11-02 14:27 UTC Olivier Boudet wrote:
> Hello,
> I'd like to report an issue we hit when upgrading from Solr 10.0.0 to
> 10.1.0.
>
> We run Solr behind a reverse proxy that only exposes the standard /solr
> path to the outside.
> With 10.0.0, the Admin UI works fine in this setup, all API calls are done
> with /solr/api/*.
> With 10.1.0, the Admin UI fails to load its data. Looking at the browser's
> network tab, the UI now sends its API calls to paths like /api/system/* at
> the root level, instead of calls living under the /solr path like before.
> Since our proxy only forwards /solr/* to Solr, these /api/* requests
> end with 404 errors.
> If we access Solr directly (bypassing the proxy), the 10.1.0 UI works as
> expected.
>
> Is this a known issue ? I couldn't find anything in the release notes
> explaining this change.
> Is there a parameter to configure this, I did not find anything ?
>
> If it's an unintended regression, do I need to open a new bug report ?
>
> Thank you
>
Thanks for reporting this!
10.1 is the first version of Solr to start really embracing the new V2 apis.
They live under /api and so you should add /api and /solr to your proxy.
There is a small mention of it in
https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-10.html#v2-api
but maybe we should have highlighted it under "Solr Admin UI" header?
Eric