# NAS down, Support Portal not helpful

**URL:** <https://community.qnap.com/t/nas-down-support-portal-not-helpful/7532>\
**Category:** General\
**Tags:** support\
**Created:** [November 11, 2026, 5:38pm UTC](https://community.qnap.com/t/nas-down-support-portal-not-helpful/7532 "2026-11-11T17:38:28Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![RalKed](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@RalKed](https://community.qnap.com/u/RalKed)\
**Post date:** [November 11, 2026, 5:38pm UTC](https://community.qnap.com/t/nas-down-support-portal-not-helpful/7532/1 "2026-11-11T17:38:28Z")

</div>

Hi, my nas is down for some days and is not reachable via LAN, only by console. I opended a ticket at QNAP support portal, but got no help for days. First they did not read my ticket and asked nonsens questions. Then they asked for several tests. They got the answers but nobody cares.

Are there other ways to get help? I´m willing to pay a little money but I need my storage and my docker apps back!!!

---

<div class="post-metadata">

**Author:** ![dolbyman](https://community.qnap.com/user_avatar/community.qnap.com/dolbyman/32/136_2.png) [@dolbyman](https://community.qnap.com/u/dolbyman)\
**Post date:** [November 11, 2026, 6:36pm UTC](https://community.qnap.com/t/nas-down-support-portal-not-helpful/7532/2 "2026-11-11T18:36:46Z")

</div>

NAS model, setup (backups?) and exact symptoms would be helpful to start with

---

<div class="post-metadata">

**Author:** ![RalKed](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@RalKed](https://community.qnap.com/u/RalKed)\
**Post date:** [November 11, 2026, 7:12pm UTC](https://community.qnap.com/t/nas-down-support-portal-not-helpful/7532/3 "2026-11-11T19:12:55Z")

</div>

—English Translation added by Dolbyman—  
It’s a TVS-675.

Incoming TCP connections from the LAN are failing on all ports (8080, 443, 445, 22) for both wired and wireless clients, including from Home Assistant (wired). Pinging works. A Pi-hole container running on its own IP address exhibits the same behavior. Outbound TCP from the NAS (e.g., `curl` to 10.0.0.92:8123) works, and a local `curl` to 127.0.0.1:8080 or 10.0.0.53:8080 returns “200 OK.” After booting, the HDMI display indicates that HD Station is not installed. Access is possible only via the local console (HDMI + USB keyboard, ALT+F2) logged in as `admin`.

Findings:

- Services are listening (`netstat -tln` shows: 0.0.0.0:22, :::8080, :::443, :::445, :::5001); the `Recv-Q` for all listening sockets is 0.
- SYN packets from 10.0.0.141 appear in `/proc/net/nf_conntrack` (as `SYN_SENT`, `[UNREPLIED]`), but `netstat` never shows a state of `SYN_RECV` or `ESTABLISHED`.
- `/proc/net/netstat`: `ListenDrops` is increasing (5606 → 6589 → 6632; it rose by 43 during a single browser request); `ListenOverflows` is 0.
- `iptables` INPUT: Policy is set to `ACCEPT`; the only rule is a `DROP` for ICMP type 13 (with 0 hits). The `mangle` and `nat` tables show nothing unusual; `rp_filter` is set to 0; routing and `ip rule` configurations appear normal. - TCP InCsumErrors = 0, standard offloading, no discards at the IP layer.
- tcp\_syncookies = 1, somaxconn = 4096, tcp\_max\_syn\_backlog = 2048;  
sufficient RAM available (approx. 25 GB free/cached), no OOM (Out of Memory) events, no signs of a SYN flood in `dmesg`.
- Stopped Container Station and ran `network.sh restart`: no change.  
Container Station was also stopped and restarted for a data backup: the issue persists.
- Restarted switch and router: no change.
- RAID arrays (md1 RAID5 4/4, md2 RAID1 2/2, md3 1/1) and all volumes are healthy and mounted; no `fsck` processes are running; system load \< 1.

Data status: Important data has been backed up to an external USB drive.

---

<div class="post-metadata">

**Author:** ![dolbyman](https://community.qnap.com/user_avatar/community.qnap.com/dolbyman/32/136_2.png) [@dolbyman](https://community.qnap.com/u/dolbyman)\
**Post date:** [November 11, 2026, 7:56pm UTC](https://community.qnap.com/t/nas-down-support-portal-not-helpful/7532/4 "2026-11-11T19:56:55Z")

</div>

And you tried to do a 3 second reset?

---

<div class="post-metadata">

**Author:** ![NA9D](https://community.qnap.com/user_avatar/community.qnap.com/na9d/32/1278_2.png) [@NA9D](https://community.qnap.com/u/NA9D)\
**Post date:** [November 11, 2026, 8:38pm UTC](https://community.qnap.com/t/nas-down-support-portal-not-helpful/7532/5 "2026-11-11T20:38:42Z")

</div>

Sounds like an IP address issue. See the pinned post at the top of the forum.

---

<div class="post-metadata">

**Author:** ![RalKed](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@RalKed](https://community.qnap.com/u/RalKed)\
**Post date:** [November 11, 2026, 9:10pm UTC](https://community.qnap.com/t/nas-down-support-portal-not-helpful/7532/6 "2026-11-11T21:10:02Z")

</div>

Yes, I did. Nas can be pinged but does not answer incoming HTTP, SSH, … and other TCP communications.

---

<div class="post-metadata">

**Author:** ![RalKed](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@RalKed](https://community.qnap.com/u/RalKed)\
**Post date:** [November 11, 2026, 9:15pm UTC](https://community.qnap.com/t/nas-down-support-portal-not-helpful/7532/7 "2026-11-11T21:15:01Z")

</div>

Hi, which post do you mean?

---

<div class="post-metadata">

**Author:** ![OneCD](https://community.qnap.com/user_avatar/community.qnap.com/onecd/32/156_2.png) [@OneCD](https://community.qnap.com/u/OneCD)\
**Post date:** [November 11, 2026, 9:20pm UTC](https://community.qnap.com/t/nas-down-support-portal-not-helpful/7532/8 "2026-11-11T21:20:38Z")

</div>

> [@NA9D](#):
>
> See the pinned post at the top of the forum.

Important to note: this forum allows per-user unpinning of forum topics. What you see as pinned may not be pinned for another user. 😉

---

<div class="post-metadata">

**Author:** ![NA9D](https://community.qnap.com/user_avatar/community.qnap.com/na9d/32/1278_2.png) [@NA9D](https://community.qnap.com/u/NA9D)\
**Post date:** [November 11, 2026, 10:38pm UTC](https://community.qnap.com/t/nas-down-support-portal-not-helpful/7532/9 "2026-11-11T22:38:59Z")

</div>

I thought it was globally pinned. That was the point…

---

<div class="post-metadata">

**Author:** ![NA9D](https://community.qnap.com/user_avatar/community.qnap.com/na9d/32/1278_2.png) [@NA9D](https://community.qnap.com/u/NA9D)\
**Post date:** [November 11, 2026, 10:40pm UTC](https://community.qnap.com/t/nas-down-support-portal-not-helpful/7532/10 "2026-11-11T22:40:01Z")

</div>

> [@RalKed](#):
>
> Hi, which post do you mean?

> [@HELP! - I've lost access to the NAS and my password does not work! - How to solve this](https://community.qnap.com/t/help-ive-lost-access-to-the-nas-and-my-password-does-not-work-how-to-solve-this/6259/):
>
> We see a large number of requests on the forum here for people who are suddenly locked out of their NAS for one reason or another. Their password no longer works. This post is to provide a guide for this so people are not as stuck. If your password has been defaulted for whatever reason (3 second reset, a glitch, etc) here is what you need to know courtesy of QNAP: 1.) The default password can vary depending on your NAS model and firmware version. Please see this app note for information on…

---

<div class="post-metadata">

**Author:** ![OneCD](https://community.qnap.com/user_avatar/community.qnap.com/onecd/32/156_2.png) [@OneCD](https://community.qnap.com/u/OneCD)\
**Post date:** [November 11, 2026, 10:55pm UTC](https://community.qnap.com/t/nas-down-support-portal-not-helpful/7532/11 "2026-11-11T22:55:53Z")

</div>

> [@NA9D](#):
>
> I thought it was globally pinned. That was the point…

Globally pinned means it appears in every sub-forum. But, it can be unpinned by each user when they decide they’ve seen it enough times. 😉

---

<div class="post-metadata">

**Author:** ![NA9D](https://community.qnap.com/user_avatar/community.qnap.com/na9d/32/1278_2.png) [@NA9D](https://community.qnap.com/u/NA9D)\
**Post date:** [November 11, 2026, 11:09pm UTC](https://community.qnap.com/t/nas-down-support-portal-not-helpful/7532/12 "2026-11-11T23:09:47Z")

</div>

Never knew. Kinda defeats the purpose don’t you think?

---

<div class="post-metadata">

**Author:** ![OneCD](https://community.qnap.com/user_avatar/community.qnap.com/onecd/32/156_2.png) [@OneCD](https://community.qnap.com/u/OneCD)\
**Post date:** [November 11, 2026, 11:26pm UTC](https://community.qnap.com/t/nas-down-support-portal-not-helpful/7532/13 "2026-11-11T23:26:34Z")

</div>

> [@NA9D](#):
>
> Kinda defeats the purpose don’t you think?

Kinda.

But, it also allows for user customisation.

Personally, I’d rather acknowledge a globally pinned topic once, then unpin it so I don’t have to see it again. If I think I’ll need it, I’ll save it as a bookmark, or just search the forum for it. I don’t need it thrown in my face every time I visit. 😁
