MMM-MealieMenu Fetch Error

WallysWellies

@zanix The mealie module has been in an error since yesterday and I wonder if you might be able to help me troubleshoot?

I have run the following command:

tail -100 .pm2/logs/mm-error.log

And at the end I see the following:

[2024-05-31 16:47:51.577] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-05-31 17:47:51.580] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-05-31 18:47:51.581] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-05-31 19:47:51.590] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-05-31 20:47:51.571] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-05-31 21:47:51.575] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-05-31 22:47:51.582] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-05-31 23:47:51.574] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-06-01 00:47:51.604] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-06-01 01:47:51.601] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-06-01 02:47:51.576] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-06-01 03:47:51.576] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-06-01 04:47:51.577] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-06-01 05:47:51.575] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-06-01 06:47:51.580] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-06-01 07:47:51.571] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-06-01 08:47:51.577] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-06-01 09:47:51.572] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-06-01 10:47:51.577] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-06-01 11:47:51.576] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-06-01 12:47:51.568] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"
[2024-06-01 13:47:51.580] [ERROR] [MMM-MealieMenu] Fetch error: "Unauthorized"

I have confirmed that the correct username / password is in my config.js file (and it has worked previously) - I can login via my laptop using http://raspberrypi:9925/ using these credentials.

The config.js file is using the following line for the connection:

host: "http://localhost:9925"

I use browser / terminal / SSH etc. to access the Pi but if necessary I can connect a keyboard / mouse if that would aid in narrowing down the issue.

Do you have any thoughts? I can probably just restart the mirror service but I haven’t yet in case that deletes any valuable information. Any advice would be appreciated.

WallysWellies

I have found the part of Mealie that allows creation of an API key so I could switch to that method for authentication.
I also see I am a couple of versions behind the Mealie master branch (I use version 1.5.1 - current version is 1.7.0). That looks drastic but it’s only 2 releases behind.

I don’t think either of these things are causing my issue necessarily but it’s a couple of things I can change soon.

sdetweil

@WallysWellies are you using watchtower to keep. your containers up to date?

WallysWellies

@sdetweil Mealie is the first time I’ve used docker so it’s totally manual. I’ve never tried to update it - it was setup within the last couple of months.

I was planning to do the update based on the Mealie docs but I could look into watchtower.

sdetweil

@WallysWellies i have watchtower maintain all my docker stacks

WallysWellies

@sdetweil I’ll look into it, thanks.

zanix

I normally use an API key but I just tried my username/password and it worked. I’m on Mealie 1.7.0.
Go ahead and restart MM and see if that works.

Are you on the latest MMM-MealieMenu (1.5.0)? I added an additional log when the auth token fetch fails.

zanix

I just realized this error occurs when the meal plan is fetched. I wonder if the auth token is expiring.

WallysWellies

@zanix Restarting the MM service fixed the issue with no additional steps so it may well be an expiring token or something.

I have updated the Mealie container so I am now on v1.7.0 and switched to using the API key for auth. I have also checked and I am using the current version of your module, v1.5.0.

I’ll report back if anything interesting happens. Thanks again for your advice.

zanix

@WallysWellies Thanks!
I think the token does expire. I just checked the token on my instance and it expires 1 month from now.
I will work on fixing that soon.

zanix

@WallysWellies I just updated the module to account for token expiration.
It took me a bit to test since I needed to let the token expire to make sure it worked.

WallysWellies

@zanix that’s dedication, thanks!

I see the update notification so I’ll get it updated tonight. Cheers.

WallysWellies

@zanix Hi Zanix. Just updated the module and all meal entries now seem to use the default image. I updated the docker image in case that was the problem but they’re all still showing the default orange image.

Possible bug introduced in the latest release?

WallysWellies

@zanix Sorry, ignore me - it seems to only be using default images on my laptop. On the actual screen it’s showing the images. Maybe it’s something to do with resolution or something. Apologies.

zanix

@WallysWellies I opened MM on my desktop (MM runs on a Pi5) and I can see the meal images.
The default image only displays when the meal image cannot load. Maybe the URL of the images isn’t accessible on your laptop?

WallysWellies

@zanix You are correct. Looking in the console it’s trying to load from localhost. I’m not greatly fussed but one day I might look into where I can fix that.

Cheers!

zanix

@WallysWellies Are you running MM and Mealie on the same computer? And do you have the MMM-Mealie URL set as localhost?
If so, try changing the MMM-Mealie URL to the IP address of the computer it’s running on.