Closed Dinth closed 1 year ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
/config/nginx/nginx.conf
/config/nginx/site-confs/default.conf
Can you update these and see if you still have an issue?
Same for me. I did a fresh installation today, without preexisting old config files, and I can't log in with the default settings described in the documentation. The only thing I see when trying to log in on port :9283 is a 502 error from the nginx server.
I actually managed to fix my problem by reinstalling while preserving the database and config file (copied them to a backup location prior to removing the container)
Ok, I revise my error message. The connection via port 9283 still works. It just takes what feels like an eternity. For me, a connection was only possible after ~5 minutes. Perhaps this information should be added to the documentation to avoid misunderstandings.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Did a fresh install of this, and given no further reports of issues, I think it could have been an issue with the rebase at the time. All seems OK now, so closing unless anything else shows up as broken
Expected Behavior
When i want to access my instance of Grocy on a new machine, i should be presented with a login form.
Current Behavior
Right now when im trying to access Grocy on a new machine, im presented with a completely blank page. But on the machines where i have already been signed in, Grocy works perfectly fine, so the problem is only with the login page.
Grocy's nginx log file shows:
FastCGI sent in stderr: "Unable to open primary script: /app/www/public/login.php (No such file or directory)" while reading the response header from upstream, client: 172.17.0.1, server: _, request: "GET /login.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "https://grocery.xxxx.xx"
But the only file in /app/www/public/ is index.htm
Steps to Reproduce
I am not 100% sure what is the main cause of the problem
Environment
OS: Debian 11.5, Docker 20.10.17 CPU architecture: x86_64 How docker service was installed: distro repo
Command used to create docker container (run/create/compose/screenshot)
Docker logs
After generating the above, i have followed the advice and replaced nginx.conf and default.conf with the relevant sample files, but this havent changed anything.