Troubleshooting

• Custom Grafana Dashboard - YML Files not being processed
• Resolving “Login failed: User sync failed” Error in Grafana

Custom Grafana Dashboard - YML Files not being processed

What

A custom Grafana dashboard may stop processing data from YML files after the FileWave API key is regenerated. When that happens, Grafana keeps using the old bearer_token_file, so the YML-backed targets cannot authenticate.

When/Why

When you use 3.1.2 Testing the Prometheus Scrape while setting up a custom Dashboard with a YML file, the targets may show “DOWN,” as shown below. Dashboard widgets that depend on those targets will not populate.

How

To fix this, SSH to the FileWave Server and remove bearer_token_file. Restart FileWave Server so it regenerates the file with the current API key. Hosted customers should contact FileWave Support; support often handles custom YML uploads and can remove the file for you.

rm /usr/local/etc/filewave/prometheus/conf.d/bearer_token_file
/usr/local/bin/fwcontrol server restart

Resolving “Login failed: User sync failed” Error in Grafana

What

This article explains how to resolve the “Login failed: User sync failed” error when an administrator signs in to the FileWave Dashboard through Grafana.

When/Why

This error occurs when a FileWave administrator account uses a username that conflicts with Grafana. The most common case is a FileWave Central administrator named “admin”, since Grafana also uses an internal “admin” account. The conflict can appear when that administrator tries to open the FileWave Dashboard through Grafana.

How

Avoid using “admin” as a FileWave administrator username. Use the steps below for a built-in administrator account. If the affected administrator comes from LDAP or an IdP, rename or adjust the account in that identity source instead.

1.  Access FileWave Central:
   • Open FileWave Central.
   • Navigate to Preferences -> Manage Administrators.
2. Rename the “admin” Account:
   • Identify if an “admin” user exists.
   • Rename this user to a specific named account, such as a real administrator name.
   • Ensure the new username is unique and does not conflict with other system usernames.
3. Create Named Accounts:
   • Create individual named accounts for each administrator.
   • Named administrator accounts help prevent this Grafana conflict and make audit trails easier to understand.
4. Update Login Credentials:
   • Inform administrators whose usernames changed.
   • Update any saved login credentials in browsers or password managers accordingly.

Related Links

• Managing FileWave Administrators

Digging Deeper

Grafana uses a default “admin” account during initial setup. If FileWave also has an administrator named “admin”, Grafana user synchronization can fail because the username is already reserved or in use.

Named accounts also improve accountability because administrator activity can be tied to a person instead of a shared generic login.

For FileWave administrator-account setup, see the related administrator-management article above.