send2cgeo icon indicating copy to clipboard operation
send2cgeo copied to clipboard

Send2cgeo server is very slow

Open Lineflyer opened this issue 4 months ago • 5 comments

@mucek4 While testing the new send2cgeo release 2025.08.17 I noticed that the server side is reacting very slow. This means:

  • Requested the PIN from c:geo takes up to 20 seconds
  • Registering the device takes up to 30 seconds
  • Sending caches takes up to 40 seconds from requesting the download until the download is triggerd in c:geo

The same problem was already noted in https://github.com/cgeo/send2cgeo/issues/144#issuecomment-2341167990 in September 2024

Lineflyer avatar Aug 17 '25 20:08 Lineflyer

I have tried to register mine and I don't see any slow calls. Could it be IPv6 problem?

mucek4 avatar Aug 19 '25 12:08 mucek4

Could be, I was on v6 for sure. Will check the log and try v4.

Lineflyer avatar Aug 19 '25 19:08 Lineflyer

I have v6 available and used everywhere (home and both mobile operators available) and don't know how to enforce v4.

That's what I get from the c:geo log:

Image

It a 200 response after a bit more than 30 seconds. This makes me guess, that there might be a timeout on v6 and fallback request on v4 after 30s?! Could that be?

Lineflyer avatar Aug 19 '25 19:08 Lineflyer

@mucek4 Ping 6 is not a problem at least, so maybe on protocol level (port not on v6)?

Image

Lineflyer avatar Aug 19 '25 19:08 Lineflyer

@mucek4 I repeated the test today. Now caches "sent" from the website are immediately loaded in c:geo. IPv6 was available and thus potentially in use. Can you confirm you changed something on server side? Seems fixed at least.

Lineflyer avatar Sep 11 '25 19:09 Lineflyer