What does this show
engine-config -g WebSocketProxy
should be <fqdn>:6100
if not try setting it with
engine-config -s WebSocketProxy=<fqdn>:6100
then restarting the engine.
Regards,
Paul S.
________________________________
From: Gianluca Cecchi <[email protected]>
Sent: 05 February 2020 13:57
To: Nicolás <[email protected]>
Cc: users <[email protected]>
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 <[email protected]<mailto:[email protected]>>
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://<fqdn>:6100.
A snapshot is included in this mail.
I don't know why is it trying to connect to this address, seems like a
missed step on the upgrade process? (we upgraded 4.1 -> 4.2 -> 4.3).
How can I fix this problem?
Thanks!
To get current value stored:
engine-config -g WebSocketProxy
If wrong, to change it:
engine-config -s WebSocketProxy=your_desidred_fqdn:6100
systemctl restart ovirt-engine
HIH,
Gianluca
To view the terms under which this email is distributed, please go to:-
http://leedsbeckett.ac.uk/disclaimer/email/
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/Z7YH6LVLGUDDD2FFICFPALDF7IUNZTNE/
