Depends on the user installing the same(mostly personal laptops, either MacOS, Windows or Linux) or could be managed kubernetes cluster or containers or bare metals.
Issue
harness.io failed to fetch : 504 gateway time-out
Resolution
This usually happens when the application is still in the startup phase, and the user tries to sign-up.
Diagnostic Step
During the installation of Harness-cd-community using helm, it takes time for the pods to start running, so if you follow the steps mentioned here to start using Harness-CD, which includes a wait command which should be used. kubectl wait --namespace harness --timeout 900s --selector app=proxy --for condition=Ready pods
Once the wait command completes your Harness installation is ready.