Hi.

First of all thanks for your work to run Snapdrop with Node.
I got it installed but when I open my server on the internet it loads the page but it can't connect.
At the bottom it says "Connection lost" all the time. After the announced 5 seconds it disappears briefly and then comes back.

How can I fix this?

On November 28, node-snapdrop public server will stop working because of Heroku Free Plan Shutdown.
Since I cannot spend money to keep running this server my own, it will be shutdown because I'll not have "free dynos" anymore.

I'm asking all the Snapdrop and node-snapdrop community to help this open-source project keep running by proposing new free hosting solutions that are compatible with technologies used here.

Remember also node-snapdrop have to keep WebSocket connections for clients discover, so for example Serverless Functions (Vercel, etc...) won't work properly.

Starting November 28, 2022, we plan to stop offering free product plans and plan to start shutting down free dynos and data services.
- Heroku Next Chapter

Hello,

As soon as I try to upload a file at node-snapdrop.onrender.com, the following error is thrown :

network.js:333 DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: Called in wrong state: stable
_onError @ network.js:333
(anonymous) @ network.js:289
Promise.catch (async)
onServerMessage @ network.js:289
_onMessage @ network.js:378
(anonymous) @ network.js:367
fire @ network.js:509
_onMessage @ network.js:39
ws.onmessage @ network.js:19

Thanks

Tracking issue for:

• https://github.com/Bellisario/node-snapdrop/security/code-scanning/4

Should be introduced ASAP a fix for this vulnerability since an user could use DDoS attacks to shut down the entire application just by requesting index.html.

I think I'll fix this using express-rate-limit.

This is not a really high severity vulnerability since Heroku hosting has an internal DDoS attack protection, but this is really bad instead for users hosting their own node-snapdrop server.

The first boot worked just fine.

When I restart the program I always geht the Error message:
"ERR_TOO_MANY_REDIRECTS", whenever I try to access the webpage.

I run it on a raspberry pi 3B+

Testing my own and yours and I can't get messages to work. Tapping, right clicking, etc all fail to do anything through this version. The original snapdrop works fine. I can't see what would be going wrong myself that is different from the original.

Thanks for the great work. It probably works well, but I never got around to trying it 🥺

Could you implement the server in the form of .exe and .dmg files, as for example done in VLC Remote? This will allow simple beginners to use this wonderful service without unnecessary difficulties, simply by adding them to the system startup. I will be very grateful 🙏

I have the node server running on my Macbook pro. If I open it in a browser on the Macbook and on a handheld device by using the ip (in my case 192.168.0.258:3000) it works on both but they don't discover each other. If I open it in multiple tabs on either device, the different instances on one device discover each other, though.