El 2020-02-05 13:57, Gianluca Cecchi escribió:
On Wed, Feb 5, 2020 at 2:50 PM wrote:
A little bit more info on it. I debugged the requests with Chrome
and
seems that the webservice call is made with https://engine:6100 [1]
(literally), instead of https://:6100.
A snapshot is included in
Cc: users
Subject: [ovirt-users] Re: Websocket-proxy not working after upgrade to 4.3
Caution External Mail: Do not click any links or open any attachments unless
you trust the sender and know that the content is safe.
On Wed, Feb 5, 2020 at 2:50 PM mailto:nico...@devels.es>>
wrote:
A
Hi,
nico...@devels.es writes:
> A little bit more info on it. I debugged the requests with Chrome and
> seems that the webservice call is made with https://engine:6100
> (literally), instead of https://:6100.
>
> A snapshot is included in this mail.
>
> I don't know why is it trying to connect
On Wed, Feb 5, 2020 at 2:50 PM wrote:
> A little bit more info on it. I debugged the requests with Chrome and
> seems that the webservice call is made with https://engine:6100
> (literally), instead of https://:6100.
>
> A snapshot is included in this mail.
>
> I don't know why is it trying to
4 matches
Mail list logo
