S3 Web Console "Networking Error"

Hello,

Greetings of the day,

I suspect the issue is with the browser hence I would kindly recommend you to try the following to resolve the issue.

1. Try accessing the AWS s3 console again after clearing your browser's cache.
2. Also try using incognito mode to access s3 console.
3. Use different network/machine. Please check if you are behind any firewalls or proxy server's.
4. Try accessing s3 console from different browser.

Furthermore,
Another possible reason for this could be due to a high number of versions and delete markers present in the bucket being browsed, the list bucket operation using the console could result in some errors ( example : unexpected error ). I have also seen this happening with buckets having high number of objects/versions/delete markers.

S3 LIST operations for a large amount of objects that have a large amount of versions and delete markers could take time to return as the list operations include past versions of objects and the delete markers for the deleted versions. If the non-current versions are not required for production purposes, it could help with list performance to remove unnecessary versions:

-> Deleting Object Versions - https://docs.aws.amazon.com/AmazonS3/latest/dev/DeletingObjectVersions.html
-> Object Lifecycle Management - https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html

Removing unwanted versions could result in improved performance when listing via console.

Thank you!!

I ran into this issue when I had an 'Allow CORS' plugin enabled in my browser. Check that or other plugins.

Hi,

Did you find the cause of this problem and how to resolve it?
I'd appreciate anything you're able to share.

Cheers,
Soroush

Hello,

I also met this kind of issue and I can not connect to S3 now.

I`d really appreciate if you find the solution.
Thanks.

Hello,

I also met this kind of issue and I can not connect to S3 now.

I`d really appreciate if you find the solution.
Thanks.

This just happened to me as well. Clearing the browser cookies resolved the issue.