Open Servinjesus1 opened 2 months ago
I'm getting this as well, although I'm running Grocy natively without Docker, as the latest version - 4.2.0. I checked the browser console logs and see over and over that the following two API calls keep getting logged
grocy.getQuantityUnits
grocy.getProducts
and for a more thorough message it looks like this.
TRPCClientError: [ { "code": "invalid_type", "expected": "array", "received": "object", "path": [], "message": "Expected array, received object" } ]
Hopefully that helps track this down!
oh, another clue that i don't know how i missed is that on the settings page it tells me right there, "Not connected to Grocy Unable to connect to Grocy - check your URL and API key"
So what do you know - once I double checked my Recipe Buddy's Docker compose file, I had my GROCY_BASE_URL
set incorrectly. I had the trailing /api/
. Once I removed that, the rest of everything worked just fine!
I am seeing the same error now, I wasn't dwelling on the settings page sufficiently long for the Not connected to Grocy error to pop up. But I can't fix it and I think I have my command (or in this case docker-compose file) configured correctly. Can someone who uses the Grocy docker chime in?
To be specific:
GROCY_API_KEY
is a 50-character key generated on Grocy's API keys settings pageGROCY_BASE_URL
is http://localhost:9283
i.e. the main webpage with the default port suggested by docker-grocyNEXTAUTH_SECRET
is a 44-character code generated by openssl rand -base64 32
and used nowhere else but to be placed here. Mine has two forward slashes, some plusses, and ends with an equal sign, of which I worried maybe were poor characters to have in this secret, but that doesn't seem to be the problem.Have I done something wrong here?
I'm not capable enough to try hosting Grocy natively without docker. Particularly on how to spin up the repo to host it on a local port.
The database is working fine, so at least I know the plugin itself is presumably operating normally.
@Servinjesus1 What worked for me is using the IP of the machine that is hosting it, rather than "localhost". I think in this case, localhost refers to the docker instance, rather than the machine itself.
Does recipe import pull "Grocy stock" from actual Stock or Products tables? I suspect it should pull from the Product table - not what's actually in stock right now. That said, mine is pulling from neither.
I'm getting reasonable log messages stating that the instance is set up.
Simple recipe appears to scrape fine:
but during import nothing is shown to select for product/unit.
Grocy:
lscr.io/linuxserver/grocy:latest
61522391c2212c794fc8336294d6d3227fb0d7febb3eb7b597466f6931080a44
Recipe-Buddy:ghcr.io/georgegebbett/recipe-buddy:latest
8b9455aeb39a111c972d424be6791804ce08bd011275e04f405d30a2652910ab
Compose: