I’ll do some testing later and see if the number of connections is large. As you know, I am obsessed with that for and what it means for ordinary users.
I wonder as well if the protocol is very ‘chatty’. That might not play well with mobile broadband connections or VPNs.
I’ll try later. What size uploads are you talking about?
It did when I had proton VPN. Also it was relatively slow compared to the other VPN I use. I can max out my 400Mbit/s d/l 40Mbit/s upload link with it across the Tasman sea to NZ.
I no longer use proton vpn anymore for this very reason
Generally, problems are more noticeable in files larger than 200-300 chunks.
I have been with them for more than two years and, until now, I have had no problems.
In a speed test today and with VPN enabled, I am getting about half the speed of my connection. Other times I get up to 100%.
If I kept this speed it would be fine, but the problem is that, when uploading files, it ends up reducing the speed to almost zero.
Nevertheless, I have filed a complaint. Let’s see what they tell me.
800M files upload in 17mins - no difference for me with/without VPN.
all playing just fine 
Thanks.
There are a problem with ProtonVPN.
With VPN enabled the connection freezes.
Without VPN, no.
There can be many reasons for that:
I have tried different servers in different countries and always the same. It starts with a good speed but after a while it slows down until it almost stops.
This happens only on uploads. In normal use or downloading files in safe, works fine.
think we have lost the faucet
🔗 Connected to the Network Requesting token for wallet address: b657dd76cbfa1a155f6023e74446add281fb6078faaa4dddd4756489ccdf0ff12623bbbbeae550602ba71800eeaf0cf7
Failed to get tokens from faucet, server responded with: "Failed to send tokens: Transfer Error Failed to send tokens due to The transfer was not successfully registered in the network: CouldNotSendMoney(\"Network Error GetRecord Query Error RecordNotFound.\")."
What’s largest upload anyone had managed so far ?
I’m getting to about 6000 chunks before getting errors using default settings.
Well thats unfortunate…
safe@CloserNet01:~/logfiles_with_records$ safe files upload safenode.log.20231222T195138
Logging to directory: "/home/safe/.local/share/safe/client/logs/log_2023-12-22_20-04-42"
Built with git version: 61a47b3 / main / 61a47b3
Instantiating a SAFE client...
Trying to fetch the bootstrap peers from https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts
Connecting to the network with 98 peers:
🔗 Connected to the Network Starting to chunk "safenode.log.20231222T195138" now.
Chunking 1 files...
Uploading 42 chunks
Error:
0: Failed to upload chunk batch: Transfer Error Failed to send tokens due to The storage payment transfer was not successfully registered in the network: CouldNotSendMoney("Network Error GetRecord Query Error RecordNotFound.").
Location:
sn_cli/src/subcommands/files/mod.rs:306
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
I have many many of these RecordRejected errors. I will try putting relevant logfiles to filebin instead.
Wonder if being in Australia is an issue for Proton. Because it was constantly very slow and trying to download any large files was a nightmare. I was with them for over a year. It was only ever used for browsing and streaming youtube was a very poor experience.
[EDIT] Yes I often used different servers around the world. Usually Swiss servers were the better experience.
I also reached around 6000 chunks.
I tried to upload a 6GB ISO, with about 12K chunks, but half way through it started to give errors.
And yes, since about 5 hours ago the faucet gives error.
Hi, All,
the server itself is still running,
BUT there is failing point in the infrastructurestructure, which result in any new spends (of transferring token from faucet_server to a user) will be rejected by the network.
Just checked the logs from faucet_server, which shows there was a burst of service at 2023-12-22T18:16 GMT, which seems triggered an unrecoverable failure within the transfer infrastructure,
and fails any further get token request to faucet_server, as it can no longer get its spend to be approved by the network.
We are currently investigating it.
Meanwhile, if you spot any handling of records 163800 , e2eb19 and 774c86 in your nodes’ logs, please send the correspondent log files to me directly.
Thank you very much.
Have would you recommend to search the logs on a machine ?
just search 163800 , e2eb19 and 774c86 these three keywords among the logs
I have e2eb19 and 163800 - relevant lines with two before and after below. I also have a lot of references to 163800Z - but I don’t think that’s relevant here so I omitted them. Can send full logs if needed.
If I’m on form this will do it:
grep -le "163800(5\|e2eb19(c\|774c86(a" ~/.local/share/safe/node/*/logs/*
That’s grep minus ee el, and backslash pipe separating the hex values, but you can copy and paste of course. 