QuTS hero h6.0 Beta Testing Issues - Container Station will not accept the Container folder

QuTS hero h6.0 Beta
,
1

Summary

Container Station repeatedly displayed “Failed to Change Container Folder” whenever I attempted to select a custom directory for container storage. Even after recreating the folder, fixing permissions, rebuilding ZFS datasets, and reinstalling Container Station, the error persisted.

Root Cause

QuTS hero enforces strict validation rules for Container Station storage paths:

  • The folder must be a QTS Shared Folder, not a manually created directory under /share.

  • The name “Container” is reserved and cannot be used for shared folders or datasets.

  • Manually created ZFS datasets (via CLI) are not registered in QTS’s internal configuration, so Container Station rejects them.

  • Container Station will only accept folders created through Control Panel → Shared Folders.

Resolution

  • Created a new shared folder through the GUI using a non‑reserved name (ContainerData).

  • Selected this shared folder directly in Container Station’s storage settings.

  • Container Station immediately accepted the folder once it was a properly registered shared folder.

2. QVPN UPnP Port Forwarding Errors (PPTP, OpenVPN, QBelt)

Summary

UPnP status showed mixed results: TCP services forwarded correctly, but several VPN services (PPTP, OpenVPN, QBelt) consistently failed UPnP port mapping. Only L2TP/IPSec succeeded.

Root Cause

The pattern revealed:

  • UDP ports were failing, while TCP ports succeeded.

  • QBelt was using UDP 443, a port often blocked or reserved by routers/ISPs.

  • Some routers do not support UPnP for UDP mappings.

  • Possible double NAT or ISP restrictions on low‑numbered UDP ports.

Resolution

  • Changed QBelt to a high, clean UDP port (60000), which avoids router and ISP filtering.

  • Manually forwarded the port on the router (UDP 60000 → NAS_IP).

  • Restarted QVPN service.

  • QBelt and other VPN services began functioning normally after switching to a high‑range UDP port.

3. ZFS Dataset Behavior on QuTS hero

Summary

Manually created ZFS datasets mounted correctly but were not recognized by QTS services such as Container Station.

Root Cause

QuTS hero requires datasets to be created as Shared Folders through the GUI so they are:

  • registered in QTS configuration

  • assigned proper ACLs

  • visible to system services

  • validated by Container Station

CLI‑created datasets bypass these registration steps.

Resolution

  • Recreated the dataset as a Shared Folder through the GUI.

  • Allowed QTS to manage mountpoints, ACLs, and metadata.

  • All dependent services (Container Station, QVPN) recognized the folder correctly afterward.

2

Shared folders are entirely different in QuTS Hero than QTS. This is one of the major differences between the two operating systems.

I don’t know if QTS requires the “Container” folder, but Container Station in QuTS Hero creates it automatically. This is well known behavior.

Using your YAML code, you can then use another other volume on the NAS or folder path for data storage, accesss by the container, etc.

3

Could you please clarify if you are referring to UPnP or UDP? Thank you!

Regarding your other points, we appreciate your feedback. We will forward them to our internal team for further verification.

4

I was about to share the screenshot showing how I solved the issue, but as soon as I enabled Qsirch again, my NAS became non‑responsive. This is exactly the same behavior I saw before — long periods where the system is unreachable. So I can’t grab the screenshot right now until the NAS recovers.

Once it stabilizes, I’ll share the details of what I did.

5

Thanks for the explanation — that makes sense. In my case, though, it looks like the demo firmware didn’t create the Container folder at all, or at least the creation failed. It never appeared automatically on my system.

I even tried creating the folder manually over SSH, but Container Station still wouldn’t recognize it. The only way I got it working was by creating a different folder name and pointing Container Station to that path instead.

So this might be a bug in the demo firmware, or at least something inconsistent with how the final QuTS Hero builds behave. Just wanted to share what I ran into in case anyone else sees the same issue.

6

The firmware doesn’t create the folder until you start Container Station for the first time. Then it will create it. What you should do is delete all the stuff you created and start over with it.

Also, this is not demo firmware. It is beta firmware. Big difference.

7

anyhow, create folder when i first open Container Station wont work

8

Hm.. OK. That sounds like a bug then.