linuxserver.io Posted September 26, 2020 Share Posted September 26, 2020 (edited) As off June 5, 2022 this image has been deprecated, read the notice here https://info.linuxserver.io/issues/2022-06-05-chevereto/ Application Name: Chevereto Application Site: https://github.com/Chevereto/Chevereto-Free Docker Hub: https://hub.docker.com/r/linuxserver/chevereto/ Github: https://github.com/linuxserver/docker-chevereto Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, rather use the linuxserver.io forum for support. Edited June 13, 2022 by linuxserver.io Quote Link to comment
hernandito Posted October 1, 2020 Share Posted October 1, 2020 Hi Team, Thanks for this Docker. I gave it a try and found a potential show-stopper issue. I tried dragging a .jpeg file that is about 8MB. On the UI I get a message that says "File too big". The UI does say: "JPG PNG BMP GIF 2 MB" This maximum file size is way too small for any modern recent camera file. I googled a bit and found this posting. It basically says that the hosting service is the one limiting the file size to 2MB. I figured since I am the host, there should be a setting somewhere to change this. I found this, which states: Quote In our last article, we’ve explained about limiting user file upload size in Apache. In this article, we will explain how to limit user file upload size in Nginx. Restricting file upload size is useful to prevent some types of denial-of-service (DOS) attacks and many other related issues. By default, Nginx has a limit of 1MB on file uploads. To set file upload size, you can use the client_max_body_size directive, which is part of Nginx’s ngx_http_core_module module. This directive can be set in the http, server or location context. It sets the maximum allowed size of the client request body, specified in the “Content-Length” request header field. Here’s an example of increasing the limit to 100MB in /etc/nginx/nginx.conf file. Set in http block which affects all server blocks (virtual hosts). http { ... client_max_body_size 100M; } Set in server block, which affects a particular site/app. server { ... client_max_body_size 100M; } So I went into /appdata/chevereto/nginx/nginx.conf and in the http: block changed: "client_max_body_size 100M;" It was originally set to 0 (a bad sign). I restarted the docker and still had the same issue. 😦 Is there a way to increase this minimum? Did I do this in the wrong place? There is no "server" block in the .conf file. Thanks again. H. Quote Link to comment
JonathanM Posted October 1, 2020 Share Posted October 1, 2020 13 minutes ago, hernandito said: So I went into /appdata/chevereto/nginx/nginx.conf and in the http: block changed: "client_max_body_size 100M;" It was originally set to 0 (a bad sign). 0 is unlimited, or more precisely, not checked. http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size Quote Link to comment
hernandito Posted October 1, 2020 Share Posted October 1, 2020 19 minutes ago, jonathanm said: 0 is unlimited, or more precisely, not checked. http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size I figured that when I saw the zero value. So is there a way to change this within the Docker, or is it a hard limit beyond our control? Quote Link to comment
JonathanM Posted October 1, 2020 Share Posted October 1, 2020 Probably not related to container implementation, but I could be wrong. Try here. https://chevereto.com/community/ Quote Link to comment
hernandito Posted October 1, 2020 Share Posted October 1, 2020 7 hours ago, jonathanm said: Probably not related to container implementation, but I could be wrong. Try here. https://chevereto.com/community/ Thanks.... that is where I saw the note about client_max_body_size potential solution... They also note other PHP configuration items. Quote Link to comment
ClintWilkenson Posted December 25, 2020 Share Posted December 25, 2020 It was easy enough to get the container up and running but I get this error when I try to use the upgrade to premium feature in the webUI Quote Link to comment
ClintWilkenson Posted December 25, 2020 Share Posted December 25, 2020 On 10/1/2020 at 1:37 PM, hernandito said: Thanks.... that is where I saw the note about client_max_body_size potential solution... They also note other PHP configuration items. @hernandito you want to check the php-local.ini file located at /chevereto/php/ and make sure its got the sizes you want (restart the container for changes to take effect) After that, go into chevereto's webUI settings under image upload and change the limits there as well. Quote Link to comment
ubermetroid Posted December 26, 2020 Share Posted December 26, 2020 5 hours ago, ClintWilkenson said: It was easy enough to get the container up and running but I get this error when I try to use the upgrade to premium feature in the webUI Dont use the linuxserver build. it has a glitch. use the nmtan/chevereto build. That will allow the upgrade. Quote Link to comment
rdlombardi Posted December 28, 2020 Share Posted December 28, 2020 Hi there!, Is there any step by step turotial about how to get Chevereto up and running on unRIAD? 1 Quote Link to comment
PeterW Posted February 9, 2021 Share Posted February 9, 2021 I have Chevereto running well in docker/unraid, however, It appears to be storing my images within the docker itself. Is there a way to map an external (to the docker image) folder for the image store? How would I go about doing this? Thankyou. Quote Link to comment
saarg Posted February 9, 2021 Share Posted February 9, 2021 3 hours ago, PeterW said: I have Chevereto running well in docker/unraid, however, It appears to be storing my images within the docker itself. Is there a way to map an external (to the docker image) folder for the image store? How would I go about doing this? Thankyou. Why do you think it saves the images inside the container? Quote Link to comment
PeterW Posted February 11, 2021 Share Posted February 11, 2021 On 2/9/2021 at 11:58 PM, saarg said: Why do you think it saves the images inside the container? saarg, #1: The only change I made was to install container and upload a few GB of photos for test, and suddenly my docker.img is full. #2: The container template also doesn't appear to have any mappings for any array folders. Quote Link to comment
fonex Posted February 19, 2021 Share Posted February 19, 2021 nice this bullcrap just deleted all my images i've gathered for 15 years. I imported images and for some reason this shit corrupted itself and few moments later i find that all my images are gone. remove this shit....... Quote Link to comment
saarg Posted February 19, 2021 Share Posted February 19, 2021 1 hour ago, fonex said: nice this bullcrap just deleted all my images i've gathered for 15 years. I imported images and for some reason this shit corrupted itself and few moments later i find that all my images are gone. remove this shit....... Not that this will help much, but might be good to back up important files. Hard to figure anything out with the info you have supplied. Quote Link to comment
Hydranmenace Posted March 6, 2021 Share Posted March 6, 2021 I am trying to set this up. I installed the MySQL docker image. MySQL says it's running. I went to the webui for cheverito to enter my info there and get the message "Can't connect to the target database. The server replied with this: SQLSTATE[HY000] [2054] The server requested authentication method unknown to the client Please fix your MySQL info." I don't know what info I need to fix? I installed the MySQL Workbench docker and I seem to be able to connect with that... So I don't know what I am doing wrong? Quote Link to comment
matda59 Posted May 25, 2021 Share Posted May 25, 2021 (edited) Running Chevereto on UNRAID utilising MariaDB. Any time i do a container update it looses my image mapping see below. I've restored mariaDB and cheverto from backup, looked at the config file cannot get the images\photos to show up. Edited May 26, 2021 by matda59 Quote Link to comment
rshuler Posted July 11, 2021 Share Posted July 11, 2021 (edited) After a conainer update, the Chevereto only has links, but the links do not point to images. I see others have experience a similar issue. Any work arounds for this failure? Thanks, Robert Edited July 12, 2021 by rshuler Quote Link to comment
Spiritreader Posted July 19, 2021 Share Posted July 19, 2021 (edited) Using version-1.4.0 results in the following error message: Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 7.4.0". Is that an issue on my end or is the used php version outdated? What do I need to do? UPDATE: fixed in latest container version Edited August 1, 2021 by Spiritreader Quote Link to comment
Rick_Sanchez Posted November 21, 2021 Share Posted November 21, 2021 Can anyone muster up a step-by-step install for this? And then maybe pin to the thread? Quote Link to comment
dompe Posted February 14, 2022 Share Posted February 14, 2022 Hello, I installed this app, I've changed the logo, favicon and background, but when I restart the docker, everything goes into default. It's normal or I miss something ? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.