Troubleshooting

• Verify the JobManager REST endpoint URL and port are correct (default 8081) and use Test Connection on Configuration → Flink Cluster.
• Check network reachability (firewall / security group / VPC peering) between Flink Manager and the cluster.
• If TLS is enabled, confirm the truststore configuration on Configuration → Flink Cluster.
• Confirm the cluster is running and healthy from the Flink CLI or UI.

• The seeded accounts are admin/admin, operator/operator, developer/developer, viewer/viewer — change every password after the first login.
• Passwords are case-sensitive; make sure you are on the right console URL (…/flink-manager/).
• If you switched the authentication provider to LDAP or OIDC, the local login remains available as a fallback.
• Role and permission changes apply on the user's next login — sign out and back in after RBAC changes.

• Check DB_URL, DB_USERNAME, and DB_PASSWORD — Flink Manager requires a reachable PostgreSQL database (14+).
• Make sure the database exists and the user can create tables: the schema is created and migrated automatically on first startup.
• If you intended a quick test without a database, make sure SPRING_PROFILES_ACTIVE=in-memory-db is set — otherwise the default profile expects PostgreSQL.
• If migrations fail midway, fix the database issue and restart — migrations resume where they stopped.

• The SQL workbench is backed by the Flink SQL Gateway and is disabled until a gateway endpoint is configured — set FLINK_SQL_GATEWAY_URL or configure it on Configuration → Flink Cluster (default port 8083).
• Confirm the SQL Gateway is reachable from the Flink Manager host.

• Make sure you copied the full token with no truncation or extra whitespace.
• Check the license expiry date on Configuration → License — expired or missing licenses lock protected operations.
• If you're on a trial, request a fresh trial license from the license page — it is issued instantly.
• Only users with the LICENSE_MANAGE permission (the admin role by default) can install licenses.

• Validate the job JAR/SQL syntax in the editor before submitting.
• Check cluster capacity — add task managers if slots are exhausted.
• Review the job's error message in the jobs view.
• Check the savepoint directory: it must be writable by the JobManager and TaskManagers.

Flink Manager writes rotated log files (rotation by size, gzip compression, retention by age and total size). By default they live in a logs folder next to the start script, or in the /opt/flink-manager/logs volume in Docker. Tune the location and retention with the LOG_DIR, LOG_MAX_FILE_SIZE, LOG_MAX_HISTORY, and LOG_TOTAL_SIZE_CAP environment variables.

Administrative actions are additionally recorded in the audit log (Audit section of the console). For deeper diagnostics, also check the Flink JobManager and TaskManager logs on your cluster.