New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not possible to connect to grocy #256
Comments
I too am having the same problem |
Had this issue, too. Fixed by clearing out the cookies for the site and creating a new username and password for recipe-buddy from /setup endpoint |
I have the same problem. |
That is not possible, it's not possible to make another user. |
I have the same problem - can't create a new user from the frontend. But I can change the user accessing the mongodb; finding my way to get there (not very experienced with docker and docker-compose) I realized, that there are different networks interacting. |
I am having the same issue. React and typescript aren't familiar to me, so I am struggling figuring the actual issue out. I did write the two Grocy settings values directly to the mongodb and I have a connection to grocy now. My Settings page loads my Grocy URL and API Key, but when I click update, I still get PUT http://192.168.86.101:4000/api/users 401 (Unauthorized) [EDIT] Environment.... HomeAssistant installed in a Virtual Machine in Proxmox on an old HP ProLiant. Grocy is added to homeAssistant as an Addon. I do have an extra port mapped in the Grocy Addon settings so I can access Grocy directly rather than being forced to get routed through HomeAssistant. I tried three different ways/IPs/Paths of accessing Grocy. I have several other apps and tools successfully communicating with Grocy. |
Got the same with the official docker images, interestingly it works when running the dev version 🤷♂️ Adding a recipe will return a 500 but it still shows up in grocy |
I believe it is axios that is the problem. So.. my theory is that 1.3.2 is running in dev mode, where as 1.2.0 is running in the build. Axios is the problem, error |
Was going to go with Mealie until I found this plugin for Grocy but it doesn't work. 😥 |
I am also having trouble getting this to connect with Home Assistance installation of Grocy. I am able to connect my barcode scanner and apps to my phone without trouble, I just can't get this to communicate at all with Home Assistance without getting this error. I am going to guess the issue is that this is not running along side it. I have Home Assistant on my Pie and trying to connect to it from a device I have not logged into with, I will get a 404 page when I visit the base URL page and if I visit it when I am logged into Home Assistant I can see the Grocy page as normal. I think if there was a Ad-On of this built into Home Assistant it will resolve a lot of problems as I believe there is extra steps needed to communicate with Home Assistant installations with the Grocy app. |
I too am having the same problem |
+1 |
1 similar comment
+1 |
Same problem here |
+1 |
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. |
It's not possible to connect to grocy,
The url to my grocy is correct, and tried different api keys.
I use the same username and password as for grocy.
The backend log says when trying to connect to grocy:
TypeError: Cannot read properties of undefined (reading 'get')
And in the browser i get the following errors:
Failed to load resource: the server responded with a status of 401 (Unauthorized)
There is no problem with my Grocy, the api is working, im using api for other applications.
There is some problems in your system.
The text was updated successfully, but these errors were encountered: