Quick workaround: try changing https and port 8443 to http and port 8080, and see if that works. If it does, it could be a proxy in between, or it could be a missing SSL certificate preventing HTTPS communications from being established.
Correct fix: verify if there is any proxy information or SSL certificates that were in your old installation that might not be added to the new installation yet. Correct missing info and retry.
The certificate would be provided by your company’s IT or network team.
Use http instead of https (unencrypted communication).
For KNIME update sites, this is found under File > Preferences > Install/Update > Available Software Sites.
Possibly change the proxy configuration you’re using (File > Preferences > General > Network Connections).
Should the proxy certificate be preconfigured in Windows by your IT, you can use the Windows trust store. To do so, add these two lines at the end of the knime.ini within the KNIME installation folder (while KNIME isn’t running):