Troubleshooting

Record title not as expected

If you are seeing your record titles displaying unexpected data, check the title fields are defined correctly in the table admin page.

If the record titles are displaying correctly on their own record details pages but not when returned on a related table summary, then you should check that the foreign key relationship is defined specifically for that relationship.

Example

There is a table, "status", that is defined as follows:

+--------+--------------+------+-----+---------+----------------+
| Field  | Type         | Null | Key | Default | Extra          |
+--------+--------------+------+-----+---------+----------------+
| id     | int unsigned | NO   | PRI | NULL    | auto_increment |
| name   | varchar(30)  | YES  |     | NULL    |                |
| closed | tinyint(1)   | YES  |     | 0       |                |
+--------+--------------+------+-----+---------+----------------+

The `name` field is defined as a "main" title field and the table contains the following rows:

+----+------------------+--------+
| id | name             | closed |
+----+------------------+--------+
|  1 | New              |      0 |
|  2 | In progress      |      0 |
|  3 | Testing          |      0 |
|  4 | Client to revert |      0 |
|  5 | Resolved         |      1 |
|  6 | Closed           |      1 |
+----+------------------+--------+

This is referenced from the `status` field on another table, `call`, which is defined as follows:

+--------------+--------------+------+-----+---------+-------------------+
| Field        | Type         | Null | Key | Default | Extra             |
+--------------+--------------+------+-----+---------+-------------------+
| call_ref     | int unsigned | NO   | PRI | NULL    | auto_increment    |
| request_type | int unsigned | YES  | MUL | NULL    |                   |
| priority     | int unsigned | YES  | MUL | NULL    |                   |
| summary      | varchar(255) | YES  |     | NULL    |                   |
| description  | text         | YES  |     | NULL    |                   |
| status       | int unsigned | YES  | MUL | NULL    |                   |
| raised_by    | int unsigned | YES  | MUL | NULL    |                   |
| assigned_to  | int unsigned | YES  | MUL | NULL    |                   |
| created_at   | timestamp    | YES  |     | now()   | DEFAULT_GENERATED |
+--------------+--------------+------+-----+---------+-------------------+

However, despite the `name` field being defined as a "main" title field, the call summary is displayed like this:

In this case, the issue is that there is no foreign key relationship defined specifically for the `status` field on the `call` table. To fix this, you would need to run the following SQL command to create a foreign key relationship between the `status` field on the `call` table and the `id` field on the `status` table:

ALTER TABLE call
ADD FOREIGN KEY (status) REFERENCES status(id);

After running this command, the call summary will display as expected:

Connection problems

If Redbrix cannot connect to your database, work through the following checks:

• Host and port: Confirm the hostname or IP address is correct and that the server is listening on the port you entered (MySQL and MariaDB default to 3306, PostgreSQL to 5432).
• Remote access: Your database server must accept remote connections. Also, if applicable, check that your firewall allows inbound connections from address 13.134.60.54. On MySQL and MariaDB, check that the server is not bound only to 127.0.0.1 (its bind-address setting). On PostgreSQL, listen_addresses in postgresql.conf must include an address Redbrix can reach.
• User permissions: The database user must be allowed to connect from remote hosts. On MySQL and MariaDB, a user defined as 'user'@'localhost' will be rejected; it needs to be 'user'@'%' or allow Redbrix's address. On PostgreSQL, the server's pg_hba.conf needs a line allowing your login to reach your database from Redbrix's address, for example:

  hostssl  your_database  your_user  13.134.60.54/32  scram-sha-256

  (use host rather than hostssl if the server does not use encryption), then reload the server's configuration.
• Encryption: If Redbrix reports that the server does not support SSL/TLS, the server has no encryption set up. Untick "Require SSL/TLS" to connect without requiring it, or ask whoever runs the server to enable it.
• Credentials: Double-check the username, password, and database name. These are case-sensitive on most servers.
• Schema (PostgreSQL): If you connect but see no tables, check you have chosen the schema your tables are in, and that your login has USAGE on that schema and SELECT on its tables.

If you are still unable to connect, contact us and we will do our best to help.