• Resolved Deepak

    (@d88pak)


    Hi Team,

    While I was using W3TC on the local development machine, tried to serve the “Host attachments” from the Amazon S3 bucket. First time images refused to load. However, when I checked “Set cookie domain to “mylocal.subdoman.com” it worked fine (self-signed certificate is trusted for local development).

    Now I am beginning to set up an actual site that has Letsencrypt issued certificate, I can’t load the image no matter what I do.

    When selecting default option to use “<my_bucket_name>.s3.amazonaws.com”, my chrome says invalid certificate “NET::ERR_CERT_COMMON_NAME_INVALID”. When I checked, the certificate issued was “*.s3.amazonaws.com” (not my domain).

    However, when I try to use the actual path like “s3.ap-south-1.amazonaws.com/<my_bucket_name>/” (on CNAME field), it works

    So my question is why can’t I use the default subdomain option? It looks much cleaner. I named my bucket “cdn.mydomain.com”

    Any suggestion?

    Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @d88pak

    Thank you for your inquiry and I am happy to assist you with this.
    Please make sure that all the settings in the AWS console are set up correctly. You can check out the instructions on how to setup AWS CDN with W3 Total Cache in our FAQ.
    I hope this helps!
    Thanks!

    Thread Starter Deepak

    (@d88pak)

    Hi,

    I think I have set up the CDN part correctly. The only issue is AWS is also issuing a certificate besides my application, which is causing an invalid certificate anomaly.

    Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Set cookie domain to “example.com” Seems not Working’ is closed to new replies.