Title: Uncaught Exceptions
Last modified: August 22, 2016

---

# Uncaught Exceptions

 *  [Wes Turner](https://wordpress.org/support/users/wesswei/)
 * (@wesswei)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/uncaught-exceptions/)
 * `[Tue Nov 18 13:43:52 2014] [error] [client 108.176.17.234] PHP Fatal error: 
   Uncaught Aws\\S3\\Exception\\PermanentRedirectException: AWS Error Code: PermanentRedirect,
   Status Code: 301, AWS Request ID: 1902569AD752F8BB, AWS Error Type: client, AWS
   Error Message: The bucket you are attempting to access must be addressed using
   the specified endpoint. Please send all future requests to this endpoint: "s3.
   amazonaws.com"., User-Agent: aws-sdk-php2/2.6.15 Guzzle/3.9.2 curl/7.22.0 PHP/
   5.3.10-1ubuntu3.15 MUP\n thrown in /var/www/server.local/wp-content/plugins/tcs3/
   aws/Aws/Common/Exception/NamespaceExceptionFactory.php on line 91, referer: http://
   server.local/wp-admin/upload.php`
 * The ability to test if the configuration is setup properly would help setup. 
   I was using “US Standard” in S3, but since there was no option for this, I had
   to try them all. Amazon say’s the use the s3.amazonaws.com endpoint for the US
   Standard region, which resolves to either Virginia or West Coast. The test could
   upload a simple log file so that you can clearly see the path and file from S3
   management in AWS console.
 * When all files are synced, there does not appear to be a way to un-sync or re-
   sync all. Using the sync button in settings fails due to a javascript issue: 
   ids is null in the for loop. Use case would be if these are synced to the wrong
   path or the bucket gets emptied. Only recourse is to delete the meta_key “is_on_s3.”
   Similar to mark all as synced, there should be a mark all (or single if on the
   media page) as unsynced.
 * Cancel sync should be an option for bulk sync since you may have realized as 
   I did that your setting are incorrect.
 * Your action hovers in media for “send this to s3” is missing an href tag and 
   therefore lacks the cursor: pointer. At least a `javascript:void(0)` should be
   thrown in the href tag.
 * [https://wordpress.org/plugins/tcs3/](https://wordpress.org/plugins/tcs3/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Thread Starter [Wes Turner](https://wordpress.org/support/users/wesswei/)
 * (@wesswei)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/uncaught-exceptions/#post-5493403)
 * Also, I don’t see the original file being uploaded to S3, only the various sizes
   are getting there.
 *  Thread Starter [Wes Turner](https://wordpress.org/support/users/wesswei/)
 * (@wesswei)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/uncaught-exceptions/#post-5493412)
 * Also, do images get synced when a new one is added; that is, is there a hook 
   for uploads that allows an object to be synced afterwards?
 * Possibly a real or wp cron job to periodically check for uploads that do not 
   have the meta “is_on_s3” property and upload them automatically?
 *  Thread Starter [Wes Turner](https://wordpress.org/support/users/wesswei/)
 * (@wesswei)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/uncaught-exceptions/#post-5493446)
 * For the above comment re: not seeing the original file uploaded to S3. I still
   don’t see it on AWS console, but after fixing the rewrite rule, I no longer have
   404s.
 * I was using:
    #RewriteRule ^tcS3_media/(.*)$ [http://d1vt6iw2a1rnfl.cloudfront.net/media/$1](http://d1vt6iw2a1rnfl.cloudfront.net/media/$1)[
   R=301,L] RewriteRule ^tcS3_media/(.*)$ /index.php?file=$1 [R=301,L]
 * Ideally the first rule should work and point directly to the cloudfront, no? 
   I see you’re likely handling the fallbacks that way in the `load_image` method?
   This isn’t working for me as we are using full links (no specific sizes) and 
   those are falling back to the local versions since the originals are not found
   on CDN.
 * In any case, it would be nice to point directly to the CDN to prevent getting
   dings on multiple redirect chains.
 * Instead of the get request, it might be a better way to hook into the request,
   which would detect that the post type is attachment, so you could perform your
   checks there.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Uncaught Exceptions’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/tcs3.svg)
 * [tcS3](https://wordpress.org/plugins/tcs3/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/tcs3/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/tcs3/)
 * [Active Topics](https://wordpress.org/support/plugin/tcs3/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/tcs3/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/tcs3/reviews/)

## Tags

 * [bugs](https://wordpress.org/support/topic-tag/bugs/)
 * [exceptions](https://wordpress.org/support/topic-tag/exceptions/)
 * [Issues](https://wordpress.org/support/topic-tag/issues/)

 * 3 replies
 * 1 participant
 * Last reply from: [Wes Turner](https://wordpress.org/support/users/wesswei/)
 * Last activity: [11 years, 4 months ago](https://wordpress.org/support/topic/uncaught-exceptions/#post-5493446)
 * Status: not resolved