Hi,
In 4.0 you can access oVirt engine only with the same FQDN that was specified during engine-setup. If you have used different FQDN, you may change it using ovirt-engine-rename tool.
Martin Perina
On Sunday, July 3, 2016, Yaniv Dary <ydary@redhat.com> wrote:
>
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
> Tel : +972 (9) 7692306
> 8272306
> Email: ydary@redhat.com
> IRC : ydary
>
> ---------- Forwarded message ----------
> From: COUSIN Kevin <kevin@famillecousin.fr>
> Date: Thu, Jun 30, 2016 at 5:31 PM
> Subject: [ovirt-users] [oVirt 4.0] Is it possible to access oVirt through a reverse proxy
> To: users@ovirt.org
>
>
> Hi list,
>
> I upgraded to oVirt 4.0 and it works fine. However, I used HAProxy to
> access oVirt outside my LAN. It doesn't work anymore since I upgraded
> to 4.0. It seems the oVirt Manager URL is rewritten by the SSO engine.
> eg: ovirt.externaldomain.tld -> ovirtmanager.internaldomain.tld.
>
> Is it possible to disable this behaviour and stay with
> ovirt.externaldomain.tld ?
>
> Regards
>
> --
> COUSIN Kevin <kevin@famillecousin.fr>
>
> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users