### Feature(s) Stopped Working After Updating to Latest Version
-
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:
-
-
1. Verify - Try navigating to LubeLogger in Incognito mode.
-
2. If everything functions as expected in Incognito, you have a caching issue.
-
3. Clear your browser's cache or perform a hard reload(hit CTRL+SHIFT+R multiple times on most browsers)
-
-
### Can't Send Email via SMTP
-
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.
-
-
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.
-
-
#### Gmail SMTP Authentication Error
-
Use port 587 instead of 465, LubeLogger only supports TLS.
-
-
### Console shows Authentication Errors
-
Those are purely informational, add this line in your environment variables to prevent information logs from showing up in the console.
-
-
`LOGGING__LOGLEVEL__DEFAULT=Error`
+
>| ### Feature(s) Stopped Working After Updating to Latest Version
+
>| 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:
+
>|
+
>| 1. Verify - Try navigating to LubeLogger in Incognito mode.
+
>| 2. If everything functions as expected in Incognito, you have a caching issue.
+
>| 3. Clear your browser's cache or perform a hard reload(hit CTRL+SHIFT+R multiple times on most browsers)
+
+
>| ### Can't Send Email via SMTP
+
>| 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.
+
>|
+
>| 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.
+
+
>| #### Gmail SMTP Authentication Error
+
>|
+
>| Use port 587 instead of 465, LubeLogger only supports TLS.
+
+
>| ### Console shows Authentication Errors
+
>|
+
>| Those are purely informational, add this line in your environment variables to prevent information logs from showing up in the console.
+
>|
+
>| `LOGGING__LOGLEVEL__DEFAULT=Error`
## Locale Issues
-
### Can't input values in "," format / shows up as 0.
-
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.
+
>| ### Can't input values in "," format / shows up as 0.
+
>|
+
>| 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.
-
### Locale Not Updating/¤ Currency Symbol/Date Format Issues
-
Try the following steps:
-
1. Check if the environment variables are injected correctly(does SMTP/OICD configurations work)
-
2. Re-deploy Container
-
3. If that doesn't work, try re-creating the `.env` file
-
4. If using Portainer/Synology, you might have to enter the environment variables manually.
-
5. One last thing to try: copy and paste the environment variables into docker-compose.yml
+
>| ### Locale Not Updating/¤ Currency Symbol/Date Format Issues
+
>|
+
>| Try the following steps:
+
>|
+
>| 1. Check if the environment variables are injected correctly(does SMTP/OICD configurations work)
+
>| 2. Re-deploy Container
+
>| 3. If that doesn't work, try re-creating the `.env` file
+
>| 4. If using Portainer/Synology, you might have to enter the environment variables manually.
+
>| 5. One last thing to try: copy and paste the environment variables into docker-compose.yml
## Postgres Issues
-
### Schema Does Not Exist
-
Make sure that there is a schema named "app" in the database as specified in the Postgres connection string. For more information, see [[Postgres]]
+
>| ### Schema Does Not Exist
+
>|
+
>| Make sure that there is a schema named "app" in the database as specified in the Postgres connection string. For more information, see [[Postgres]]
## OpenID Connect(OIDC) Issues
-
### No Option to Login via OIDC
-
Make sure Authentication is enabled, check "Enable Authentication" in Settings tab and set up root user credentials
-
-
### Logging-in via OIDC Requires Token
-
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.
-
-
### No Auto-Redirect to OIDC Provider
-
A LogOutURL must be provided for the OIDC provider otherwise the OIDC login flow will not be auto-initiated.
+
>| ### No Option to Login via OIDC
+
>|
+
>| Make sure Authentication is enabled, check "Enable Authentication" in Settings tab and set up root user credentials
+
>|
+
>| ### Logging-in via OIDC Requires Token
+
>|
+
>| 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.
+
>|
+
>| ### No Auto-Redirect to OIDC Provider
+
>|
+
>| A LogOutURL must be provided for the OIDC provider otherwise the OIDC login flow will not be auto-initiated.
