mirror of
https://github.com/dutchcoders/transfer.sh.git
synced 2026-02-03 14:13:26 +00:00
transfer.sh is down #45
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @srikanthbojja on GitHub.
Looks like transfer.sh service is down since morning.
any update?
@KaKi87 commented on GitHub:
Hi, although the site is up, all upload attempts fail with error 500. Thanks
@stefanbenten commented on GitHub:
I can confirm, we are looking into some abuse details and are having the service unavailable during this time.
@cayenne17 commented on GitHub:
transfer.sh is back
@srikanthbojja commented on GitHub:
the service is down again since morning CET @stefanbenten
@srikanthbojja commented on GitHub:
It is back up again, thanks. Please close this ticket
@cayenne17 commented on GitHub:
Hi,
a issue has been opened:
https://github.com/dutchcoders/transfer.sh/issues/594
@qzmtch commented on GitHub:
And for users with RU IP, access to the service was blocked on principle? Or is it the hosting that is blocking access to the site?
@Ever4engel commented on GitHub:
Seem the website is down again
@stefanbenten commented on GitHub:
It is geoblocking abusing countries of various kinds.
@cayenne17 commented on GitHub:
uploading to transfer.sh has not worked for almost 1 month
@cayenne17 commented on GitHub:
from operator FR Free (AS12322) did not work for me
@acastillorobles77 commented on GitHub:
transfer.sh seems to be currently down
@mbenencase commented on GitHub:
I'm in Brazil, I can't use it as well
@dhavalsingh commented on GitHub:
Indian IPs might also be blocked, not working for me.
@GangstaPichu commented on GitHub:
I can't use it either and I'm from the US.
@tobbi commented on GitHub:
It seems to be working again on my end.
@Sierra410 commented on GitHub:
Ignoring the blatant racism that is calling entire populations of countries you don't like "abusers", the service also seems to be unavailable to at least some EU-based IPs. I have a server in the Netherlands and one in Poland (residential ISP, not a datacenter), and neither can access the service.
Is it only available to a list of "trusted" residential ISPs or something?
Regardless of how it's configured, in this state this service is basically useless. I have access to 5 different IPs/ISPs in 3 different countries and none of them can access the service. So, extrapolating from that: if I wanted to share a file with someone and managed to upload one, the chances are, they'd not be able to download it due to draconian IP filtering.
Not really putting that "sharing" part into "filesharing" there.
@cayenne17 commented on GitHub:
@stefanbenten
Would it be possible to whitelist trusted IPs?
What you call abuse is
@stefanbenten commented on GitHub:
Closing, since service has been restored. As soon as abuse is detected, we will suspend service again 👍
@cayenne17 commented on GitHub:
same since Saturday
@stefanbenten commented on GitHub:
It is currently not available at all, due to the fact that 80% of the files being shared were malicious, copyrighted and similar content. The time and effort it takes to resolve all reports for those 80% simply made it impossible to keep up (currently at least). Before calling our actions blatant racism, which in reality is just measuring the % traffic from each country and their reports caused, you should be aware of the "risks" of hosting a service with almost no restrictions on the data it accepts and the side effects it causes.
Since you have servers yourself, i do recommend to operate it yourself and then share your service to others, if your believe is it easy to do 👍
transfer.sh is intended to be selfhosted and the instance under the projects name is upon till this day best effort, since non-profit. Once we get to a better place in terms of detection and denial of copyrighted and malicious content, the likelyhood of it going back into service is low.
@paolafrancesca commented on GitHub:
https://github.com/dutchcoders/transfer.sh?tab=readme-ov-file#disclaimer
I'm locking the issue, and please everyone just the readme
@Sierra410 commented on GitHub:
Oh, I'm self-hosting things, alright. I just remember this being a useful solution I could recommend to other people, or use myself when I don't have access to my own servers.
If it's down due to it being impossible to moderate, perhaps announce that the service is down for that reason? E.g. on the home page? Which is not even loadable as of now.
"Geoblocking abusing countries of various kinds" is an vague statement that sounds like a claim that entire countries just randomly conspire to start abusing this service in particular, which makes no sense. Who says something like that?
I don't know the exact numbers, but assuming that most abuse (by which I mean malware, in this example, not copyright infringements. That'd be higher for poorer countries, naturally) comes from malware and that it's spread across the world more or less uniformly, countries with higher abuse % would be just countries in which the service is less popular among real people.
For example, if you ban the entirely of US or Canada or some other country, people there would learn that they can't rely on the service and would stop trying to use it (or they'd not learn about it in the first place, since even the homepage can't be viewed). Now, if you then un-ban that region one day, next to 100% of the traffic would be traffic generated by malware which automatically tries to use the service to spread itself.
It's sort of a self-fulling prophesy, so to say.
So, a single number that's illicit/legit traffic ratio for a region in isolation doesn't really say anything about the region in question.
And even if there is a measurable increase in abuse, there are more granular ways to filter traffic. For example regions which have slightly high abuse rates could be forced to complete a captcha (breaking curl support, but allowing use through a browser). If the rates are higher than that, the region could be banned from uploading, but not downloading. And if there's a legitimate state-sponsored attack or malware targeting a specific country, only then would a complete block make sense.