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
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.
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
>|
25
>| `LOGGING__LOGLEVEL__DEFAULT=Error`
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
>|
29
>| You didn't persist your docker volumes for, 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.
30
22a8cf Hargata Softworks 2024-02-02 01:15:01 31
## Locale Issues
32
377dc5 Hargata Softworks 2024-04-23 17:47:12 33
>| ### Can't input values in "," format / shows up as 0.
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
>|
9c9cc5 Hargata Softworks 2025-10-18 21:35:17 39
>| You will need to restart the docker container/executable after configuring locale
2021c9 Hargata Softworks 2024-02-02 01:49:46 40
621921 Hargata Softworks 2024-03-28 04:48:29 41
## Postgres Issues
42
377dc5 Hargata Softworks 2024-04-23 17:47:12 43
>| ### Schema Does Not Exist
44
>|
2b40a9 DESKTOP-T0O5CDB\DESK-555BD 2024-09-20 15:19:12 45
>| 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 46
d68c48 Hargata Softworks 2024-04-11 04:01:21 47
## OpenID Connect(OIDC) Issues
48
377dc5 Hargata Softworks 2024-04-23 17:47:12 49
>| ### No Option to Login via OIDC
50
>|
51
>| Make sure Authentication is enabled, check "Enable Authentication" in Settings tab and set up root user credentials
76aa66 Hargata Softworks 2024-04-23 17:48:50 52
377dc5 Hargata Softworks 2024-04-23 17:47:12 53
>| ### Logging-in via OIDC Requires Token
54
>|
55
>| LubeLogger operates on an invite-only basis, 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.
76aa66 Hargata Softworks 2024-04-23 17:48:50 56
377dc5 Hargata Softworks 2024-04-23 17:47:12 57
>| ### No Auto-Redirect to OIDC Provider
58
>|
59
>| 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 60
cbd446 Hargata Softworks 2024-09-05 03:22:40 61
>| ### Expected id_token, received {...}
62
>|
63
>| Add `openid` to the OpenIDConfig__Scope environment variable
64
d0d09d Hargata Softworks 2025-04-01 14:41:56 65
>| ### Issues with OpenID Provider
33e8e0 Hargata Softworks 2025-04-01 14:40:42 66
>|
dc1912 Hargata Softworks 2025-04-01 14:41:29 67
>| 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 68
2021c9 Hargata Softworks 2024-02-02 01:49:46 69
## Server Issues
70
4c772e Hargata Softworks 2024-04-23 17:52:21 71
>| ### ERR_TOO_MANY_REDIRECTS
72
>|
73
>| 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:
74
>|
75
>| `The configured user limit (128) on the number of inotify instances has been reached`
76
>|
77
>| 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.
78
c17a40 Hargata Softworks 2024-08-12 15:01:00 79
## API Issues
80
81
>| ### Input Object Invalid
82
>|
83
>| This error is either caused by a missing field in the input object or if the API client is passing the payload in as json. If all fields are already provided, check and make sure that the payload is passed in as either form-data or x-www-urlencoded
84
7114f6 Hargata Softworks 2025-10-17 21:19:37 85
>| ### Can't Access LubeLogger Instance from Other Devices
86
>|
7caed0 Hargata Softworks 2025-10-17 21:20:08 87
>| 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 88
2021c9 Hargata Softworks 2024-02-02 01:49:46 89
### NGINX / Cloudflare
90
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.
91
92
Here's a sample Nginx reverse proxy configuration courtesy of [thehijacker](https://github.com/thehijacker)
93
```
94
server
95
{
96
listen 443 ssl http2;
97
server_name lubelogger.domain.com;
98
99
ssl_certificate /etc/nginx/ssl/acme/domain.com/fullchain.pem;
100
ssl_certificate_key /etc/nginx/ssl/acme/domain.com/key.pem;
101
ssl_dhparam /etc/nginx/ssl/acme/domain.com/dhparams.pem;
102
ssl_trusted_certificate /etc/nginx/ssl/acme/domain.com/fullchain.pem;
103
104
location /
105
{
106
proxy_pass http://192.168.28.53:8289;
107
client_max_body_size 50000M;
108
proxy_set_header Host $http_host;
109
proxy_set_header X-Real-IP $remote_addr;
110
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
111
proxy_set_header X-Forwarded-Proto $scheme;
112
proxy_http_version 1.1;
113
proxy_set_header Upgrade $http_upgrade;
114
proxy_set_header Connection "upgrade";
115
proxy_redirect off;
116
}
117
}
118
```
87e9c2 Hargata Softworks 2025-01-27 00:14:47 119
120
#### Troubleshooting Issues with Reverse Proxies
121
fd6ecc Hargata Softworks 2025-01-27 05:04:46 122
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.