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
>|
9
>| 1. Verify - Try navigating to LubeLogger in Incognito mode.
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)
12
13
>| ### Can't Send Email via SMTP
14
>| 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.
15
>|
16
>| If you've downloaded the .env file from the GitHub repo, there is an issue with how the file gets formatted when it is downloaded, you will have to copy the contents and re-create one manually on your machine.
17
18
>| #### Gmail SMTP Authentication Error
19
>|
20
>| Use port 587 instead of 465, LubeLogger only supports TLS.
21
22
>| ### Console shows Authentication Errors
23
>|
24
>| Those are purely informational, add this line in your environment variables to prevent information logs from showing up in the console.
25
>|
26
>| `LOGGING__LOGLEVEL__DEFAULT=Error`
22a8cf Hargata Softworks 2024-02-02 01:15:01 27
a1fc3a Hargata Softworks 2024-09-29 15:55:03 28
>| ### Data Missing after Update to Latest Version
29
>|
30
>| 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.
31
22a8cf Hargata Softworks 2024-02-02 01:15:01 32
## Locale Issues
33
377dc5 Hargata Softworks 2024-04-23 17:47:12 34
>| ### Can't input values in "," format / shows up as 0.
35
>|
36
>| 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.
22a8cf Hargata Softworks 2024-02-02 01:15:01 37
377dc5 Hargata Softworks 2024-04-23 17:47:12 38
>| ### Locale Not Updating/ยค Currency Symbol/Date Format Issues
39
>|
40
>| Try the following steps:
41
>|
42
>| 1. Check if the environment variables are injected correctly(does SMTP/OICD configurations work)
43
>| 2. Re-deploy Container
44
>| 3. If that doesn't work, try re-creating the `.env` file
45
>| 4. If using Portainer/Synology, you might have to enter the environment variables manually.
46
>| 5. One last thing to try: copy and paste the environment variables into docker-compose.yml
2021c9 Hargata Softworks 2024-02-02 01:49:46 47
621921 Hargata Softworks 2024-03-28 04:48:29 48
## Postgres Issues
49
377dc5 Hargata Softworks 2024-04-23 17:47:12 50
>| ### Schema Does Not Exist
51
>|
2b40a9 DESKTOP-T0O5CDB\DESK-555BD 2024-09-20 15:19:12 52
>| 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 53
d68c48 Hargata Softworks 2024-04-11 04:01:21 54
## OpenID Connect(OIDC) Issues
55
377dc5 Hargata Softworks 2024-04-23 17:47:12 56
>| ### No Option to Login via OIDC
57
>|
58
>| 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 59
377dc5 Hargata Softworks 2024-04-23 17:47:12 60
>| ### Logging-in via OIDC Requires Token
61
>|
62
>| 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 63
377dc5 Hargata Softworks 2024-04-23 17:47:12 64
>| ### No Auto-Redirect to OIDC Provider
65
>|
66
>| 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 67
cbd446 Hargata Softworks 2024-09-05 03:22:40 68
>| ### Expected id_token, received {...}
69
>|
70
>| Add `openid` to the OpenIDConfig__Scope environment variable
71
d0d09d Hargata Softworks 2025-04-01 14:41:56 72
>| ### Issues with OpenID Provider
33e8e0 Hargata Softworks 2025-04-01 14:40:42 73
>|
dc1912 Hargata Softworks 2025-04-01 14:41:29 74
>| 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 75
2021c9 Hargata Softworks 2024-02-02 01:49:46 76
## Server Issues
77
4c772e Hargata Softworks 2024-04-23 17:52:21 78
>| ### ERR_TOO_MANY_REDIRECTS
79
>|
80
>| 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:
81
>|
82
>| `The configured user limit (128) on the number of inotify instances has been reached`
83
>|
84
>| 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.
85
c17a40 Hargata Softworks 2024-08-12 15:01:00 86
## API Issues
87
88
>| ### Input Object Invalid
89
>|
90
>| 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
91
352cbc Hargata Softworks 2024-04-23 17:51:43 92
### Can't Access LubeLogger Instance from Other Devices
93
94
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`
95
96
Note: replace `10.0.0.4:5000/5011` with your local ip address and port
97
98
```
99
"Kestrel": {
42597e Hargata Softworks 2024-04-23 17:49:39 100
"Endpoints": {
101
"Http": {
102
"Url": "http://10.0.0.4:5000"
103
},
104
"Https": {
105
"Url": "https://10.0.0.4:5011"
106
},
4e8ab6 Hargata Softworks 2025-04-28 19:56:40 107
}
42597e Hargata Softworks 2024-04-23 17:49:39 108
}
352cbc Hargata Softworks 2024-04-23 17:51:43 109
```
885547 Hargata Softworks 2024-02-16 06:52:26 110
dd5d38 Hargata Softworks 2024-11-16 16:30:59 111
Verify that your JSON is still valid, make sure to add `,` appropriately, or you will get an error.
112
569bc8 Hargata Softworks 2025-04-28 19:18:00 113
Full Example of appsettings.json with the Kestrel portion added:
114
115
```
116
{
117
"Logging": {
118
"LogLevel": {
119
"Default": "Information",
120
"Microsoft.AspNetCore": "Warning"
121
}
122
},
123
"AllowedHosts": "*",
124
"UseDarkMode": false,
125
"UseSystemColorMode": false,
126
"EnableCsvImports": true,
127
"UseMPG": true,
128
"UseDescending": false,
129
"EnableAuth": false,
130
"DisableRegistration": false,
131
"EnableRootUserOIDC": false,
132
"HideZero": false,
133
"AutomaticDecimalFormat": false,
134
"EnableAutoReminderRefresh": false,
135
"EnableAutoOdometerInsert": false,
136
"EnableShopSupplies": false,
137
"ShowCalendar": true,
138
"EnableExtraFieldColumns": false,
139
"UseUKMPG": false,
140
"UseThreeDecimalGasCost": true,
141
"UseThreeDecimalGasConsumption": true,
142
"UseMarkDownOnSavedNotes": false,
143
"HideSoldVehicles": false,
144
"PreferredGasMileageUnit": "",
145
"UserColumnPreferences": [],
146
"UseUnitForFuelCost": false,
147
"PreferredGasUnit": "",
148
"UserLanguage": "en_US",
149
"VisibleTabs": [ 0, 1, 4, 2, 3, 6, 5, 8 ],
150
"TabOrder": [ 8, 9, 10, 0, 1, 4, 2, 7, 3, 6, 5 ],
151
"DefaultTab": 8,
152
"UserNameHash": "",
153
"UserPasswordHash": "",
154
"DefaultReminderEmail": "",
155
"Kestrel": {
156
"Endpoints": {
157
"Http": {
158
"Url": "http://10.0.0.4:5000"
159
},
160
"Https": {
161
"Url": "https://10.0.0.4:5011"
162
},
414a13 Hargata Softworks 2025-04-28 19:54:41 163
}
569bc8 Hargata Softworks 2025-04-28 19:18:00 164
}
165
}
166
```
167
2b40a9 DESKTOP-T0O5CDB\DESK-555BD 2024-09-20 15:19:12 168
Additionally, see [[Setting up HTTPS|Advanced/HTTPS]] for HTTPS/SSL Cert Configuration
e8c0f1 Hargata Softworks 2024-02-16 06:53:32 169
2021c9 Hargata Softworks 2024-02-02 01:49:46 170
### NGINX / Cloudflare
171
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.
172
173
Here's a sample Nginx reverse proxy configuration courtesy of [thehijacker](https://github.com/thehijacker)
174
```
175
server
176
{
177
listen 443 ssl http2;
178
server_name lubelogger.domain.com;
179
180
ssl_certificate /etc/nginx/ssl/acme/domain.com/fullchain.pem;
181
ssl_certificate_key /etc/nginx/ssl/acme/domain.com/key.pem;
182
ssl_dhparam /etc/nginx/ssl/acme/domain.com/dhparams.pem;
183
ssl_trusted_certificate /etc/nginx/ssl/acme/domain.com/fullchain.pem;
184
185
location /
186
{
187
proxy_pass http://192.168.28.53:8289;
188
client_max_body_size 50000M;
189
proxy_set_header Host $http_host;
190
proxy_set_header X-Real-IP $remote_addr;
191
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
192
proxy_set_header X-Forwarded-Proto $scheme;
193
proxy_http_version 1.1;
194
proxy_set_header Upgrade $http_upgrade;
195
proxy_set_header Connection "upgrade";
196
proxy_redirect off;
197
}
198
}
199
```
87e9c2 Hargata Softworks 2025-01-27 00:14:47 200
201
#### Troubleshooting Issues with Reverse Proxies
202
fd6ecc Hargata Softworks 2025-01-27 05:04:46 203
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.