I have a crazy problem. I am uploading images to s3 via strapi. The files are in the bucket and I can access them. When showing them in my webpage I see them too.
But when I am in the strapi dashboard, I am just seeing the name of the file, but not the image. When I right click on the image and open it in a new tab its showing my the right one.
Did someone had a similar problem with strapi, s3, heroku?
Related
Today I got this error while displaying the images on site
Your request contains duplicate headers.
but still last week my site was showing images properly. there ware no error
I checked on s3 bucket there is not changes in settings .but still images not showing
enter image description here
I'm beginner of strapi, nodejs headless cms framework.
I've followed quick start guide of official document. I've created gatsby-blog and it works.
After setup, I've created new article with uploaded image, in the middle of article. (Not the image field in the Slug section) In the strapi admin page, I can find my new image in the media library list.
But when I open my strapi client in browser, the image is not shown. The source of image seems to the file path of backend server. I can find the image file on the backend/public/uploads folder. But it returns 404 error.
So, What am I missing of strapi setting? I've searched a lot but I can't find similar issue.
Make sure that the field is public in your Strapi admin dashboard.
Beyond that, it seems like the src tag in your screenshot has a relative url - if you are not hosting the backend on the same path as the frontend, I would suspect you have to prepend the backend base path :-)
Django 1.11.2
Wagtail 1.10.1
Apache2.4
I uploaded an image from my computer via the wagtail dashboard. Wagtail shows the image and I clicked "update".
Then I went back to images. There is no new image but a new card with the name of the new file. There is also a picture symbol with the file name of the picture. If I click this field I get the template to edit the image. But the image is not shown (Bildschirmfoto_2018_03_18_17_23_06.png).
Why is the image not shown?
You need to configure Apache to serve files from /media/images/ (or whatever you've set as MEDIA_ROOT in your settings file). See https://docs.djangoproject.com/en/2.0/howto/deployment/wsgi/modwsgi/#serving-files
In S3, I have an index.html, a CSS file and an images folder with 3 jpg files in it. I cut and pasted the jpgs into the S3 folder. They showed as being there. I set a display policy per the instructions to display to everyone. The page displayed, but the images did not. I get the alt text and the tooltips, but no images. On the page, when I right click the Open Image in New Tab, I get an Access Denied message in XML. The page is: http://s3.amazonaws.com/pittsfordcommunitycenter/index.html
Images display on my development PC. I've tried a lot of things in AWS, including what the documentation suggested. What do I need to change?
This is your index.html URL:
http://s3.amazonaws.com/pittsfordcommunitycenter/index.html
This is your first image URL, which is missing the bucket name:
http://s3.amazonaws.com/images/WheelchairInElevator_w_475.jpg
The image URL should actually be:
http://s3.amazonaws.com/pittsfordcommunitycenter/images/WheelchairInElevator_w_475.jpg
Viewing your page source it looks like, given the location of your index.html file, all your image paths should start with ./images/ instead of ../images/. Since it works on your local machine I'm guessing your local index.html location is different, relative to the image files.
AWS domain links are case sensitive unlike you local machine.
In AWS S3 static Webhosting
../images/WHEELCHAIRINELEVATOR_W_475.JPG is **NOT EQUAL** to
../images/wheelchairinelevator_w_475.jpg
In Bassi Banner Slider, I'm going to upload an image in a slide. The image path has been stored to database, but the image is not uploading to site.
So image is not showing in front end, Only the path is shown.
What's the solution for this ?
Solved....
All the images are coming from the amazon server and i was uploading it to testing server.
On live site, it works well.