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
Superuser can't access the action menu (3 vertical dots) on any recipe #2863
Comments
clear the browser cache and confirm that there are no errors in the browser console. |
Thanks @smilerz, there's definitely an error in the Browser console when I access a recipe... here it is:
I also see this warning:
Does it ring a bell ?! |
Do you have another proxy sitting in front of nginx? |
The standard Synology Reverse Proxy is configured like this: |
I am seeing the exact same issue. New install with the same browser errors in the console. Is this a bug? If not, how can I resolve this? |
It's not a bug. It's a setup issue. You have put a proxy in front of Tandoor and probably not setup headers correctly. |
I added the requested header, but it did not solve the issue... I'll try to troubleshoot it a bit later this week. |
Same. If you find a resolve, could you please share? |
Sure, I will... I however saw last night that the Mealie Team has released a new stable version of their application with loads of bug fixes and features... Being an existing Mealie user that was looking for additional features, I'll give the new Mealie version a shot as the previous version was a breeze to install. |
I went the same route. With lots of trial and error following the headers documentation, I'm trying the Mealie release. With the same setup and headers, it's working correctly. Thanks for the recommendation |
I finally installed the latest version of Mealie, it installs correctly, and it's snappy. |
Tandoor Version
Dec 3 commit abf8f79
Setup
Docker / Docker-Compose
Reverse Proxy
Others (please state below)
Other
Login Portal (Synology Reverse Proxy)
Bug description
I installed Tandoor using Portainer (docker-compose), and the installation completed successfully. When I access Tandoor for the first time, I get asked to create a superuser, which I do.
The authentication with the superuser credentials is then successful, and I can create a new recipe using the dropdown menu in the top banner. The recipe gets created without a problem.
I can then search for the recipe, and access it, no problem... Once in the recipe, I don't have access to the "three vertical dots" (I don't see it) to edit or delete the newly created recipe.
If I access to the Users menu, in the Admin feature, I can see that this user is active, and is flagged as a superuser.
Any idea what it could be ?
docker-compose
NGINX tandoor.conf
Environment variables
Relevant logs
No response
The text was updated successfully, but these errors were encountered: