1. run solr on different port other than 8983. 2. If you are exposing it publicly, dont expose through port. But have a apache/nignx server in middle to pass traffic to solr.
cheers On Thu, Jul 13, 2017 at 11:13 PM, Susheel Kumar <susheel2...@gmail.com> wrote: > But don't expose Solr outside to public... > > On Thu, Jul 13, 2017 at 1:41 PM, Susheel Kumar <susheel2...@gmail.com> > wrote: > > > This window solr server must have a name and IP address associated with > > it. Check from external content deliver servers if port 8983 to Solr > server > > is open and if so you can refer solr via http://<machinename>:<port>/ > solr. > > if port 8983 is not open then try to run solr 80/8080 or work with > > network team to open the ports. If you need to access solr server by > > domain name then you would have to ask network team to create a DNS/VIP > and > > map it to solr IP address. > > > > Enjoy!!! > > > > > > > > > > > > > > On Thu, Jul 13, 2017 at 1:23 PM, Bertini, Vickie < > > vickie.bert...@bannerhealth.com> wrote: > > > >> I have installed Solr 6.5.1 as a service on our Windows Server 2012. It > >> is up and running properly under localhost:8983, however, I have a > domain > >> name I want to assign to it so our external content delivery servers can > >> reach it for our web search. However, I am very new to Solr and mostly > only > >> familiar with IIS, not jetty, so is there documentation on how I would > >> configure solr to run on our new domain/IP instead of localhost? Web > >> searches up to this point have been fairly unproductive and unhelpful. > >> > >> > >> > >> *Vickie Bertini* > >> IT Sitecore Architect > >> > >> Digital Business Technology > >> 602.747.7186 <(602)%20747-7186> office > >> > >> > >> > >> <https://www.bannerhealth.com/> > >> > >> > >> > > > > >
