<p>Everytime I try accessing my minIO console via the browser with a port-forward, the connection will work briefly with multiple connection messages of:</p>
<pre><code>Handling connection for 9000
Handling connection for 42935
Handling connection for 42935
Handling connection for 42935
Handling connection for 42935
Handling connection for 42935
Handling connection for 42935
...
</code></pre>
<p>Then a moment later, this error message</p>
<p><code>E0128 18:22:01.801739   40952 portforward.go:378] error copying from remote stream to local connection: readfrom tcp6 [::1]:42935-&gt;[::1]:50796: write tcp6 [::1]:42935-&gt;[::1]:50796: write: broken pipe</code></p>
<p>Before it finally spamming with multiple messages of:</p>
<pre><code>E0128 18:22:31.738313   40952 portforward.go:346] error creating error stream for port 42935 -&gt; 42935: Timeout occurred
Handling connection for 42935
E0128 18:22:32.120930   40952 portforward.go:346] error creating error stream for port 42935 -&gt; 42935: write tcp 192.168.0.16:50776-&gt;34.133.9.102:443: write: broken pipe
Handling connection for 42935
E0128 18:22:32.574837   40952 portforward.go:346] error creating error stream for port 42935 -&gt; 42935: write tcp 192.168.0.16:50776-&gt;34.133.9.102:443: write: broken pipe
...
</code></pre>
<p>Here's my deployment file:</p>
<pre><code>apiVersion: apps/v1
kind: Deployment
metadata:
  name: minio-deployment
  namespace: minio-ns
spec:
  replicas: 1
  selector:
    matchLabels:
      app: minio
  template:
    metadata:
      labels:
        app: minio
    spec:
      containers:
        - name: minio
          image: minio/minio
          args:
            - server
            - /data
            - --console-address
            - &quot;:42935&quot;
          volumeMounts:
            - name: minio-pv-storage
              mountPath: /data
      volumes:
        - name: minio-pv-storage
          persistentVolumeClaim:
            claimName: minio-pv-claim
---
apiVersion: v1
kind: Service
metadata:
  name: minio-service
  namespace: minio-ns
spec:
  selector:
    app: minio
  ports:
    - name: minio
      port: 9000
      targetPort: 9000
    - name: minio-console
      port: 42935
      targetPort: 42935
  type: LoadBalancer
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: minio-pv-claim
  namespace: minio-ns
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi

</code></pre>
<p>I changed the minio-service type to LoadBalancer (from ClusterIP) to access the console via the browser along with adding the --console-address flag and exposing the necessary port. This worked in allowing the minIO console to show despite being in a constant loading state. If I try to login, it will just refresh until crashing/timing out</p>

Leo Lad
<p>Resolved. The issue didn't have anything to do with my actual code.</p>
<p><a href="https://github.com/minio/console/issues/2539" rel="nofollow noreferrer">https://github.com/minio/console/issues/2539</a></p>
