Self-hosted Bitwarden not working after GH2.0 f/w upgrade to 3.11.6.1

[Wayne_]

Since the Giga Hub 2.0 firmware upgrade to 3.11.6.1, I'm unable to access self-hosted services like Bitwarden password manager which I have otherwise run fine for 4+ years on my Bell Fibe service. I run Bitwarden on my Synology NAS. I usually access Bitwarden via desktop/browser apps, but despite not changing any of the firewall nor port forwarding settings, I'm just unable to login to Bitwarden from within my Bell WAN/LAN. I've since played endlessly with various permutations of NAS firewall and GH2.0 port forwarding settings, but nothing has worked.

If I'm hotspotting from my Bell mobility phone (i.e. off from Bell Fibe WAN/LAN), or I'm using any other Internet connection aside that which my NAS is using, then I'm able to access Bitwarden just fine.

It's the same experience for other Synology NAS applications like DS Notes, DS Photos, etc.

I'm speculating that Bell changed something to do with NAT?

Has anyone come by something similar and resolved this problem?

Thanks in advance for your help!

[Vanadiel]

There's an issue with the latest firmware on the home hub.

No news from Bell on a possible fix for this issue, or if it's intended changes.

[Wayne_]

Thanks for that update.

@BellPatricia any updates? Many of us are still waiting for a fix to the bugs introduced in the latest Gigahub 2.0 firmware related to NAT loopback and other issues: https://forum.bell.ca/t5/internet/bug-critique-nat-loopback-et-sessions-acs-giga-hub-2-0-firmware/td...

[BellNick]

Hi @Wayne_ 
Thank you for your post .
Are you able to share how exactly it is that you access your self-hosted Bitwarden service? Is this something like a IP you type into your Bitwarden client or do you access it via hostname, or another way?
Looking forward to hearing back.

[Wayne_]

Thanks for responding @BellNick !

To be clear, the problem is not just Bitwarden but also other Synology apps like Photos, Notes, etc.

But to answer your direct question: I access bitwarden via desktop apps and browser extensions using a {server name}.synology.me:{port} address. This doesn’t work when I’m on the Bell WAN/LAN. It works fine as expected when I’m accessing these self-hosted services from outside the Bell WAN/LAN.

Hence why I, and others, are pointing to a NAT problem that the latest firmware has introduced.

Any resolution to this problem?

[Wayne_ · Accepted solution]

Seems like the firmware push to 3.11.6.2 has helped. I'll keep monitoring. Thanks @BellNick for your help to date.

[Strontium]

I am experiencing the same issue (works outside LAN but not within-LAN), how do I get 3.11.6.2 pushed to my Gigahub?

[dks]

Thanks for your question. The easiest way to do what you ask is to reboot the Giga Hub. There is no guarantee you will receive it, however.