Calling webdocket (ledger) routes from a different origin about btcpayserver-docker

[NicolasDorier]

closed?

[sigHash]

I wasn't really sure if there was an issue with my CI/CD or the nginx conf here.

Here's what I experienced:

I tried to deploy BTCPay on a PC (running ubuntu) behind a router and websocket routes stopped working. I checked the nginx logs and there is no trace of GET request for ledger routes. it simply times out. (other routes work just fine)

I should mention that I am making cross origin calls to those routes from a React web app, but I have already enabled Cors.

I still can not make it work on-prem, but it works just fine on azure without making any changes. (same docker images)

[NicolasDorier]

where it does not work, you are using a reverse proxy somewhere ?

[sigHash]

No, it's a bare metal machine, behind a router. I started BTCPAY with nginx as reverse proxy as mentioned here:

Hardware Deployment

[NicolasDorier]

Can you make an invoice and check in the Console logs if it manage or not to connect websocket?