Bouquins Does it mean this issue only occurs when using Wifi ?
I would be careful about generalizing from @wingman-4's particular experience.
Updating errors have been a sporadic, but common, experience for several years. The typical pattern is that download speeds slow to a crawl (a few KB's per second) for 120 seconds or longer, and then the server breaks the connection.
I haven't had the problem recently (in the last three weeks I've done three fresh installations, in each case requiring a 400+ file update, without an issue), but I've had the problem numerous times over the years I've used Solus, A year or two back, I had the problem with almost every weekly update, typically occurring during large-file downloads -- Firefox, libreoffice-common, kernel. It was maddening, but others taught me the eopkg up persistence method I described above. Quite a number of threads discussed the issue at that time, and the persistence method was the standard solution.
The best evidence is that the RIT server is overloaded, throttling down download speed in an attempt to remain in service but eventually breaking. That is consistent with the "slow to a crawl and break" experience from earlier iterations of the problem. @WetGeek suggested in another thread that current issue may be related to the fact that RIT students returned to in-person schooling last week, with attendant high server use. I don't have any information about that, but the current issue seems to be clearly related to server overload, because that is where the "slow to a crawl and break" behavior described by @Antoine and others discussing the issue in other recent threads clearly points.
But the typical pattern might hide specific, particular issues relating to particular users. The download process is a complicated chain with many links -- source server, internet routing, ISP routing, local routing, and network adapter, to name a few components that are involved. If any link in the chain is not working, the download will fail, and troubleshooting between the network adapter and the server is next to impossible for most users.
Given the possibility of masking, I don't doubt that @wingman-4's problems might be related to his wifi adapter or wifi router. That would explain why his Ethernet connection works but wifi doesn't. But I would not generalize from his experience given what we know. What has been reported points to the RIT server as the proximate cause.
If the RIT source server is the root of the current problem, the good news is that the current problem is most likely temporary. The server seemed to be fine Wednesday or Thursday of last week, when I did a fresh install of Solus Budgie, but went to the dogs since then. Chances are RIT source-server traffic will return to normal levels within a few days, and the problem will fade away until the next time. That is cold comfort, but there is a workaround/solution, which I described above and which is described in many other threads on the issue.
