Issue self hosting Bitwarden alongside other services

[subhb]

I am trying to self host Bitwarden along side my other web services.
I am following the below posts but it appears that I am missing something here:

Guide to setting up Bitwarden behind an nginx reverse proxy configuration

Guide to routing to your Bitwarden Server via nginx reverse proxy Using a Reverse Proxy In this guide we will cover how to set up a Self-hosted Bitwarden Server, accessed via an Nginx Reverse Proxy. A reverse proxy is an application that sits between end-users and the servers and services that they wish to access. There are many reason a user may wish to implement a reverse proxy, which can be read about here: In particular, many users implement reverse proxies to host multiple services o…

The issue that I am facing right now is that my Bitwarden is running along with nginx as per the architecture mentioned in the link.

But now, neither the base nginx nor the Bitwarden is accessible over the domain.
I keep on getting a HTTP 522 on them.

FYI: Self hosting with sub domain was working prior to this setup where the only service was Bitwarden. Problem started occurring as soon as I started switching over to this architecture.

[subhb]

FYI: For NGINX and Bitwarden port conflict, I have followed : Guide to Setting up Bitwarden behind an Apache reverse proxy configuration

[subhb]

Could anyone please help me here?

[grb]

Have you tried reaching out to customer support?