Adding a recipe to Grocy produces white page with white box

[Camreyn]

Clicking on ADD TO GROCY brings this page up with these errors when inspected.

Below is a screen grab of my grocy link, keep in mind both are the latest and grocy is running is Home Assistant.

These are very standard configs with no edits to the configs.

Any help would be appreciated, thank you!

[georgegebbett]

All that CORS stuff is a bit weird - does it work if you install this chrome extension and enable it for that site? https://chrome.google.com/webstore/detail/allow-cors-access-control/lhobafahddgcelffkeicbaginigeejlf

[georgegebbett]

A lot of the grocy communication happens in the browser because at the time I knew no better lol

[Camreyn]

Thank you for the swift reply, I was out for the weekend, that is on me, I apologize.

I installed the extension on firefox but I am still getting the same error. Cool extension however, added to my tool-belt.

[Camreyn]

Ignore previous, I refreshed the console because I was not convinced. I still get the same white page but the console does appear different now.

[creuzerm]

I was getting this error too. Somewhere in Grocy's instructions or one of the other tools that plug into Grocy there is the suggestion of setting a port so we can access Grocy direction and not route through HomeAssistant.

HomeAssitant->Settings->Addons->Grocy->Configuration->Network

Add port 9192 in that Network section. This doesn't appear to alter anything about the HomeAssistant integration, but now allows you to access Grocy directly, outside of HomeAssitant, by using that port.

This looks to stop the CORS errors which I think are from trying to access Grocy on the HomeAssistant path from outside HomeAssistant. Different IPs is different domains, so CORS is doing it's job.

Now, I get a 500 error when I try to add a recipe, but that's something I haven't dug into to try to sort out, and likely for a different issue thread if somebody already started one.

[Camreyn]

@creuzerm I can do as you did with the port but when I feed the http://192.168.1.39:9192/api/ into Recipe Buddy, it says it cannot connect to grocy. But if I go to that link in my web browser it brings me to the grocy api...

[creuzerm]

@TheEndOfYoRHa I am having the same issue as noted in #256

[dinvisible1]

I cant connect to my grocy instance, even with providing the the url and api key

[georgegebbett]

Hi all, apologies for the delay in getting back to you all on this - I have just released V2 which takes the Grocy URL as an env var into the Docker container and has a vastly simplified setup process and architecture - please have a go with this and open a new issue if you have further problems.