...
If proxying is required for HTTP(S) connectivity in your environment, please see this article for help.
Unimus doesn't properly display special characters
In some cases, you might see that Unimus doesn't properly show special / national characters (they are shows as a question mark).
This can be solved by properly setting the DB charset / collation:
- Shut down Unimus
- Set DB collation to UTF8mb4 and charset to UTF8mb4_unicode_cs
- Start Unimus
After setting tables in the DB to this, any new special characters written to the DB should be displayed properly.
(this will not change data already existing in the DB)
MySQL DB initialization fails with "Specified key was too long" errors
When finishing the Deployment Wizard, you might see an error saying "Unable to upgrade database" when using a MySQL DB.
Some On some older versions of MySQL default to using the "utf8mb4" charset, which the DB only support VARCHARs of max size 191.
Unimus requires multiple DB columns to be VARCHAR(255).
...
Code Block | ||
---|---|---|
| ||
cat /etc/timezone timedatectl |
Both outputs should show correct timezone.
...