Mealie widget still not working on latest release of Mealie (nightly build)

[lennon101]

Description

I want to reopen the (now closed) issue outline in #1924

I'm currently on the latest release of Mealie and the latest release of HomePage and I'm not having any luck with the Mealie widget. The config I have is:

And the result is:

Steps to reproduce

Create an api key via an admin user on the mealie page using
Click on Settings
Create an api key under "API-Tokens"
Insert API-Key on the homepage-config

homepage version

v0.8.13 (986a181, May 6, 2024)

Installation method

Docker

Configuration

- Mealie:
        href: http://<private ip>:9925
        description: A self-hosted recipe manager and meal planner
        icon: mealie.png
        widget:
          type: mealie
          url: http://<private ip>:9925
          key: <mealie api token>

### Container Logs

_No response_

### Browser Logs

_No response_

### Troubleshooting

I've tried recreating an API token and refreshing my browswer cache.

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

To assist you with the issue you're experiencing with the Mealie widget on Homepage, we need to go through a few troubleshooting steps:

1. Verify API Key: Ensure that the API key you generated is from an admin account on Mealie, as non-admin tokens may not have the necessary permissions.

2. Check URL Format: According to the documentation, the URL in the widget configuration should not end with a slash or other API path. Make sure that the URL is formatted correctly as per the instructions on https://gethomepage.dev/latest/configs/service-widgets/.

3. Check Network Accessibility: Verify that the Homepage installation can connect to the Mealie service. You can do this by pinging the Mealie server from the Homepage container:

   docker exec homepage ping <private ip>
   

   If the ping fails, you may need to adjust your Docker network settings or check for firewall issues.

4. Check for API Endpoint: Ensure that the Mealie version you are using has the necessary API endpoints. You can check this by visiting http://<mealie-ip:mealie-port>/docs and looking for the relevant endpoints.

5. Review Logs: Since you have not provided container or browser logs, it would be helpful to check these for any error messages. For container logs, you can use:

   docker logs homepage
   

   For browser logs, you can check the console in your web browser's developer tools.

6. Debugging: If the above steps do not resolve the issue, consider setting the LOG_LEVEL environment variable to debug for more detailed logs.

7. Review Documentation: Make sure to review the documentation for both Mealie and Homepage to ensure that all configuration steps have been followed correctly.

If you have gone through these steps and the issue persists, please provide any error messages or logs that you have, as they will be crucial in diagnosing the problem. Additionally, you can reach out for support on the #ai-support channel on Discord or open a GitHub discussion for further assistance.

This comment was generated by Glime.

[shamoon]

Better than a screenshot is the actual output, would help the bot see the "ETIMEDOUT" part, which means this is almost certainly a networking issue and not the possibility that the mealie widget has been broken for the last ~10 months =)

As with almost 99% of these, starting with the troubleshooting guide is never a bad idea: https://gethomepage.dev/latest/more/troubleshooting/

[shamoon]

Start with the 3 steps here: https://gethomepage.dev/latest/more/troubleshooting/#service-widget-errors

Also you can chat back-and-forth with the ai bot on our docs site, which can be pretty helpful along the way

[lennon101]

ok thanks, I'll give the ai bot a go. In the meantime, here's what I have so far:

• I definitely do not have a trailing / in the widget url. It is just the <local ip> and port number
• both mealy and homepage are mounted on the same machine in seperate docker containers but both are accessed at <local ip>.
• I can ping the <local ip> from the homepage container (makes sense because it's the same ip)

<lennon>@thinkcentre:~$ sudo docker exec homepage ping <private ip>
[sudo] password for <lennon>:
PING <private ip> (<private ip>): 56 data bytes
64 bytes from <private ip>: seq=0 ttl=64 time=0.101 ms
64 bytes from <private ip>: seq=1 ttl=64 time=0.177 ms
64 bytes from <private ip>: seq=2 ttl=64 time=0.162 ms
64 bytes from <private ip>: seq=3 ttl=64 time=0.162 ms
^C

• the curl inside the container fails:

<lennon>@thinkcentre:~/docker/homepage/config$ sudo docker exec homepage curl -X 'GET'   'http://<private ip>:9925/api/groups/statistics'   -H 'accept: appli                                                                             cation/json'   -H 'Authorization: Bearer <mealie api token>'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:01:18 --:--:--     0
curl: (28) Failed to connect to <private ip> port 9925 after 134274 ms: Couldn't connect to server

• I can do the curl command outside of the container (on the host) and the api works

<lennon>@thinkcentre:~$ curl -X 'GET' \
  'http://<private ip>:9925/api/groups/statistics' \
  -H 'accept: application/json' \
  -H 'Authorization: Bearer <mealie api token>'
{"totalRecipes":46,"totalUsers":2,"totalCategories":5,"totalTags":2,"totalTools":0}lennon@thinkcentre:~/docker/homepage/config$

<lennon>@thinkcentre:~$

[shamoon]

The guide explains how to install curl inside the container. apk add curl

[lennon101]

Sorry, I think you misunderstood when I said "the curl command fails inside the container", I installed curl, but, as you can see, it fails with a timeout. Where do I go from here?

curl: (28) Failed to connect to <private ip> port 9925 after 134274 ms: Couldn't connect to server

[shamoon]

Ah yea I did. Ok that’s exactly why we recommend this. So it’s probably a docker networking issue, which can be hard to solve with one recommendation. A couple things:

• if ping works to the IP perhaps check the port. But remember ping just tells you there’s something there, it could be the wrong server/container or whatever (see below)
• in general docker supports using container names instead of IP, and it’s often better and avoids eg an IP changing (unless you’re forcing a static IP)
• Make sure they share a docker network
• sometimes just taking down the entire compose (or docker stack) and removing the networks and re-creating them solves this

but yea at this point it’s not going to be reall a homepage thing so googling in general might be helpful

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.