Read the statement by Michael Teeuw here.
MMM-MealieMenu Fetch Error
-
- 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.
-
@WallysWellies are you using watchtower to keep. your containers up to date?
-
@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.
-
@WallysWellies i have watchtower maintain all my docker stacks
-
@sdetweil I’ll look into it, thanks.
-
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.
-
I just realized this error occurs when the meal plan is fetched. I wonder if the auth token is expiring.
-
@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.
-
@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. -
@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.
