If the keys line up nicely across jumps...
On Wed, Jan 2, 2019, 10:49 AM Kay Wrobel In case of multiple "jumps", might I suggest the -J switch which allows
> you to specify a jump host.
>
> Kay
>
> > On Jan 2, 2019, at 9:37 AM, Gus Heck wrote:
> >
> > I typically resolve this sort of situation
In case of multiple "jumps", might I suggest the -J switch which allows you to
specify a jump host.
Kay
> On Jan 2, 2019, at 9:37 AM, Gus Heck wrote:
>
> I typically resolve this sort of situation with a ssh proxy such as
>
> ssh -f user@123.456.789.012 -L :127.0.0.1:8983 -N
>
> Then I
I typically resolve this sort of situation with a ssh proxy such as
ssh -f user@123.456.789.012 -L :127.0.0.1:8983 -N
Then I can access the solr GUI from localhost: on my machine, and all
the traffic is secured by SSH. Pick your local port ( here) as desired
of course. Sometimes I
In this case create a VPN and then access it.
> Am 02.01.2019 um 11:03 schrieb s...@cid.is:
>
> First I want to thank you for your comments.
> Second I'll add some background information.
>
> Here Solr is part of a complex information management project, which I
> developed for a customer and
First I want to thank you for your comments.
Second I'll add some background information.
Here Solr is part of a complex information management project, which I
developed for a customer and which includes different source
databases, containing edited/imported/crawled content.
This project
On 12/31/2018 2:48 PM, s...@cid.is wrote:
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?
If you've blocked the Solr port, then you
I think a better approach to tunneling would be:
ssh -p -L :localhost:8983 use...@myremoteserver.example.com
This requires you to set up a different port () rather than use the
standard 22 port (on your router and on your sshd config). I've been
running something like this for
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 :
>
> You can use ssh to tunnel in.
>
> ssh -L8983:localhost:8983
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 wrote:
>
> Why would you want to expose the administration gui on the web? This
Yes, exposing the admin UI on the web is very dangerous. Anyone who finds it
can delete all your collections. That UI is designed for “back office” use only.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jan 1, 2019, at 9:43 AM, Gus Heck 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
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?
>
>
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
13 matches
Mail list logo
