12:05 p.m.
On 01/28/2017 09:28 AM, Yaniv Kaul wrote:
On Jan 27, 2017 12:32 PM, "Juan Hernández" <jhernand(a)redhat.com
<mailto:jhernand@redhat.com>> wrote:
On 01/27/2017 11:56 AM, Alex wrote:
> Hi,
>
> I added the IP address at 11-setup-sso.conf (found at
> /etc/ovirt-engine/engine.conf.d), at line
SSO_ALTERNATE_ENGINE_FQDNS="IP".
> Then restarted engine.
> I can access now engine vm using IP, but I cannot when connecting
> remotely using localhost and port forwarding through ssh. I tried
to add
> also localhost as alternate fqdn without any luck.
> Any idea?
>
> Many thanx,
> Alex
>
Make sure to include also the port number that you are using. For
example, if you are using port 10000 then you will need this:
SSO_ALTERNATE_ENGINE_FQDNS="localhost:10000"
I'd also suggest to avoid modifying the 11-setup-sso.conf file, as it
will be overwritten if you run 'engine-setup' again, during an upgrade,
for example. Instead of that try to create your own 99-my.conf file, for
example.
Also, if you want this just for SSH, I'd suggest to use the SSH SOCKS
proxy support instead. For example, I reach all my systems via SSH,
using 'server.example.com <http://server.example.com>' as the SSH
gateway. I start SSH like this:
ssh -D 127.0.0.1:10000 <http://127.0.0.1:10000> server.example.com
<http://server.example.com>
And then I configure my browser to use 127.0.0.1:10000
<http://127.0.0.1:10000> as SOCKS proxy
for *.example.com <http://example.com>;.
+1 to the SOCKS proxy - I use it too. You still need to be able to DNS
resolve on your host - though I believe there is a way to resolve over
SOCKS as well.
Y.
I use Firefox, and it has a "Proxy DNS when using SOCKS 5" option that
you can tick/untick. I am not 100% sure, but I believe that other
browsers just enable it by default when a SOCKS5 proxy is used.
>
> On January 27, 2017 1:10:33 AM GMT+02:00, Alex
<rightkicktech(a)gmail.com <mailto:rightkicktech@gmail.com>>
> wrote:
>
> Thank you Martin.
> I will check that.
>
> On January 26, 2017 9:39:42 PM GMT+02:00, Martin Perina
> <mperina(a)redhat.com <mailto:mperina@redhat.com>> wrote:
>
> Hi,
>
> please take a look at [1], since oVirt 4.0.4 you can defined
> alternate names (or IPs) to access engine.
>
> Regards
>
> Martin Perina
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1325746
<https://bugzilla.redhat.com/show_bug.cgi?id=1325746>
>
>
> On Thu, Jan 26, 2017 at 6:59 PM, rightkicktech.gmail.com
<http://rightkicktech.gmail.com>
> <http://rightkicktech.gmail.com
<http://rightkicktech.gmail.com>> <rightkicktech(a)gmail.com
<mailto:rightkicktech@gmail.com>
> <mailto:rightkicktech@gmail.com
<mailto:rightkicktech@gmail.com>>> wrote:
>
> Hi all,
>
> Is there any way to bypass the FQDN access requirement on
> ovirt 4? On previous versions I was able to access ovirt
> engine using IP. It is impractical to access with FQDN
when
> doing remote port forwarding.
>
> Thanx,
> Alex
> --
> Sent from my Android device with K-9 Mail. Please
excuse my
> brevity.
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org <mailto:Users@ovirt.org>
<mailto:Users@ovirt.org <mailto:Users@ovirt.org>>
> http://lists.ovirt.org/mailman/listinfo/users
<http://lists.ovirt.org/mailman/listinfo/users>
> <http://lists.ovirt.org/mailman/listinfo/users
<http://lists.ovirt.org/mailman/listinfo/users>>
>
>
>
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org <mailto:Users@ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users
<http://lists.ovirt.org/mailman/listinfo/users>
>
_______________________________________________
Users mailing list
Users(a)ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
<http://lists.ovirt.org/mailman/listinfo/users>