Protected Links
ExpressionEngine 2, ExpressionEngine 3, ExpressionEngine 4, ExpressionEngine 5, ExpressionEngine 6
Back to this add-on's main page
View Other Add-ons From Yuri Salimovskiy
Help! New error has popped up…
Support Request
|
Lisa Ellington
|
| Posted: 27 February 2017 12:52 PM |
|
|
|
|
Our client using protected links is having a new error. When the links are clicked this is happening.
Can you help?
|
|
|
|
|
Yuri Salimovskiy
|
| Posted: 27 February 2017 12:57 PM |
# 1
|
|
|
Developer
|
This is AWS/Cloudfront error.
It’s either:
- wrong permission (e.g. file is private)
- wrong link
- misconfiguration in Protected Links
|
|
|
|
|
Yuri Salimovskiy
|
| Posted: 27 February 2017 12:58 PM |
# 2
|
|
|
Developer
|
Looking at the URL, it looks like name of container is repeated twice. If you specify container name in PL settings, make sure you don’t include it with file name.
|
|
|
|
|
Lisa Ellington
|
| Posted: 27 February 2017 01:06 PM |
# 3
|
|
|
|
Thanks for the quick reply, Yuri.
Since you helped me set this up over a year ago, I’m thinking it’s an issue on the cloudfront side.
|
|
|
|
|
Yuri Salimovskiy
|
| Posted: 27 February 2017 01:08 PM |
# 4
|
|
|
Developer
|
If you are sure everything is correct (e.g. file has not moved, permissions not changed etc) you can try regenerating the link
|
|
|
|
|
Lisa Ellington
|
| Posted: 27 February 2017 03:27 PM |
# 5
|
|
|
|
Yuri - We aren’t generating a link. We are not specifying the container name in PL. File permissions are fine and URL hasn’t changed. If I go to the direct AWS S3 link it works perfectly. Here’s the code you helped me write a year ago:
{exp:ending until=”/xxx/” string=”{file}” parse=“inward”}
Returns
| |
