Home A - Z

An Otter Wiki

Blame

22a8cf Hargata Softworks 2024-02-02 01:15:01 1
# Troubleshooting
2
Common issues and steps you can take to fix them.
3
4
## General Issues
5
377dc5 Hargata Softworks 2024-04-23 17:47:12 6
>| ### Feature(s) Stopped Working After Updating to Latest Version
7
>| Your browser might have cached an older version of a JavaScript(JS) file which is no longer compatible with the current version of LubeLogger. Try the following steps:
8
>|
c87ea9 Hargata Softworks 2025-10-18 21:33:43 9
>| 1. Verify - Try navigating to LubeLogger in Incognito mode or on another device
377dc5 Hargata Softworks 2024-04-23 17:47:12 10
>| 2. If everything functions as expected in Incognito, you have a caching issue.
11
>| 3. Clear your browser's cache or perform a hard reload(hit CTRL+SHIFT+R multiple times on most browsers)
c87ea9 Hargata Softworks 2025-10-18 21:33:43 12
>| 4. Check if the site works as intended on the [demo site](https://demo.lubelogger.com)
377dc5 Hargata Softworks 2024-04-23 17:47:12 13
14
>| ### Can't Send Email via SMTP
2e4a24 Hargata Softworks 2025-12-28 18:36:13 15
>| Note that for most email providers, you can no longer use your account password to authenticate and must instead generate an app password for LubeLogger to be able to authenticate on your behalf to your email provider's SMTP server. Note that certain email providers have completely phased out basic authentication for SMTP and is pushing for OAuth, LubeLogger does not support this method of authentication for emails, you must use a relay or switch to a different provider that still supports basic auth.
377dc5 Hargata Softworks 2024-04-23 17:47:12 16
17
>| #### Gmail SMTP Authentication Error
18
>|
19
>| Use port 587 instead of 465, LubeLogger only supports TLS.
20
21
>| ### Console shows Authentication Errors
22
>|
23
>| Those are purely informational, add this line in your environment variables to prevent information logs from showing up in the console.
24
>|
2e4a24 Hargata Softworks 2025-12-28 18:36:13 25
>| `LOGGING__LOGLEVEL__DEFAULT=Error` or `LOGGING__LOGLEVEL__DEFAULT=Warning`
22a8cf Hargata Softworks 2024-02-02 01:15:01 26
a1fc3a Hargata Softworks 2024-09-29 15:55:03 27
>| ### Data Missing after Update to Latest Version
28
>|
2e4a24 Hargata Softworks 2025-12-28 18:36:13 29
>| You didn't persist your docker volumes, check your docker-compose file. All your data should still be there however, they might just be anonymous volumes that you have to re-link back to the container.
a1fc3a Hargata Softworks 2024-09-29 15:55:03 30
22a8cf Hargata Softworks 2024-02-02 01:15:01 31
## Locale Issues
32
2c6cea Hargata Softworks 2025-12-28 01:29:39 33
>| ### Can't input values in with "," as decimal separator / shows up as 0.
377dc5 Hargata Softworks 2024-04-23 17:47:12 34
>|
9c9cc5 Hargata Softworks 2025-10-18 21:35:17 35
>| Ensure that your locale is configured correctly in the Server Settings Configurator
22a8cf Hargata Softworks 2024-02-02 01:15:01 36
377dc5 Hargata Softworks 2024-04-23 17:47:12 37
>| ### Locale Not Updating/ยค Currency Symbol/Date Format Issues
38
>|
2e4a24 Hargata Softworks 2025-12-28 18:36:13 39
>| You will need to restart the docker container/executable after configuring locale through the Server Settings Configurator. If configured using Environment Variables, you will need to run `docker compose up` again. If none of these work, you will need to check if the locale is installed on your OS as some don't come with locales enabled(i.e.: Arch Linux)
2c6cea Hargata Softworks 2025-12-28 01:29:39 40
41
>| ### Currency and Decimal Separator Mismatch
42
>|
a510b9 Hargata Softworks 2025-12-28 01:33:55 43
>| Certain locales have different decimal separators for currencies and regular decimals(i.e.: regular decimals are written as 12,34 but currencies are written as $12.34). This configuration is not supported within LubeLogger and can cause issues on certain labels within the app. You will need to select a different locale for your region where the decimal separators are identical.
2021c9 Hargata Softworks 2024-02-02 01:49:46 44
621921 Hargata Softworks 2024-03-28 04:48:29 45
## Postgres Issues
46
377dc5 Hargata Softworks 2024-04-23 17:47:12 47
>| ### Schema Does Not Exist
48
>|
2b40a9 DESKTOP-T0O5CDB\DESK-555BD 2024-09-20 15:19:12 49
>| Make sure that there is a schema named "app" in the database as specified in the Postgres connection string. For more information, see [[Postgres|Advanced/Postgres]]
621921 Hargata Softworks 2024-03-28 04:48:29 50
d68c48 Hargata Softworks 2024-04-11 04:01:21 51
## OpenID Connect(OIDC) Issues
52
377dc5 Hargata Softworks 2024-04-23 17:47:12 53
>| ### No Option to Login via OIDC
54
>|
2e4a24 Hargata Softworks 2025-12-28 18:36:13 55
>| Make sure Authentication is enabled, check "Enable Authentication" in Settings tab and set up root user credentials. You must also provide a name for the OIDC Provider in the Server Settings Configurator in order for the option to login via OIDC to show up on the login page.
76aa66 Hargata Softworks 2024-04-23 17:48:50 56
377dc5 Hargata Softworks 2024-04-23 17:47:12 57
>| ### Logging-in via OIDC Requires Token
58
>|
2e4a24 Hargata Softworks 2025-12-28 18:36:13 59
>| LubeLogger operates on an invite-only basis by default, a token will need to be generated for the user logging in via OIDC if it is their first time. Once an account for the user exists they will no longer be prompted for the token in subsequent login attempts. You can enable "Open Registration" in the Server Settings Configurator so that users can generate a token for themselves.
76aa66 Hargata Softworks 2024-04-23 17:48:50 60
377dc5 Hargata Softworks 2024-04-23 17:47:12 61
>| ### No Auto-Redirect to OIDC Provider
62
>|
63
>| A LogOutURL must be provided for the OIDC provider otherwise the OIDC login flow will not be auto-initiated.
d68c48 Hargata Softworks 2024-04-11 04:01:21 64
cbd446 Hargata Softworks 2024-09-05 03:22:40 65
>| ### Expected id_token, received {...}
66
>|
67
>| Add `openid` to the OpenIDConfig__Scope environment variable
68
d0d09d Hargata Softworks 2025-04-01 14:41:56 69
>| ### Issues with OpenID Provider
33e8e0 Hargata Softworks 2025-04-01 14:40:42 70
>|
dc1912 Hargata Softworks 2025-04-01 14:41:29 71
>| If none of the above troubleshooting steps worked, the problem might exist on the OpenID Provider side of things, LubeLogger has a built-in OpenID debugger which can be used to identify what key information might be missing from the OpenID Provider's Authorization Response. See [[Advanced Troubleshooting|Advanced/OpenID#advanced-troubleshooting]] for more information.
33e8e0 Hargata Softworks 2025-04-01 14:40:42 72
2021c9 Hargata Softworks 2024-02-02 01:49:46 73
## Server Issues
74
4c772e Hargata Softworks 2024-04-23 17:52:21 75
>| ### ERR_TOO_MANY_REDIRECTS
76
>|
77
>| 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:
78
>|
79
>| `The configured user limit (128) on the number of inotify instances has been reached`
80
>|
81
>| 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.
82
2e4a24 Hargata Softworks 2025-12-28 18:36:13 83
>| ### All changes to server settings are only reflected when restarted
84
>|
85
>| 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.
86
c17a40 Hargata Softworks 2024-08-12 15:01:00 87
## API Issues
88
89
>| ### Input Object Invalid
90
>|
2e4a24 Hargata Softworks 2025-12-28 18:36:13 91
>| This error is either caused by a missing field in the input object or if you have an additional trailing or leading space in the property names.
c17a40 Hargata Softworks 2024-08-12 15:01:00 92
7114f6 Hargata Softworks 2025-10-17 21:19:37 93
>| ### Can't Access LubeLogger Instance from Other Devices
94
>|
2e4a24 Hargata Softworks 2025-12-28 18:36:13 95
>| 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 configure the HTTP Endpoint via the Server Settings Configurator. Additionally, see [[Setting up HTTPS|Advanced/HTTPS]] for HTTPS/SSL Cert Configuration
e8c0f1 Hargata Softworks 2024-02-16 06:53:32 96
2021c9 Hargata Softworks 2024-02-02 01:49:46 97
### NGINX / Cloudflare
98
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.
99
100
Here's a sample Nginx reverse proxy configuration courtesy of [thehijacker](https://github.com/thehijacker)
101
```
102
server
103
{
104
listen 443 ssl http2;
105
server_name lubelogger.domain.com;
106
107
ssl_certificate /etc/nginx/ssl/acme/domain.com/fullchain.pem;
108
ssl_certificate_key /etc/nginx/ssl/acme/domain.com/key.pem;
109
ssl_dhparam /etc/nginx/ssl/acme/domain.com/dhparams.pem;
110
ssl_trusted_certificate /etc/nginx/ssl/acme/domain.com/fullchain.pem;
111
112
location /
113
{
114
proxy_pass http://192.168.28.53:8289;
115
client_max_body_size 50000M;
116
proxy_set_header Host $http_host;
117
proxy_set_header X-Real-IP $remote_addr;
118
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
119
proxy_set_header X-Forwarded-Proto $scheme;
120
proxy_http_version 1.1;
121
proxy_set_header Upgrade $http_upgrade;
122
proxy_set_header Connection "upgrade";
123
proxy_redirect off;
124
}
125
}
126
```
87e9c2 Hargata Softworks 2025-01-27 00:14:47 127
128
#### Troubleshooting Issues with Reverse Proxies
129
fd6ecc Hargata Softworks 2025-01-27 05:04:46 130
No support will be rendered by the maintainers for issues relating to reverse proxies because we are not going to spin up an instance of a reverse proxy with similar or identical configuration to yours just to figure out what's wrong. Any issues submitted on GitHub related to reverse proxies will be assigned an `unsupported` label, the issue will remain open for 15 days for others to chime in, and then it will be closed regardless of whether the issue is resolved or not.