You could configure a reverse proxy to provide one or more means of authentication.
However, I agree that the purpose why this is done should be clarified. > Am 01.01.2019 um 19:02 schrieb Kay Wrobel <kwro...@hawkusa.com>: > > You can use ssh to tunnel in. > > ssh -L8983:localhost:8983 use...@myremoteserver.example.com > > This will only require port 22 to be exposed to the public. > > > Sent from my iPhone > >> On Jan 1, 2019, at 11:43 AM, Gus Heck <gus.h...@gmail.com> wrote: >> >> Why would you want to expose the administration gui on the web? This is a >> very hazardous thing to do. Never mind that it normally also runs on 8983 >> and all it's functionality relies on the ability to interact with 8983 >> hosted api end points. >> >> What are you actually trying to solve? >> >> On Dec 31, 2018 6:04 PM, "Jörn Franke" <jornfra...@gmail.com> wrote: >> >> Reverse proxy? >> >> >>> Am 31.12.2018 um 22:48 schrieb s...@cid.is: >>> >>> Hi all, >>> >>> is there a way, better a solution, to access the Solr Admin GUI from >> outside the server (via public web) while the Solr port 8983 is closed by a >> firewall and only available inside the server via localhost? >>> >>> Thanks in advance >>> Walter Claassen >>> >>> Alexandraweg 32 >>> D 64287 Darmstadt >>> Fon +49-6151-4937961 >>> Fax +49-6151-4937969 >>> c...@cid.is >>> > > -- > > The information in this e-mail is confidential and is intended solely for > the addressee(s). Access to this email by anyone else is unauthorized. If > you are not an intended recipient, you may not print, save or otherwise > store the e-mail or any of the contents thereof in electronic or physical > form, nor copy, use or disseminate the information contained in the email. > If you are not an intended recipient, please notify the sender of this > email immediately.
