Jason John Schwarz

Retested on v2.5.0 and still having the same problem. I seem to be getting no response on this thread at all.

Understood, but given that any way to debug from logs or to capture data to debug?On Jul 1, 2024, at 6:42 PM, Matthias Pfefferle ***@***.***> wrote: @jjschwarz the problem is,...

Ok, how could I change that to test if it is the issue?  I do not see any setting appending that to the URL.On Jul 1, 2024, at 6:53 PM,...

Removing ::1 temporarily from /etc/hosts allows you to bypass the issue, however since Kubernetes controls that file it must be done manually each time you deploy the software.

I have not replicated it in docker, however I found a fix for the issue. If the API line in /data/.ipfs/config is updated to read: "API": ["/ip4/127.0.0.1/tcp/5001","/ip6/::1/tcp/5001"], then the issue...

Disabling IPv6 is not an option in our environment because it would impact other containers which use it.  I am using the patch I suggested for now.On Dec 2, 2023,...

Would you consider patching the API line in /data/.ipfs/config is updated to read: "API": ["/ip4/127.0.0.1/tcp/5001","/ip6/::1/tcp/5001"] to prevent this issue?

This appears to have been fixed in case 894 and my testing shows it works fine now. Thank you

I can help some...you need to terminate the SSL connection with nginx...so try something like this: apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: nginx.ingress.kubernetes.io/force-ssl-redirect: "true" nginx.ingress.kubernetes.io/backend-protocol: "HTTPS" nginx.ingress.kubernetes.io/proxy-buffering: "off" nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"...