IsardVDI - follow up - we have a winner.
Credit to Josep - and many thanks for all the help --
Josep Maria Viñolas Auquer
@vinolas · 7 hours ago
Owner
Hi,
I remembered it could be due to a bad initial certificates generation. Can you try this:
(Start everything up -- ensure the whole isardVDI system is up -)
run the following command -
docker exec -ti isard-engine python3 update_certs.py
This will show -
Seems a self signed certificate
Domain: localdomain
Certificates updated in database
And boom - this fixed my issue. -- Watch live at / admv0rl0n