Skip to content

Commit 5d4a611

Browse files
Merge pull request #213 from eshtek/dev
Release dev to main
2 parents 127e8d2 + e75fff1 commit 5d4a611

1 file changed

Lines changed: 18 additions & 0 deletions

File tree

docs/troubleshooting/common-issues/ApplicationErrors.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,24 @@
1818
![](../../public/assets/screenshots/app-troubleshooting-guide/3.png)
1919
:::
2020

21+
### Custom Application Name Conflicts
22+
23+
When installing a custom application through TrueNAS, the name you assign must be unique across your system. If a custom application shares the exact name of an application available in the HexOS catalog, the installation will fail and the catalog application will not be installable until the conflict is resolved. This commonly occurs when setting up multiple instances of the same application configured for different purposes, such as:
24+
25+
- A separate Jellyfin instance for a kids-only media library
26+
- An additional Minecraft server running a different modpack or world
27+
- A dedicated Home Assistant instance used as a staging environment
28+
- A second Vaultwarden instance reserved for family members
29+
- An extra PostgreSQL instance isolated to a specific application's data
30+
31+
HexOS will display a warning banner on the catalog application's details page when a name conflict is detected. To avoid this issue, choose a distinct name for your custom application by appending a descriptor or suffix. For example, if the catalog application is named `sonarr`, consider naming your custom application one of the following instead:
32+
33+
- `sonarr-2`
34+
- `sonarr-anime`
35+
- `sonarr-4k`
36+
37+
If you have already installed a custom application whose name matches a catalog application, uninstall or rename the custom application before installing the catalog version.
38+
2139
## Updating
2240

2341
An App has to be running for it to updated. <br>

0 commit comments

Comments
 (0)