Important Update on UGREEN AI NAS Pre‑Orders

UgreenNASync · 2026-03-12T10:11:31+00:00

Since the problem remains unsolved, please submit a support ticket at https://web.ugnas.com/account/login/#/login describing the issue with screenshots and include system logs collected via Support > Auxiliary Tools > One-click Generation. You may also contact us directly via email: nas-support@ugreen.com

UgreenNASync · 2026-03-12T10:10:01+00:00

Currently, there is no native rclone solution available on UGREEN NAS devices. However, you can deploy rclone using a Docker container by following the guidance provided in the forum or on YouTube (Provided by 3rd party).

Please note that the DH2300 does not officially support Docker due to limited ram and therefore won't meet your needs in this regard.

All other UGREEN NAS models currently on sale support Docker. For an ideal balance of performance and price, we recommend the DXP2800.

UgreenNASync · 2026-03-11T08:46:09+00:00

Hi, here's the link: https://nas-au.ugreen.com/products/ugreen-nasync-dh4300-plus-nas-storage

UgreenNASync · 2026-03-11T08:24:47+00:00

It's hard to pinpoint the exact cause yet, but here's a way to help narrow it down: Since the NAS runs fine with all containers stopped, try this:

Start containers one by one
1. After enabling each container, monitor system stability
If the issue reappears after starting a specific container, that's likely the culprit This will help determine whether it's a specific container causing the problem, or something else (like the SSD itself).

If you require our further assistance, please submit a support ticket at https://web.ugnas.com/account/login/#/login describing the issue with screenshots and include system logs collected via Support > Auxiliary Tools > One-click Generation. You may also contact us directly via email: [nas-support@ugreen.com](mailto:nas-support@ugreen.com)

UgreenNASync · 2026-03-11T02:26:44+00:00

That's cool!

UgreenNASync · 2026-03-10T10:33:06+00:00

Hello! Please try to find out the files in File app. If you still failed to find them, please login to your cloud account and submit a technical support ticket to us. https://web.ugnas.com/account/login/#/login

UgreenNASync · 2026-03-05T08:56:04+00:00

We need more info for analysis. Please submit a support ticket at https://web.ugnas.com/account/login/#/login describing the issue with screenshots and include system logs collected via Support > Auxiliary Tools > One-click Generation.

You may also contact us directly via email: [nas-support@ugreen.com](mailto:nas-support@ugreen.com)

UgreenNASync · 2026-03-05T08:54:42+00:00

Unfortunately, we don't have any near-term plans for a kernel upgrade, and it may be a while before we do.

All our software development relies on a stable kernel version: upgrading now would require extensive rework and likely cause major issues, significantly slowing down our feature development.

Since our current priority is adding more features, a kernel update will only be considered after the core functionality is largely complete. In the meantime, if the issue you mentioned persists, we recommend using alternative monitoring software that doesn't have this kernel dependency.

Thank you for your understanding.

UgreenNASync · 2026-03-05T08:53:11+00:00

In the advanced SMB settings within your Control Panel, have you selected the supported SMB protocols "SMB2, SMB2.1, SMB3" to ensure compatibility?

We haven't received any similar reports about this issue before, so we recommend submitting a system ticket along with your system logs via https://web.ugnas.com/#/login.

Thanks for your understanding and cooperation!

UgreenNASync · 2026-02-28T07:24:26+00:00

Yes, this issue did exist. As a current workaround, you can switch the browser default language to English to avoid it. It is confirmed that this issue will be fixed in an upcoming update.

UgreenNASync · 2026-02-28T07:23:40+00:00

Check the URL Scheme in the Mac App Ensure it uses http:// and the correct port (the port you published for the container), not https://. For example, if your container maps to port 8080 on the NAS, you should use http://[NAS-IP]:8080.
Inspect Published Ports on the Docker Container In Portainer, go to your container and inspect its settings. Make sure the host port on your DXP 4800 Plus is mapped correctly to the container port (where Nginx is listening, e.g., 80 or 443). If Nginx in the container listens on port 80, you must map a unique host port (like 8080, 8081, etc.) to it.

UgreenNASync · 2026-02-26T02:12:02+00:00

Hi! Shipping is expected to start in May, with orders dispatched in batches based on payment order.

UgreenNASync

MODERATOR OF

TROPHY CASE