### Can't input values in "," format / shows up as 0.
Ensure that your locale environment variables are configured correctly, note that if running via docker, both environment variables LANG and LC_ALL have to be identical.
-
### Can't change locale.
-
Environment variables are injected on deployment. You will need either need to re-deploy, or if that doesn't work, check if the environment variables are injected correctly, try to either re-create the .env file, or if you're using Portainer/Synology, you can try to enter the environment variables manually.
+
### Locale Not Updating/ยค Currency Symbol/Date Format Issues
+
Try the following steps:
+
1. Check if the environment variables are injected correctly(does SMTP/OICD configurations work)
+
2. Re-deploy Container
+
3. If that doesn't work, try re-creating the `.env` file
+
4. If using Portainer/Synology, you might have to enter the environment variables manually.
+
5. One last thing to try: copy and paste the environment variables in docker-compose.yml
## Server Issues
@@ 50,6 55,14 @@
Additionally, see [[Setting up HTTPS|HTTPS]] for HTTPS/SSL Cert Configuration
+
### ERR_TOO_MANY_REDIRECTS
+
+
If you encounter this error in your browser while attempting to navigate to your LubeLogger instance and it is accompanied by the following console error in your Docker Container:
+
+
`The configured user limit (128) on the number of inotify instances has been reached`
+
+
You have reached the maximum limit of file watchers across all your Docker Containers. In LubeLogger, file watchers are crucial for detecting changes to configuration files. To fix this, you will need to increase the inotify limit above 128.
+
### NGINX / Cloudflare
LubeLogger is a web app that runs on Kestrel, it literally doesn't matter if it's deployed behind a reverse proxy or Cloudflare tunnel. As long as the app can receive traffic on the port it's configured on, it will run.
