>| 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.
+
### Can't Access LubeLogger Instance from Other Devices
This problem is specific to the Windows Standalone Executable, the problem stems from the fact that Kestrel is configured by default to listen on and only on localhost. In order to get around this, you will need to retrieve the IPv4 address of your local machine, and add the following section into `appsettings.json`
@@ 83,14 91,6 @@
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.
