Bug: Pairing not working on self-hosted with Nginx Reverse Proxy about pairdrop

[schlagmichdoch]

Thanks for all the information! Makes debugging much easier!
Your Nginx config looks good and as files sharing works the issue is not to be found there.

TypeError: Cannot read property 'getRandomValues' of undefined

means that crypto.webcrypto does not exist for the node server. This is an unexpectected error that causes the server to crash and restart.

I'll try to reproduce the issue and come back to you

[schlagmichdoch]

crypto.webcrypto and crypto.webcrypto.getRandomValues(typedArray) need Node.js v15.0.0 or above.

When I use the given docker-compose file I cannot reproduce your issue as node:lts-alpine is used which currently points to v18.14.0.
When I replace node:lts-alpine with node:14-alpine version v14.21.2 is installed and the behaviour is exactly as you described.

• Have you changed the docker-compose.yml?
• What is the output of docker-compose run node node -v

[chaosbunker]

Ha! Not a bug, then - just a silly oversight on my end. You pointed me in the right direction by referencing the correct node version. I had an outdated and unused node:lts-alpine image 'lying around', so when i did docker-compose up -d it just used that and I didn't notice. Good reminder to purge unused docker images:)

Now running PairDrop with the most recent node:lts-alpine and pairing works as expected. I'm so happy, this is incredibly useful! Thanks so much:)

[schlagmichdoch]

Perfect!
It appears you can prevent this by running docker-compose pull before which pulls the latest image if an update is available.
https://www.baeldung.com/ops/docker-compose-latest-image
I guess I will add this to the documentation.

Glad it works now and you like it :)