This Update bricked my TS-233. noticed that it dose not bind to its static IP any more and loops to 0.0.0.0 (as it shows on My router)
edit, tried a lot of methods but no luck.
Still the NAS isn’t accessible via LAN, only via VPN / Tailscale - which is very weird.
Tried - downgrading to previous working version of qts, tried resetting network settings via CLI, etc…
Please help,
Hmm. Well, are you seeing this in Qfinder? Does the NAS show up?
I deleted the other two posts in the firmware topic, @itzq either open a new topic or reply to an existing one,doing both just adds confusion.
No wonder I was confused! I swore I replied to the post!
I saw both and had dejavu, hence the confusion
Hi @itzq ,
Thank you very much for reporting this issue and for sharing the troubleshooting steps you have already tried.
To help us further understand the current network status of your TS-233, could you please provide a screenshot of Qfinder Pro while your computer is connected to the same local network as the NAS? This will help us confirm whether the NAS can be detected and what IP address or status is currently displayed.
In addition, may we kindly ask you to try the following checks:
This information will help us further narrow down whether the issue may be related to the NAS network configuration or the local network environment.
Thank you for your patience and cooperation.
Thank you for your response.
I will provide a Qfinder Pro screenshot when I get back home.
In the meantime, here is some additional information:
My TS-233 only has a single physical LAN port, so I cannot test another NAS LAN port.
I have already tried different router ports and different Ethernet cables with the same result.
There have been no changes to my network environment before this issue started. The router, DHCP settings, IP range, switch configuration, VLANs, and firewall configuration remained unchanged.
The only change that immediately preceded the problem was updating the NAS firmware.
The behavior is very consistent:
After boot, the NAS receives a valid DHCP address (192.168.1.111) and is fully accessible from the local network for approximately 1–2 minutes.
After that, it disappears completely from the LAN.
However, it remains fully accessible through Tailscale, including SSH access.
The network interface (eth0) remains UP, retains its IP address, and the link stays established at 1 Gbps.
I also performed a 3-second reset, which successfully restored the default network configuration and obtained a fresh DHCP lease, but the exact same behavior occurred again after about 2 minutes.
I have also collected SSH diagnostics showing that the interface itself remains up while LAN connectivity is lost. If helpful, I can provide those logs as well.
Please let me know what additional diagnostic information you would like me to collect.
It’s very important to note that nothing was wrong till I’ve updated the firmware from 5.2.9.3451(20260327) to 5.2.9.3499(20260514).
Since then I’ve tried a lot of things to revert back without luck
It isn’t really “bricked”… 
if you are able to do everything you describe.
Sounds like the networking drops off or is blocked by firewall or resource issues. Or something is triggering one of the security settings (access list).
I know QNAP is working to help you, but I’m unclear on what happened when you rolled back the firmware or if you were successful in loading it.
I would go back to a basic startup. Disable all apps, particularly the firewall. See if it is findable after the 2 minute timeout. Then start the apps 1 at a time.
Fair point, it’s not completely bricked since I still have access through Tailscale.
That said, from a practical standpoint it’s unusable on the local network.
I’ve already ruled out the obvious causes:
Disabled QuFirewall completely.
Performed a 3-second network reset.
Rolled back to previous firmware versions.
Verified that the interface stays UP, keeps its IP address, and the link remains at 1 Gbps.
The NAS is reachable on the LAN for about 1–2 minutes after boot, then disappears every single time while Tailscale continues to work normally.
If this were simply a firewall rule or access list, I wouldn’t expect the behavior to survive resets and firmware rollback in exactly the same way.
If you have a specific setting or log that you think points to a firewall or security feature, I’m happy to check it.
Agreed, I would “expect” it to persist either, but if it is indeed due to a firmware issue as you seem to feel it is, then rolling back should also have corrected it, so the real issue may lie somewhere else.
Hopefully support will provide you some answers.
Depending on the size and configuration of your drives, and your backup situation, you could resort to something more drastic such as a long reset or configuring from scratch.
Another option to run out some other issues could be to boot up with the drives removed and see if it stays “alive” on your network.
If the connection is possible through Tailscale, then nothing is wrong with the NAS. What’s wrong is something on the local network. There is either a setting wrong or something.
When you say the NAS disappears - do you mean from Qfinder? That’s not always surprising. When the NAS “disappears” can you SSH into it? Can you ping it?
The network connection staying “up” meaning the link stays established, etc. is at the physical layer - layer 1. Question is which layer is failing. How do you know it retains its IP address?
Also, you mention VLANs. This appears to be a classic case of the NAS getting on the wrong VLAN if you cannot access it.
It is definitely a networking problem…
Update:
I found the root cause of the issue.
The problem was caused by the installed Tailscale application.
When I stopped the Tailscale service, the NAS immediately became reachable again over the local LAN and everything worked normally.
As soon as I started the Tailscale service again, the NAS disappeared from the local network with the exact same behavior as before, while it remained accessible through Tailscale.
To test this, I removed the existing Tailscale installation and installed the latest version from the MyQNAP repository. After upgrading to the newer version, the problem disappeared completely. The NAS is now fully accessible over both the local LAN and Tailscale, even after reboots.
As an additional suggestion, if someone from QNAP is reading this, I would recommend updating the Tailscale package available through the official QNAP App Center. The version currently provided there appears to be several years out of date, which can lead to compatibility issues and makes troubleshooting much more difficult.
Good find! Glad you were able to get things working!