Home A - Z

An Otter Wiki

Blame

22a8cf Hargata Softworks 2024-02-02 01:15 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 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 27
28
## Locale Issues
29
377dc5 Hargata Softworks 2024-04-23 17:47 30
>| ### Can't input values in "," format / shows up as 0.
31
>|
32
>| 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 33
377dc5 Hargata Softworks 2024-04-23 17:47 34
>| ### Locale Not Updating/ยค Currency Symbol/Date Format Issues
35
>|
36
>| Try the following steps:
37
>|
38
>| 1. Check if the environment variables are injected correctly(does SMTP/OICD configurations work)
39
>| 2. Re-deploy Container
40
>| 3. If that doesn't work, try re-creating the `.env` file
41
>| 4. If using Portainer/Synology, you might have to enter the environment variables manually.
42
>| 5. One last thing to try: copy and paste the environment variables into docker-compose.yml
2021c9 Hargata Softworks 2024-02-02 01:49 43
621921 Hargata Softworks 2024-03-28 04:48 44
## Postgres Issues
45
377dc5 Hargata Softworks 2024-04-23 17:47 46
>| ### Schema Does Not Exist
47
>|
48
>| Make sure that there is a schema named "app" in the database as specified in the Postgres connection string. For more information, see [[Postgres]]
621921 Hargata Softworks 2024-03-28 04:48 49
d68c48 Hargata Softworks 2024-04-11 04:01 50
## OpenID Connect(OIDC) Issues
51
377dc5 Hargata Softworks 2024-04-23 17:47 52
>| ### No Option to Login via OIDC
53
>|
54
>| 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 55
377dc5 Hargata Softworks 2024-04-23 17:47 56
>| ### Logging-in via OIDC Requires Token
57
>|
58
>| 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 59
377dc5 Hargata Softworks 2024-04-23 17:47 60
>| ### No Auto-Redirect to OIDC Provider
61
>|
62
>| 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 63
cbd446 Hargata Softworks 2024-09-05 03:22 64
>| ### Expected id_token, received {...}
65
>|
66
>| Add `openid` to the OpenIDConfig__Scope environment variable
67
2021c9 Hargata Softworks 2024-02-02 01:49 68
## Server Issues
69
4c772e Hargata Softworks 2024-04-23 17:52 70
>| ### ERR_TOO_MANY_REDIRECTS
71
>|
72
>| 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:
73
>|
74
>| `The configured user limit (128) on the number of inotify instances has been reached`
75
>|
76
>| 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.
77
c17a40 Hargata Softworks 2024-08-12 15:01 78
## API Issues
79
80
>| ### Input Object Invalid
81
>|
82
>| 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
83
352cbc Hargata Softworks 2024-04-23 17:51 84
### Can't Access LubeLogger Instance from Other Devices
85
86
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`
87
88
Note: replace `10.0.0.4:5000/5011` with your local ip address and port
89
90
```
91
"Kestrel": {
42597e Hargata Softworks 2024-04-23 17:49 92
"Endpoints": {
93
"Http": {
94
"Url": "http://10.0.0.4:5000"
95
},
96
"Https": {
97
"Url": "https://10.0.0.4:5011"
98
},
99
}
352cbc Hargata Softworks 2024-04-23 17:51 100
```
885547 Hargata Softworks 2024-02-16 06:52 101
e8c0f1 Hargata Softworks 2024-02-16 06:53 102
Additionally, see [[Setting up HTTPS|HTTPS]] for HTTPS/SSL Cert Configuration
103
2021c9 Hargata Softworks 2024-02-02 01:49 104
### NGINX / Cloudflare
105
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.
106
107
Here's a sample Nginx reverse proxy configuration courtesy of [thehijacker](https://github.com/thehijacker)
108
```
109
server
110
{
111
listen 443 ssl http2;
112
server_name lubelogger.domain.com;
113
114
ssl_certificate /etc/nginx/ssl/acme/domain.com/fullchain.pem;
115
ssl_certificate_key /etc/nginx/ssl/acme/domain.com/key.pem;
116
ssl_dhparam /etc/nginx/ssl/acme/domain.com/dhparams.pem;
117
ssl_trusted_certificate /etc/nginx/ssl/acme/domain.com/fullchain.pem;
118
119
location /
120
{
121
proxy_pass http://192.168.28.53:8289;
122
client_max_body_size 50000M;
123
proxy_set_header Host $http_host;
124
proxy_set_header X-Real-IP $remote_addr;
125
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
126
proxy_set_header X-Forwarded-Proto $scheme;
127
proxy_http_version 1.1;
128
proxy_set_header Upgrade $http_upgrade;
129
proxy_set_header Connection "upgrade";
130
proxy_redirect off;
131
}
132
}
133
```