https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html#security
Specifically the following section: Solr now binds to localhost network interface by default for better out of > the box security. Administrators that need Solr exposed more broadly can > change the SOLR_JETTY_HOST property in their Solr include ( > solr.in.sh/solr.in.cmd) file. SOLR_JETTY_HOST is also documented in these two places: * https://solr.apache.org/guide/solr/latest/deployment-guide/securing-solr.html#network-configuration * https://solr.apache.org/guide/solr/latest/deployment-guide/taking-solr-to-production.html#security-considerations Kevin Risden On Wed, Dec 14, 2022 at 10:28 AM Oakley, Craig (NIH/NLM/NCBI) [C] <craig.oak...@nih.gov.invalid> wrote: > Update: I find that if I specify the hostname as localhost (running on the > same host as the Solr instance) than it does get in. Is there some > configuration into which certain host names should be added? > > -----Original Message----- > From: Oakley, Craig (NIH/NLM/NCBI) [C] <craig.oak...@nih.gov.INVALID> > Sent: Wednesday, December 14, 2022 10:01 AM > To: users@solr.apache.org > Subject: connecting to Solr 9.1 > > I'm trying to upgrade from Solr 8.5.2 to Solr 9.1 > > After installing the software and starting the instance I cannot connect, > receiving such messages as > curl: (7) Failed connect to hostname:port; Connection refused > > I cannot connect through a browser either. Attempts to connect do not show > up in solr.log (but if I use zkcli.sh to implement security.json, that does > show up in solr.log: note that I cannot connect when there is no > security.json, so that is not the issue). > > Is there some under-documented security control preventing connection? >
