However, it is important to bear in mind that extending the idle timeout can potentially increase security risks. For example, if you log into FileWave Anywhere on a shared or public computer and forget to log out, you could remain logged in until the timeout occurs, leaving your account vulnerable.
## How To adjust the idle timeout, you will need to modify a specific line in the `settings_custom.py` file on your FileWave Server. This file is located at `/usr/local/filewave/django/filewave/` on macOS or Linux systems.**Please note:** If you are a hosted customer, you will not have direct access to the server and will need to contact FileWave Support to have them make this change for you.
Here is the process for self-hosted customers: 1. Open the `settings_custom.py` file in a text editor. 2. Add or modify the following line: `UI_INACTIVITY_TIMEOUT = 25 * 60 # seconds the UI can stay inactive before auto logoff` 3. Replace the `25` in this line with the number of minutes you want for your idle timeout. For instance, if you want the timeout to be 60 minutes, the line should read: `UI_INACTIVITY_TIMEOUT = 60 * 60`. 4. Save and close the file. 5. To activate the change, you need to restart the server. Do this by running the following command in the terminal: `fwcontrol server restart`. After these steps, the idle timeout will be set to the number of minutes you specified. # Could not create the /Volumes/XYZ directory error when opening client info ## Problem Client Info may show a "Could not create the directory" error when its last Export Current Tab location no longer exists. This commonly happens after exporting to an external drive and then disconnecting that drive. The path in the message will usually be different from the example below.  ## Solution Select a new export location to clear the error: - Open Client Info for a macOS or Windows client. - Select "Export Current Tab" on the left side of the Client Info window. - Choose a local folder on the computer, such as your desktop. - Select "Save".  - Close Client Info and open it again. The directory error should no longer appear. # Dashboard Warning levels and Descriptions ## Problem The table below provides an overview of the information that is returned by the Dashboard in the FileWave Admin console. ## Environment FileWave Central Console ## Resolution| Item | Description |
|---|---|
| Free Disk Space | Free disk space on fwxserver (db location). Warning if < 50GB or < 20% Total space, Error if < 25GB or < 10% total space. |
| CPU Load | CPU Load on fwxserver. Always OK. |
| Google Cloud Messaging | Returns Google Cloud Messaging status. Cached 1 minute. Error if configuration is not correct. |
| Total Disk Space | Total disk space on fwxserver (db location). |
| Client distribution | Returns client OS distribution (OSX, Windows, iOS, Android...). Cached 1 minute. |
| Free RAM | Free RAM on fwxserver. Always OK as some systems like OSX will free memory on demand only. |
| APN for MDM | Returns APN certificate status for MDM. Cached 1 minute. Warning if certificate expires in less than 30 days. Error if certificate is missing, expired, or Root certificate is missing. |
| VPP Tokens | Returns VPP tokens status. Cached 5 minutes. Warning if token expires in less than 30 days. Error if token is expired or incorrect. |
| FileWave Client/Mobile License | Returns License Status. Cached 1 minute. If you have more than 50 licenses: warning if available count goes below 10, error when 0. If you have less than 50 licenses: warning if available count goes below 4, error when 0. |
| Entreprise app file (ipa) | Check ipa status. Cached 1 hour. Warning if IPA file is local but does not have expected size. Error is IPA file is not on disk for local IPA, or not reachable for external IPAs. |
| DEP Accounts | Returns DEP Accounts status. Cached 5 minutes. Warning if access token expires in less than 30 days. Error if token is expired or incorrect. |
| Email sent | Returns Email sent status for the 7 past days. Cached 5 minutes. Warning if mails are still in the queue (not sent) Error if mails could not be sent (SMTP error). Note that we can't check if the POP/IMAP server rejected the mail. returns the following dict : 'success': , 'pending': , 'error': : , ... |
| Email settings | Returns email settings status. Cached 5 minutes. Error if can't connect to SMTP server. |
| LDAP Extraction status | LDAP Extraction status. Warning if one or more servers have not been contacted yet, Error if there was an error during extraction. |
| Total RAM | Total RAM on fwxserver. |
| Smart Group Count | Number of evaluated SmartGroups. Warning if last report occurred more than 1h ago, error if 2h ago. |
| [](https://kb.filewave.com/uploads/images/gallery/2025-08/V1WGBxoBq2lSpxVR-image.png) | [](https://kb.filewave.com/uploads/images/gallery/2025-08/ssygEWpYF2TwblHK-image.png) |
| **Language** | **Locale Code** | **Notes** |
|---|---|---|
| **English (US)** | en\_US | Use for American English. |
| **German** | de\_DE | Standard locale for German in Germany. |
| **French** | fr\_FR | Standard locale for French in France. |
| **Korean** | ko\_KR | Korean for South Korea. |
| **Japanese** | ja\_JP | Japanese for Japan. |
| **Chinese (Simplified)** | zh\_CN | For Mainland China. |
| **Chinese (Traditional)** | zh\_TW | For Taiwan. |
| [](https://kb.filewave.com/uploads/images/gallery/2025-08/Km2fywj9uemHBHGK-filewave-admin-2025-08-29-15-02-55.png) | [](https://kb.filewave.com/uploads/images/gallery/2025-08/DYBMBNeBw19F6JC8-image.png) |
| **Language** | **Locale Code** | **Notes** |
|---|---|---|
| **English (US)** | en\_US | Use for American English. |
| **German** | de\_DE | Standard locale for German in Germany. |
| **French** | fr\_FR | Standard locale for French in France. |
| **Korean** | ko\_KR | Korean for South Korea. |
| **Japanese** | ja\_JP | Japanese for Japan. |
| **Chinese (Simplified)** | zh\_CN | For Mainland China. |
| **Chinese (Traditional)** | zh\_TW | For Taiwan. |
When you work in FileWave Central, your changes are made in the next model. They do not affect managed devices until you update the model.
## Resolution ### Revert Revert discards unpublished model changes and returns FileWave Central to the currently deployed model. For example, the deployed model is 10. You open FileWave Central and make changes that would become model 11 when published. - You create a Fileset called **My Fileset A**. - You delete a Fileset called **Old Fileset B**. - You move the association for **Fileset C** from **Group 1** to **Group 2**. If you choose **Revert to Last Model** before updating the model, FileWave discards those unpublished changes and goes back to model 10. If you already updated the model to 11, revert no longer helps because model 11 is now the current model. ### Restore Restore makes a previous published model current again. Using the same example, if you published model 11 and then realized model 10 was the last good model, restore model 10: ```shell sudo fwcontrol server restore 10 ```The server keeps the last 20 models.
After the command finishes, quit FileWave Central and open it again. Model 10 is now restored. In this example: - **My Fileset A** no longer appears in the Filesets view, although its uploaded data may still exist on the server. - **Old Fileset B** appears again in the Filesets view, but its payload data is missing from the server. - The association for **Fileset C** points back to **Group 1**.Restoring a previous model does not restore deleted Fileset payload data. Use your backups for that.
## Additional Information If you need to recover from a major model mistake, contact [FileWave Support](https://help.filewave.com) before making more changes.