Support Database

From Freenas
Jump to: navigation, search

THIS SITE IS NOW DEPRECATED AND IN READ-ONLY MODE. REFER TO DOC.FREENAS.ORG FOR FREENAS DOCUMENTATION.

If you encounter a traceback error when using FreeNAS® or suspect that you have found a software or documentation bug, go to https://bugs.freenas.org/projects/freenas to see if your issue has already been reported. You do not need to register in order to search for existing issues. However, you will need to register if you wish to comment on an existing issue or create a new support issue.

Before creating a new issue, take the time to research your bug or feature request first. This is to prevent duplicating an existing issue and to ensure that your report contains the information that the developers need in order to implement the fix or the feature.

As part of your research, perform the following steps:

  • Determine if you are running the latest release of FreeNAS®. FreeNAS® developers tend to fix bugs rapidly and new features are being implemented as FreeNAS® matures. If you are not running the latest version, it is quite likely that the bug has already been fixed or the missing feature has been implemented. If this is the case, your best course of action is to backup your data and configuration and perform an upgrade to the latest version.
  • If you are running the latest version, use the search feature to see if a similar issue already exists. If one does, do not create a new issue. Instead, add a comment to the existing issue if you have additional information to add.

If a similar issue does not already exist, keep the following points in mind as you create a new issue:

1. You will need to register for an account, confirm you registration email address, and be logged in before you can create a new issue.

2. In the Tracker drop-down menu, select Bug if you are reporting a bug or Feature if you are making a feature request.

3. In the Subject field, include descriptive keywords that describe the issue. This is useful for other users who search for a similar problem.

4. In the Description section, describe the problem, how to recreate it, and include the text of any error messages. If you are requesting a feature, describe the benefit provided by the feature and, if applicable, provide examples of other products that use that feature or the URL of the homepage for the software.

5. If you would like to include a screenshot or log of your configuration or error, use the Browse button next to the Files field to upload the file.

6. Leave all of the other fields at their default values as these are used by developers as they take action on the issue.

7. Press the Preview link to read through your ticket before submitting it. Make sure it includes all of the information that someone else would need to understand your problem or request. Once you are satisfied with your ticket, click the Create Ticket button to submit it.

An email will automatically be sent to the address you used when registering whenever a comment or action occurs on your issue.

Personal tools
Navigation