Thanks for the reply.  This got me further.

I looked at the solr start script and it appeared to not use the 
solr.jetty.host parameter when -Dhost is being used.

Regardless, I now have added this in solr.in.sh:
SOLR_JETTY_HOST="0.0.0.0"

And now the browser connects, but goes to a login page:

Basic Authentication
Unauthorized
Solr requires authentication for resource Dashboard.
Please log in with your username and password for realm solr.

As far as I know, this installation has never used solr authentication.  Our 
custom apps don't pass any credentials when talking to solr, and I have never 
need to log in to access the admin UI.

In the solr8 admin, when I click the Security link on the left side, it 
displays:

Current user is not authenticated! Security panel is disabled.

 You do not have permission to view the security panel.

But all the other features continue to work.


So now, maybe if I can figure out how to disable authentication, then 
(hopefully) I'll be back in business.

Thanks,
Jay


-----Original Message-----
From: Alex The Rocker <[email protected]>
Sent: Friday, March 1, 2024 2:00 PM
To: [email protected]
Cc: [email protected]
Subject: [External] Re: Solr 9 Hostname configuration issue

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.


Hello Jay,

Have you tried to apply the answer to this question:
https://stackoverflow.com/questions/73817848/solr-9-ui-not-loading-but-working-with-cli
?
(looks like Solr 9 is more "secure by default" than Solr 8 was...)

Alex

Le ven. 1 mars 2024 à 19:40, Silverman, Harry (Contractor) 
<[email protected]> a écrit :
>
> Hello experts -
>
> I suspect that I have a configuration issue with respect to the hostname.
>
> I have ported our solr core from 8.11 to 9.4.
>
> Solr 9.4 appears to start normally (no errors in the logs).
>
> But when I point my browser to hostname:port - it gets no response.  It seems 
> to be listening on localhost, but not on the actual server name.
>
> The solr start command has this parameter:
> -Dhost=sandbox-search-index-004
> (we are also running on port 8080)
>
> From a bash shell on the remote linux server where solr is running, I tried 
> curl, I get "Failed to connect" and "Connection refused":
>
> -bash-4.4$ curl sandbox-search-index-004:8080/solr/
> curl: (7) Failed to connect to sandbox-search-index-004 port 8080:
> Connection refused
>
> But I get a response if it use localhost instead:
>
> -bash-4.4$ curl localhost:8080/solr/
> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
> http://www.w/
> 3.org%2FTR%2Fhtml4%2Fstrict.dtd&data=05%7C02%7Cjsilverman%40gpo.gov%7C
> 09146da4d6094bb23b6408dc3a21efd5%7C97ae4de0d4584af3a7df1c19bdbe49d0%7C
> 0%7C0%7C638449164649287949%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA
> iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=x79
> PayYf1mbT5TMwZU1D6xgG%2BU7dqY256%2BvqK18Sd5U%3D&reserved=0>
> <html ng-app="solrAdminApp" ng-csp>
> <!--
> Licensed to the Apache Software Foundation (ASF) under one or more
> contributor license agreements.  See the NOTICE file distributed with
> this work for additional information regarding copyright ownership.
> ...
>
>
> I have limited access on this server.  The local IT guy provided this 
> feedback:
> "The firewall has the port open".
> "It looks like it's misconfigured to listen locally and not on the hostname".
>
> He also showed a telnet connection working to localhost, but not to the 
> hostname.
>
> $ telnet sandbox-search-index-004 8080 Trying 172.19.63.13...
> telnet: connect to address 172.19.63.13: Connection refused
>
> And netstat showing it is only listening on localhost:
>
>
> # netstat -nap |grep 8080
>
> tcp6       0      0 127.0.0.1:8080          :::*                    LISTEN    
>   1778220/java
>
> #
>
> Suggestions appreciated!
> Jay

Reply via email to