Dario_P
November 23, 2018, 4:24pm
1
Hello.
We have a dataset with 3 rows, one of the columns is external image type.
One of them is shown correctly (.jpeg extention) and the others two not.https://URL/library/download/3911/image?preview=1
the others as I try to see the url, show this
Any Idea?
Thank you in advance.
I understand that there is a component that can’t access the site.https://www.maimonides.edu/uploads/images/181016043322_8va-jornada-de-actualizac.jpeg
Rejected Request 1 to https://www.maimonides.edu/uploads/images/181016043322_8va-jornada-de-actualizac.jpeg because cURL error 6: Could not resolve host: www.maimonides.edu (see http://curl.haxx.se/libcurl/c/libcurl-errors.html )
Dario_P
December 19, 2018, 3:07pm
3
After updating to 1.8.11 it seems that logging improved and then realized that error was related to certificates.
The images for 1.8.11 have support for this built in.
You’ll need to upgrade to 1.8.11, and add the following to the volumes line of your cms-web container in the docker-compose file before bringing the containers up:
- "./shared/cms/ca-certs:/var/www/cms/ca-certs"
So the complete section reads:
cms-web:
image: xibosignage/xibo-cms:release-1.8.11
volumes:
- "./shared/cms/custom:/var/www/cms/custom"
- "./shared/backup:/var/www/backup"
- "./shared/cms/web/theme/…
and did this
First obtain a copy of the ca cert for your corporate proxy that is spoofing your SSL certificates.
Once you have it, you’ll need to add it in to the container, by running the following substituting the name of your cms-web container:
docker cp mycert.pem xibo_cms-web_1:/usr/local/share/ca-certificates
docker exec -ti xibo_cms-web_1 update-ca-certificates
docker restart xibo_cms-web_1
That should add your certificate, and the CMS should be able to connect to the Darksky servers.
If not, plea…
Solved by Dan!
