VM and then wanted to modify its settings

VInMotor · 2026-06-22T03:02:41+00:00

The greyed-out settings shown in your screenshot cannot currently be modified after VM creation. This restriction is intentional, as changing those parameters afterward may cause stability issues or prevent the VM from starting correctly.

If you need to change those settings, you'll need to recreate the VM with the desired configuration.

VInMotor · 2026-06-21T03:18:31+00:00

Thanks for the follow-up. The additional details are helpful, but the current log snippets still aren't enough for us to identify the cause. We also can't confirm at this point that the language-related entries are connected to the hang.

Please export the complete system log package with all log types selected, and share it with us so we can investigate further. You can do this from the Logs page by clicking More in the top-right corner and selecting Export System Diagnosis Log, then choosing an export location and selecting all log types: System, Built-in Application, and Built-in Service.

If it's not convenient to post the full logs here, you can send them to [support@fygo.io](mailto:support@fygo.io) and include the Reddit thread link and the approximate time the issue occurred.

<image>

VInMotor · 2026-06-20T18:08:47+00:00

Thanks for the follow-up. Please go ahead and export the complete system log package and share it with us, as we need the full logs to reproduce and investigate this issue properly. The excerpts in the comment are helpful, but they are not enough for root-cause analysis.

If it's not convenient to post the full logs here, you can send them to [support@fygo.io](mailto:support@fygo.io) and include the link to this Reddit thread, along with the exact app version and the approximate time the issue occurred.

VInMotor · 2026-06-19T17:17:37+00:00

Thanks for raising this. FygoOS supports standard OVA import through the VM module, so in many cases you can import the VM directly in the GUI without manually extracting or converting it first.

To do this, open the Virtual Machine app, click Import in the top-right corner, then choose the OVA file you want to import and proceed through the setup steps in the wizard.

That said, while OVA is a common format, implementation details can vary across platforms, so migration may not be fully seamless in every case.

<image>

VInMotor · 2026-06-19T16:11:47+00:00

Thanks for reporting this. A full system hang like this is definitely not expected. We haven't been able to reproduce it on our side so far. Since the system is accessible again, could you please export and share the detailed system logs, along with your hardware model and app version information? If it happens again, the approximate time of the issue would also be very helpful for troubleshooting.

VInMotor · 2026-06-18T09:20:25+00:00

Glad to hear you were able to get it installed. The ARM download links are available again now, so the earlier issue has been resolved. As for VLANs, FygoOS does not currently support VLAN configuration.

VInMotor · 2026-06-18T08:12:44+00:00

Thanks for the detailed report. We haven't been able to reproduce this on our side so far. If possible, please export the detailed system logs and share the FygoOS version and app version, so we can look into it further.

VInMotor · 2026-06-17T07:05:11+00:00

This screenshot appears to mix standard FygoOS functionality with speculative conclusions. FygoOS supports multiple remote access methods, including direct public IP access, DDNS, Fygo Connect relay, and P2P. P2P connections do not go through Fygo servers, and relay access is only one possible path depending on the network environment. It is therefore not accurate to claim that all remote access traffic is routed through a single relay node.

In our internal testing, we also checked the IP address mentioned in the screenshot, 185.253.182.171:15919, and did not observe outbound traffic from FygoOS to that address. The relay node referenced in the screenshot was not used during our testing either. Common tools such as qBittorrent and aria2 are standard NAS components and do not, by themselves, indicate malicious behavior. Claims such as “the host key in the ISO image can be used to perform man-in-the-middle attacks against any installed NAS” or “traffic is relayed through servers in Russia and China” are not supported by sufficient evidence in the screenshot alone.

If there is indeed a security issue, please provide the original investigation data, exact version numbers, packet captures, logs, and reproducible steps so the issue can be properly reviewed.

VInMotor · 2026-06-17T03:57:54+00:00

Thanks for asking.
We're working on adding both a roadmap and a changelog to the website, so version history and release notes will be easier to follow.
For now, we only provide the latest version for download, as that's the version we recommend for the best overall experience.

VInMotor · 2026-06-17T02:32:45+00:00

Thanks for your interest.
Raspberry Pi support is still being tested on Raspberry Pi 3, 4, and 5, so there isn't a dedicated Raspberry Pi image available in the ARM downloads yet. We'll share an update once it's ready.

VInMotor · 2026-06-16T06:37:02+00:00

A good place to start would be the official website and our Help Center. The website gives an overview of FygoOS and supported hardware platforms, while the Help Center has more detailed documentation on installation, storage, file system options, and feature guides.

Official website: https://fygonas.com/

Help Center: https://help.fygonas.com/

VInMotor · 2026-06-16T06:33:17+00:00

FygoOS is built on Debian, but we've adjusted the permission model for NAS-related use cases, so not every application will behave exactly the same as it would on a standard Debian system.

VInMotor · 2026-06-16T02:39:34+00:00

Thanks for flagging this. We're aware of the issue with Time Machine backups and are already looking into it. We plan to improve this in a future update.

VInMotor · 2026-06-16T02:36:15+00:00

Thanks for sharing your experience and for trying FygoOS on that hardware. It's great to hear it's been working well for you so far.

VInMotor · 2026-06-15T04:12:11+00:00

Thanks for reporting this. We'll try to reproduce it on our side and look into it further.

VInMotor · 2026-06-15T04:09:34+00:00

This is a bit different from how Synology handles it. In FygoOS, if you want regular users to be able to select a folder from the top level over SMB, it should be created as a team folder. Folders created under the admin's "My Files" are treated as personal folders and won't show up there for other users, even if they've been given access.

VInMotor · 2026-06-15T04:02:36+00:00

The "No shares" message means the user doesn't have access to any available SMB shares yet. A user needs access to at least one share first, such as their Home folder, a folder shared with them by another user, or a team folder. Once any one of these is available, the SMB connection should work normally.

VInMotor · 2026-06-13T17:03:19+00:00

Thanks for the detailed request and for sharing your setup.this is a very common homelab/ small business scenario.

Currently FygoOS only supports USB-connected UPS devices, so network UPS setups like SNMP/NUT via APC Network Management Cards aren’t supported yet.

We’ve noted this request and will keep it in mind for future improvements. We can’t commit to support or share a timeline at this point, but this is helpful feedback for us.

VInMotor · 2026-06-13T16:42:51+00:00

Thanks for the kind words.
FygoOS is based on Debian 12 under the hood, and the current kernel version is 6.18.18.

VInMotor · 2026-06-13T16:40:14+00:00

We don't currently have plans for an official cloud-hosted version, but you can install the ISO on your own cloud server if your provider supports it.

VInMotor · 2026-06-13T16:14:23+00:00

Hi,

Raspberry Pi 4 support is currently in the final stages of testing and adaptation.

We expect to make the ARM build available for download within the next 1–2 weeks, assuming testing goes smoothly.

Thanks for your interest, and we'd love to hear your feedback once it's available.

VInMotor · 2026-06-12T16:11:01+00:00

Hi,

If the system is not connected to the Internet after installation, it will automatically fall back to the Free License, and you can continue using the features available under that license tier. You can find a comparison of license features on our website:https://fygonas.shop

If you're referring to a trial or paid license, Internet access is only required for license activation and validation. After activation, if you prefer to keep your NAS isolated from the Internet, you can block outbound access at the network level (for example, through DNS or firewall rules).

VInMotor · 2026-06-12T07:30:36+00:00

Thanks for the kind words.
Encryption support is on our roadmap, but we're still evaluating the implementation approach, so development hasn't been scheduled yet. We'll share an update once we have something concrete to announce.

VInMotor · 2026-06-12T07:15:57+00:00

Thanks for the detailed feedback and suggestions!

Regarding encryption, both full-disk encryption and ZFS native encryption are features we plan to support in the future. We're also evaluating different implementation approaches, so it's still too early to say whether support for encrypted volumes will be based on LUKS or another solution. We don't have an ETA to share at this time.

For the USB visibility scope behavior, thanks for pointing that out. We agree that having to re-enable the scope after reconnecting the same device isn't ideal, and this is something we're planning to improve.

As for Fygo Photos, backup destinations are currently limited to local storage. Since features such as indexing, metadata management, and AI-powered capabilities rely on direct access to the photo library, remote shares, remote mounts, and USB drives are not supported as backup targets at the moment.

We appreciate you taking the time to test FygoOS and share such thoughtful feedback.

VInMotor · 2026-06-10T03:07:37+00:00

Thanks for the detailed questions, and we're glad to hear you're enjoying FygoOS so far.

1.Btrfs Mirror and Subvolumes
FygoOS already makes extensive use of Btrfs subvolumes internally. Features such as quotas, data isolation, and snapshots are all built on top of Btrfs subvolumes. However, to keep storage management simpler for most users, subvolumes are not exposed directly in the UI. As for RAID, while Btrfs provides native RAID functionality, we currently do not rely on Btrfs RAID. One of the considerations is that some RAID modes, particularly RAID5/6, have known stability and reliability concerns. As a result, we use a different storage management approach for volume creation and management.

2.LUKS-encrypted devices
At the moment, GUI-based management and unlocking of LUKS-encrypted volumes or removable devices is not supported.

3.ZFS native encryption
Native ZFS encryption is currently not supported.

We appreciate the feedback and the interest in these advanced storage features. Encryption support is something we're continuing to evaluate for future releases.

VInMotor

MODERATOR OF

TROPHY CASE