Server issue (Not a complain, a query)

Right now as I am writing this, snapdrop.net isn't working with the error being The Snapdrop-Server cannot be reached.
This isn't a complain, I just wanna learn what does it mean exactly? What server is snapdrop talking about?

Would also appreciate if someone could explain how WebRTC works in a nutshell.

[Bellisario]

Also for me, very strage...
Waiting that the problem is solved, meanwhile you can try using my Node.js version here:
https://node-snapdrop.onrender.com/

---

@RobinLinus is there any other strange server error causing this issue?

[JustSch]

Also if you'd prefer a server independent version you can use my desktop version node-snapdrop-electron

[Bellisario]

Update

Seems Snapdrop is working properly now!

[nikkehtine]

Snapdrop is still down :/

[JustSch]

It does seem to be down again. I wonder what keeps causing it to go down.
Edit: It is up again

[Bellisario]

Seems to be up another time for me

[RobinLinus]

@Bellisario looks like the fix made it worse, no?

[fm-sys]

looks like the fix made it worse, no?

Probably same as before... Nevertheless rather unsatisfactory unfortunately :-/

[Bellisario]

@Bellisario looks like the fix made it worse, no?

Yes, it looks like that's not solving the problem...
I think in this case the best solution could be (for now) to use something like pm2 to restart the server on crash (or something similar with Docker).

[svenjacobs]

As snapdrop.net is frequently not available (just have a look at the issues 😱), is there anything that we can do to improve the stability of the service? What are the actual reasons for the recurring downtimes? Could you please share some more details @RobinLinus?

[RobinLinus]

@svenjacobs looks like the server breaks whenever there is too much load. Also someone keeps trying to DoS the Snapdrop server. We started to port it to Rust for better stability and performance #521

[tuupola]

Down again.

$ curl --include https://snapdrop.net/
curl: (7) Failed to connect to snapdrop.net port 443 after 39 ms: Connection refused

[Pkcarreno]

hi @RobinLinus ,This server problem you mention is related to the loading of the page? what about giving pwa offline capability to the page? could it work to solve this problem?