<p>I'm trying to setup ArgoCD to automatically deploy Kubernetes manifests from a remote repository.</p>
<p>Argocd is installed on my K3s cluster. The CLI is working... kind of. I can't do <code>argocd app create name</code> (with or without additional parameters) or it stalls in the terminal indefinitely... I'm not exactly sure what the word is for this, but the terminal never prompts me for another command. Note that if I do <code>argo app create --help</code> it does not stall-- it displays the help message.</p>
<p>Because of this, I want to use the UI to add an app to argo. This requires port forwarding to port 8080. I am trying to do this with the following command:</p>
<p><code>kubectl port-forward svc/argocd-server -n argocd 8080:443</code></p>
<p>But it prints</p>
<pre><code>Forwarding from 127.0.0.1:8080 -&gt; 8080
Forwarding from [::1]:8080 -&gt; 8080

</code></pre>
<p>With the cursor on the third line... This command <em>also</em> stalls indefinitely! I've waited for quite a while and nothing happens. Nothing else is running on port 8080 on any of the nodes.</p>
<p>Someone please give some guidance on how to proceed here? I am brand new to ArgoCD and Kubernetes.</p>

Antonio Leonti
<p>This was a silly misunderstanding on my part of how the <code>argocd port-forward</code> command works. When you run <code>kubectl port-forward svc/argocd-server -n argocd 8080:443</code>, it sets up a proxy so that you can communicate with the argocd server through port 8080. When that program ends, the proxy closes-- so when you press <code>control+c</code>, thinking the command is &quot;stuck&quot;, you are actually just closing the proxy you set up.</p>
<p>The solution is to run <code>kubectl port-forward svc/argocd-server -n argocd 8080:443</code>, open a new shell, and use the new shell to login and interact with ArgoCD.</p>
