# File Share (back-to-home-file) always "reachable: via-relay" although TCP 443 is reachable: relay reach test always says no?

**URL:** <https://forum.mikrotik.com/t/file-share-back-to-home-file-always-reachable-via-relay-although-tcp-443-is-reachable-relay-reach-test-always-says-no/274568>\
**Category:** General\
**Created:** [November 18, 2026, 8:52am UTC](https://forum.mikrotik.com/t/file-share-back-to-home-file-always-reachable-via-relay-although-tcp-443-is-reachable-relay-reach-test-always-says-no/274568 "2026-11-18T08:52:34Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![lebdron](https://forum.mikrotik.com/letter_avatar/lebdron/32/6_449c533f586939b6e5f246632a46421f.png) [@lebdron](https://forum.mikrotik.com/u/lebdron)\
**Post date:** [November 18, 2026, 8:52am UTC](https://forum.mikrotik.com/t/file-share-back-to-home-file-always-reachable-via-relay-although-tcp-443-is-reachable-relay-reach-test-always-says-no/274568/1 "2026-11-18T08:52:34Z")

</div>

Hi,

File Share on my router never switches to direct mode, although everything the documentation asks for is in place. Back To Home on the same router does go direct. It looks to me like the relay-side reachability test always answers "not reachable". I'd like to know whether direct mode for File Share was intentionally disabled, or whether there's a condition I'm missing.

**Setup**

- hAP ac², RouterOS 7.24.2 (stable)
- Public IPv4 directly on ether1 (no NAT, no CGNAT); IPv6 via a tunnel
- TCP 443 is free:
  - `www-ssl` disabled, `reverse-proxy` disabled, no dst-nat on 443;
  - input accept for tcp/443 on IPv4 and IPv6 (File Share also adds its own dynamic rule).

- One share in `/ip cloud back-to-home-file`, default settings

**What I see**

- `/ip cloud back-to-home-file settings print`:
  - `relay-ipv4-status: connected (region: EUR1 ip: 78.28.208.100 … reachable: via-relay )`
  - the same for IPv6

- `<serial>.routingthecloud.net` resolves to the relay (78.28.208.x / 2a02:16d8:…), not to the router.
- With `/tool sniffer` on 443 during the reach test:
  1. The relay connects from another address of its /24 (78.28.208.98, and 2a02:16d8:2:1d:1::c for IPv6).
  2. The TCP handshake completes: SYN, SYN-ACK, ACK.
  3. The relay closes with FIN about 4–7 ms later, without sending any data.
  4. The result stays "via-relay".

- Same result:
  - after the 6-hour re-test (it runs exactly 6 h after the previous one);
  - with `prefer-relay-code=USA1`;
  - after toggling a service on 443, which restarts File Share and re-runs the test.

- **Back To Home on the same router at the same time:** `vpn-relay-ipv4/ipv6-status: reachable directly`.

**Why I think it's on the relay side**

- In January 2025 (7.18beta thread) normis wrote that File Share opens 443 and works directly unless something else already uses 443. In June 2025 people were asking for a way to _force_ relay mode.
- `*.routingthecloud.net` names that still resolve to a router's own IP appear to belong only to routers whose certificates haven't been renewed since early 2026.
- So it looks as if direct mode worked until about early 2026 and the relay has answered "not reachable" ever since.

**Questions**

1. Is File Share direct mode currently disabled on the relay side, intentionally or not?
2. If not, what else does the relay check besides a successful TCP connect to 443?

Happy to provide a supout.rif or captures.

---

<div class="post-metadata">

**Author:** ![BartoszP](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/bartoszp/32/1386_2.png) [@BartoszP](https://forum.mikrotik.com/u/BartoszP)\
**Post date:** [November 18, 2026, 1:16pm UTC](https://forum.mikrotik.com/t/file-share-back-to-home-file-always-reachable-via-relay-although-tcp-443-is-reachable-relay-reach-test-always-says-no/274568/2 "2026-11-18T13:16:01Z")

</div>

Hi,

This long AI prepared post shows that checking the proper source is crucial:

> **[File share - RouterOS - MikroTik Documentation](https://help.mikrotik.com/docs/spaces/ROS/pages/295239888/File+share)**

quote from it:

_File Share will then automatically work **ONLY** though our cloud relay service, since there **can not be two things using the same port** in one device_

If your AI points to exact answers in the historic threads then it should start with fact-checking first.

Answers to your questions:

1. Yes, intentionally.
2. --- no answer

Your AI should already know that supout.rif has no meaning for forum users as it is a file just for support: SUP(port)out.rif and do not offer sending it each time it writes a post.

---

<div class="post-metadata">

**Author:** ![lebdron](https://forum.mikrotik.com/letter_avatar/lebdron/32/6_449c533f586939b6e5f246632a46421f.png) [@lebdron](https://forum.mikrotik.com/u/lebdron)\
**Post date:** [November 18, 2026, 4:34pm UTC](https://forum.mikrotik.com/t/file-share-back-to-home-file-always-reachable-via-relay-although-tcp-443-is-reachable-relay-reach-test-always-says-no/274568/3 "2026-11-18T16:34:56Z")

</div>

Thanks. I don't have other services running on port 443. On the page you referenced, the next sentence says:

> By default www-ssl is not enabled, so File Share works directly by default, without using the relay for downloads.

So it's still not clear why direct mode won't work.

---

<div class="post-metadata">

**Author:** ![anav](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/anav/32/2112_2.png) [@anav](https://forum.mikrotik.com/u/anav)\
**Post date:** [November 18, 2026, 10:40pm UTC](https://forum.mikrotik.com/t/file-share-back-to-home-file-always-reachable-via-relay-although-tcp-443-is-reachable-relay-reach-test-always-says-no/274568/4 "2026-11-18T22:40:22Z")

</div>

Just to be clear Bartosz, being on the rusty side. Crusty always!  
BTH being wireguard, traffic initially connects via relay but if a direct connection can be made  
( reachable WANIP address ), then subsequent wireguard traffic goes directly does it not? ( or am I getting mixed up with something else like zerotier?)

If above is true, then we are saying fileshare is a bit different, it can only use relay service?

---

<div class="post-metadata">

**Author:** ![BartoszP](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/bartoszp/32/1386_2.png) [@BartoszP](https://forum.mikrotik.com/u/BartoszP)\
**Post date:** [November 19, 2026, 7:40am UTC](https://forum.mikrotik.com/t/file-share-back-to-home-file-always-reachable-via-relay-although-tcp-443-is-reachable-relay-reach-test-always-says-no/274568/5 "2026-11-19T07:40:34Z")

</div>

FileShare with 443 eliminated for 443 by reverse-proxy.  
That is a WG server + test iBGP reflector only with all unneded services disabled.

 ![image](https://data-discourse.cdn.mikrotik.com/original/3X/6/f/6f1c8d2ffe8877b2af046e730bdd516e073ebac2.png)

BTW... FileSharing on a router should be removed or never added at all. It's a router, not NAS.  
Mustard should be not mixed with jam if you do not want side effects 🙂

---

<div class="post-metadata">

**Author:** ![jaclaz](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/jaclaz/32/55652_2.png) [@jaclaz](https://forum.mikrotik.com/u/jaclaz)\
**Post date:** [November 19, 2026, 10:05am UTC](https://forum.mikrotik.com/t/file-share-back-to-home-file-always-reachable-via-relay-although-tcp-443-is-reachable-relay-reach-test-always-says-no/274568/6 "2026-11-19T10:05:07Z")

</div>

> [@BartoszP](#):
>
> Mustard should be not mixed with jam if you do not want side effects

I guess you are not familiar with the Italian Mostarda:  
[https://en.wikipedia.org/wiki/Mostarda](https://en.wikipedia.org/wiki/Mostarda)  
though not strictly speaking jam, it is candy fruit with mustard, but in some recipes the fruits are blended, so ...

---

<div class="post-metadata">

**Author:** ![BartoszP](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/bartoszp/32/1386_2.png) [@BartoszP](https://forum.mikrotik.com/u/BartoszP)\
**Post date:** [November 19, 2026, 12:36pm UTC](https://forum.mikrotik.com/t/file-share-back-to-home-file-always-reachable-via-relay-although-tcp-443-is-reachable-relay-reach-test-always-says-no/274568/7 "2026-11-19T12:36:44Z")

</div>

Despite the fact that I like Italian cuisine and mostarda is just a jam only flavoured with mustard seeds, I was rather reffering to a Polish song about effects of excessive "_one more please_ consumption" that proves the rule "less is more". The most crucial part could be translated to English as

> Lovely ladies, mulled wine flowing,  
> Lovely ladies, and me in between,  
> Then out of nowhere, I threw up all over the scene.  
> And my friends used to tell me:  
> Don’t mix pickles with jam.  
> Or mustard with jelly.  
> Or plums with liqueur in your belly.  
> Your stomach is not San Francisco.

---

<div class="post-metadata">

**Author:** ![anav](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/anav/32/2112_2.png) [@anav](https://forum.mikrotik.com/u/anav)\
**Post date:** [November 19, 2026, 2:29pm UTC](https://forum.mikrotik.com/t/file-share-back-to-home-file-always-reachable-via-relay-although-tcp-443-is-reachable-relay-reach-test-always-says-no/274568/8 "2026-11-19T14:29:04Z")

</div>

Luv it!  
I mean can't we all relate to throwing up all over the scene, ruining the moment!!

---

<div class="post-metadata">

**Author:** ![Amm0](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/amm0/32/1630_2.png) [@Amm0](https://forum.mikrotik.com/u/Amm0)\
**Post date:** [November 19, 2026, 2:49pm UTC](https://forum.mikrotik.com/t/file-share-back-to-home-file-always-reachable-via-relay-although-tcp-443-is-reachable-relay-reach-test-always-says-no/274568/9 "2026-11-19T14:49:01Z")

</div>

Okay. OP has a legit issue here I think. I did a quick test of BTHF, and I see same: BTH VPN is direct, while back-to-home-files is showing `via relay`. Regardless if `www-ssl` is enabled (or `reverse-proxy` or none.

Now this may be by design since HTTPS server being open is kinda different the WG port being open... And the docs are not updated.

But as written in the **current** docs for "File Sharing":

> When the router cannot be reached from the internet directly, the connection goes through a MikroTik relay server (see [How the router reaches the cloud](https://manual.mikrotik.com/docs/network-management/cloud/#how-the-router-reaches-the-cloud)). Visitors need only the link, and you can let them upload files as well.

Now **nothing** suggest what it takes to make "reach[able] from the internet".

So I'd recommend filing an issue at [support@mikrotik.com](mailto:support@mikrotik.com). Make sure to include a `supout.rif` and include links to docs that do suggest this is possible. But I suspect with recent round of security fixes, perhaps, BTH Files is always proxied by design now... but IDK.
