Plugin

Archived
Forum
(read-only)

CE Image

ExpressionEngine 1.x, ExpressionEngine 2, ExpressionEngine 3

Back to this add-on's main page
View Other Add-ons From Causing Effect

2 of 2
2
   

There was a problem uploading your file to AWS

Support (Resolved)

dsoneil
# 16
dsoneil

I was having the exact same problem and Assets was reporting the same InvalidAccessKeyId error, but I could still access the files in the bucket. It seemed to be a server caching issue, I’m using Redis. I had to restart apache (apache2ctl graceful) and clear the EE cache and then everything worked. This may not work for everyone, but it might help someone. Cheers

tibitabo
# 17
tibitabo

Hi there,

I just purchased CE_Image and I’m having the same problem - without using Assets.

How did you solve this? I tried everything recommended in this thread, but it didn’t work.

Using CE Image v2.4.5 on a local EE v2.10.1 build running PHP 5.5.23.

PHP WARNINGS:

A PHP Error was encountered
Severity
Notice

Message
Undefined propertystdClass::$body

Filename
libraries/Ce_s3.php

Line Number
1993 
A PHP Error was encountered
Severity
Warning

Message
Cannot modify header information headers already sent by (output started at ../system/codeigniter/system/core/Exceptions.php:170)

Filenamecore/Common.php

Line Number
479 

DEBUG INFO:

Calling Class/MethodCe_img/single
-> Class CalledCe_img
-> Method Calledsingle
***  CE Image debugBase path'WEBROOT'
***  CE Image debugSource image'PATH'Fallback image''
***  CE Image debugThe image 'PATH' is cached.
Calling Extension Class/MethodCe_img_aws_ext/pre_parse
***  CE Image AWS debugThere was a problem uploading your file to AWS
tibitabo
# 18
tibitabo

OK, I was able to solve the warning by switching to PHP 5.4.39, but the AWS issue still occurs. :(

tibitabo
# 19
tibitabo

Any ideas anyone?! I need to get this to work soon. :(

CreateSean
# 20
CreateSean

HI,

I’m having this issue as well. My bucket is all lowercase. EE 2.9.3 CE Image 2.4.5. Images are being successfully uploaded to Amazon via Assets using the same credentials.

I have added the following to my focuslab config set up:

// CE Image AWS 
  
$env_config['ce_image_aws_key''****************';
  
$env_config['ce_image_aws_secret_key''*****************';
  
$env_config['ce_image_bucket''sparkphotography2';
  
$env_config['ce_image_aws_request_headers'= array();
  
$env_config['ce_image_aws_request_headers']['Cache-Control''max-age=' . (30 24 60 60);
  
$env_config['ce_image_aws_request_headers']['Expires'gmdate("D, d M Y H:i:s T"strtotime('+1 month') );
  
$env_config['ce_image_aws_storage_class''STANDARD'

The above config items give me a php error on the front end which disappears if I comment above out:

A PHP Error was encountered

Severity
Notice

Message
Undefined propertystdClass::$body

Filename
libraries/Ce_s3.php

Line Number
1993 


My debug info is:

(0.219819 11.68MB)   ***  CE Image debugBase path'D:/xampp/htdocs/sparks-photos/'
(0.219839 11.68MB)   ***  CE Image debugSource image'http://s3.amazonaws.com/sparksphotography2/Assets/Photographers_Images/Clay_Stang_Commissions/01_01.jpg'Fallback image''
(0.219846 11.68MB)   ***  CE Image debugThe image 'D:/xampp/htdocs/sparks-photos/images/made/images/remote/http_s3.amazonaws.com/sparksphotography2/Assets/Photographers_Images/Clay_Stang_Commissions/01_01_375_500.jpg' is cached.
(
0.221027 11.67MBCalling Extension Class/MethodCe_img_aws_ext/pre_parse
(0.555324 11.93MB)   ***  CE Image AWS debugThere was a problem uploading your file to AWS.
(
0.555471 11.91MB) -> Data Returned 
jjpmann
# 21
jjpmann

Just has similar issue this morning. Did a var_dump of the variables and notice AWS was complaining about the server time being off. Simple update to re-sync server time fixed the issue.

PP
# 22
PP

Sorry for digging out this old thread. I have the same debug error info. I am running EE 2.5.2. Is it even possible to connect to AWS with this old version? I can connect to AWS with the same info usin Transmit.

PP
# 23
PP

How can I get more information about the error than “CE Image - AWS debug: There was a problem uploading your file to AWS.”?

2 of 2
2