# Wrong config - No match in Diagnostics

**URL:** <https://vaultwarden.discourse.group/t/wrong-config-no-match-in-diagnostics/1651>\
**Category:** Uncategorized\
**Created:** [May 23, 2022, 9:11am UTC](https://vaultwarden.discourse.group/t/wrong-config-no-match-in-diagnostics/1651 "2022-05-23T09:11:29Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![OlliF\_69](https://avatars.discourse-cdn.com/v4/letter/o/77aa72/32.png) [@OlliF\_69](https://vaultwarden.discourse.group/u/OlliF_69)\
**Post date:** [May 23, 2022, 9:11am UTC](https://vaultwarden.discourse.group/t/wrong-config-no-match-in-diagnostics/1651/1 "2022-05-23T09:11:29Z")

</div>

since a few weeks I can’t get connection with my vaultwarden server.  
What’s going wrong?

My Config: Synology NAS with docker (vaultwarden).  
Fritzbox router with firewall config for port forwarding  
latest SW on NAS.  
No connection possible via safari (MACOS), firefox or by my iPhone.

 ![vaultwarden_fred](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/5ab0d3b702a6f555242f6a8c5244cdb0941c9859.png)

---

<div class="post-metadata">

**Author:** ![ramsesderzweite](https://avatars.discourse-cdn.com/v4/letter/r/c77e96/32.png) [@ramsesderzweite](https://vaultwarden.discourse.group/u/ramsesderzweite)\
**Post date:** [May 24, 2022, 12:10pm UTC](https://vaultwarden.discourse.group/t/wrong-config-no-match-in-diagnostics/1651/2 "2022-05-24T12:10:22Z")

</div>

Use the [https://xxxxx.synology.me/admin/diagnostics](https://xxxxx.synology.me/admin/diagnostics) in your browser to connect to Vaultwarden. Don’t use the internal IP and Port 5151 to get there.

---

<div class="post-metadata">

**Author:** ![OlliF\_69](https://avatars.discourse-cdn.com/v4/letter/o/77aa72/32.png) [@OlliF\_69](https://vaultwarden.discourse.group/u/OlliF_69)\
**Post date:** [May 24, 2022, 4:37pm UTC](https://vaultwarden.discourse.group/t/wrong-config-no-match-in-diagnostics/1651/3 "2022-05-24T16:37:33Z")

</div>

Ups.hmm - to be honest - that doesn’t work. It also doesn’t work with the IP address and https at the start. Currently only HTTP runs.  
Oh my… what have I done wrong? I thought my DNS is configured correctly.  
– so was blödes –  
Thanks for your tip, but what can I do next? what can I check?  
 ![Bildschirmfoto 2022-05-24 um 18.34.11](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/86b48469b29d5d9bc359c8abd65b0ec724b84ec9.png)

---

<div class="post-metadata">

**Author:** ![OlliF\_69](https://avatars.discourse-cdn.com/v4/letter/o/77aa72/32.png) [@OlliF\_69](https://vaultwarden.discourse.group/u/OlliF_69)\
**Post date:** [May 24, 2022, 4:38pm UTC](https://vaultwarden.discourse.group/t/wrong-config-no-match-in-diagnostics/1651/4 "2022-05-24T16:38:20Z")

</div>

![Bildschirmfoto 2022-05-24 um 18.35.40](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/cdeb8174a69154054b74201f5169234f2aba5262.png)

---

<div class="post-metadata">

**Author:** ![OlliF\_69](https://avatars.discourse-cdn.com/v4/letter/o/77aa72/32.png) [@OlliF\_69](https://vaultwarden.discourse.group/u/OlliF_69)\
**Post date:** [May 26, 2022, 5:47pm UTC](https://vaultwarden.discourse.group/t/wrong-config-no-match-in-diagnostics/1651/5 "2022-05-26T17:47:00Z")

</div>

My problem is solved. It was the firewall inside my NAS. Now all is working fine again.  
Thanks for support.

---

<div class="post-metadata">

**Author:** ![hamblingreg52](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/hamblingreg52/32/303_2.png) [@hamblingreg52](https://vaultwarden.discourse.group/u/hamblingreg52)\
**Post date:** [May 27, 2022, 6:44am UTC](https://vaultwarden.discourse.group/t/wrong-config-no-match-in-diagnostics/1651/6 "2022-05-27T06:44:53Z")

</div>

I have noted it down. Will keep in my mind next time.