You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you try to add a recipe with an image that is too large for Grocy to support (such as https://gabriellaquille.com/salmon-avocado-crispy-rice-paper-rolls/) then the recipe is added to Grocy, but without an image. An error is displayed in Recipe Buddy which implies that the whole thing has failed.
The text was updated successfully, but these errors were encountered:
This is not actually an issue with recipe buddy.
I had to update my PHP settings in grocy.env AND my reverse proxy to handle larger file sizes.
Recipe buddy is really not able to control much in this case. Error internally is a 413 Response too Large on the grocy side, due to server config. The API from grocy returns 500 Error which doesn't tell us a terribly lot about the problem.
Error handling could be improved dramatically, and for that reason alone I would keep the bug open, but change it to an improvement..
On to the config that fixed it...
nginx
server {
listen 80;
server_name grocy.local;
client_max_body_size 50M;
}
If you try to add a recipe with an image that is too large for Grocy to support (such as https://gabriellaquille.com/salmon-avocado-crispy-rice-paper-rolls/) then the recipe is added to Grocy, but without an image. An error is displayed in Recipe Buddy which implies that the whole thing has failed.
The text was updated successfully, but these errors were encountered: