Amazon S3 Known Issues

Rules for Bucket Naming

Amazon S3 bucket path should not have dots for the name of the bucket.

Solution

Bucket names must be unique across all existing bucket names in Amazon S3.

• The bucket's name must comply with DNS naming conventions.
• The bucket's name must be at least 3 but less than 64 characters long.
• The bucket's name must not contain uppercase characters or underscores.
• The bucket's name must start with a lowercase letter or number.
• The bucket's name must be a series of one or more labels. Adjacent labels are separated by a single period (.). A bucket's name can contain lowercase letters, numbers and hyphens. Each label must start and end with a lowercase letter or a number.
• The bucket's name must not be formatted as an IP address. (Example: 192.168.5.4)
• If you're using virtual hosted-style buckets with a Secure Sockets Layer (SSL), the SSL wildcard certificate will only match buckets that do not contain any period. To work around this, please use HTTP or write your certificate verification logic. We would like to recommend that you do not use the period (.) in the bucket's name while using virtual hosted-style buckets.

Cannot Display Avatar

EasySocial failed to display the avatar because Amazon's library isn't downloading the avatar from Amazon S3.

Solution

This issue is related to the allow_url_fopen PHP directive. It is most probable this directive is not enabled on your server. Therefore, please enable this to fetch images from the Amazon S3.

Cannot Change Existing Avatar

When users try to change their avatar (browse existing avatar image) on the profile page, the ajax response for the request shows 504 Gateway Time-out. One of the possible reasons this issue occurs is that the request hits a timeout limit.

Proposed Solution

If you're using a Plesk server and FastCGI, then you might try to increase the timeout limit from the following directive value:

proxy_connect_timeout 180s;
proxy_send_timeout 180s;
proxy_read_timeout 180s;
fastcgi_send_timeout 180s;
fastcgi_read_timeout 180s;

Cannot Upload to Amazon S3

One of the possible reasons this issue occurs is due to not having the correct permission to upload objects to S3. You'll need to see the error message generated in the S3 logs such as "Access Denied".

Solution

Please check and make sure that the following accesses are disabled/off in your S3 account and bucket.