3 weeks ago
This is the primary reason i would cancel my gorpo plus account as well.
Pointless to pay for a service that takes so long to uplaod and use.
Gopro must do something about this otherwise they are greatly losing reputation amoung their loyal customers.
https://gopro-media-uploads.s3.us-west-2.amazonaws.com seems to be hardocded in the
GoProShareService, which is very unfortunate.
This resolves (CNAME) to s3-r-w.us-west-2.amazonaws.com. This means, according to AWS Regions and Endpoints , that european users have to talk with a server in US West (Oregon).
I've tried to trick the DNS-Resolution to a european server. This works, but i see TLS-Errors in the GoProShareService log. So no upload is happening.
How are you uploading your media to the cloud - is it via auto upload, through Quik for desktop, or manually through gopro.com?
Also, which file types are you uploading - photos? videos? a combination?
Check if there are chaptered files among the files as these can only be uploaded by auto upload or Quik.
Also, see if there is anything beyond 450MB as they might be taking longer than usual to be uploaded manually than through Quik.
Let us know what you find out. You observation will help a lot in isolating the source of the trouble. We hope to hear back from you.
Sunday - last edited Sunday
Please make this test
and tell me the percentage improvment.
You can't do anything to make it better . . it's a matter for gopro and their Amazon S3 Cloud design (which is terrible)