GreasyFork is Banned in China Due to SNI Blocking #1378
Comments
|
|
mc-yzy15
changed the title
|
Hi there, I am also affected by the SNI blocking issue in China.I do not have access to a VPN, and I have tried several methods(DNS modification, hosts file editing, browser configuration,and tools like bypass-GFW-SNI)but none of them worked. Is there any other solution that doesn't require a VPN? Any help would be appreciated. Thanks! |
|
I tried various methods to bypass the SNI blocking, including DNS modification, hosts file editing, and browser configuration, but none worked. Even tools like bypass-GFW-SNI failed. I don't have a VPN, and it seems like the only viable solution for now. GFW's SNI detection and DPI are very effective. Any other suggestions would be appreciated. |
|
先等一段时间看看是啥情况和态度再说吧，这和gitcode沾不到什么关系，你的issue感觉像是chatgpt生成的，实在不行后期也会有人搭建镜像访问站点的 |
|
I'll look into possible countermeasures. I do note that greasyfork.org appears to be blocked, but sleazyfork.org, with the same IPs, does not seem to be. |
This comment has been minimized.
This comment has been minimized.
|
I don't need you forwarding AI-generated suggestions to me. If I wanted AI's advice, I can ask it myself. |
|
Okay. I'm so sorry. |
|
GitHub Issue Reply Reply: Thank you for your detailed observations. It's clear that the situation has evolved with both GreasyFork and SleazyFork facing different types of blocking mechanisms: • GreasyFork(SNI Blocking): • GreasyFork is currently blocked due to SNI(Server Name Indication)filtering. This means that the GFW is inspecting the SNI field in the TLS handshake and blocking connections to GreasyFork based on its domain name. • SleazyFork (TCP RST Blocking): • SleazyFork is now also blocked, but through a different mechanism: TCP RST packets. This type of blocking involves sending RST packets to forcibly terminate the connection before it can be established. It is looks like this:
Best regards, 2025/2/7 |
能沾到一点，gitcode上面我记得可以部署pages，可以试试拿它做镜像，实在不行就github.io或者siteproxy也行 |
我这个也不完全是GPT生成的，我写的完了之后让GPT帮我完善了一下（本人第一次写Issues，怕写错，写漏，请理解） |
|
I've checked https://www.comparitech.com/privacy-security-tools/blockedinchina/ which claims greasyfork.org is blocked but not sleazyfork.org. My own analytics show full Chinese traffic still coming in on sleazyfork.org, at least as of start of day UTC. So if it's true that sleazyfork.org is blocked, it has to be both a different method that the checker can't detect, and have happened more recently than greasyfork.org. |
Thanks for the info. It looks like the situation is evolving quickly. If SleazyFork is now being blocked by TCP RST, that would explain why traditional SNI-based detection methods might not catch it. The RST blocking could be more recent and harder to detect initially. We'll keep an eye on this and see if there are any updates or changes in the blocking methods. Appreciate the heads-up! Best, |
Interesting.It seems that the situation with GreasyFork and SleazyFork is quite different now.For GreasyFork,the TCP Ping is only working normally in Hong Kong and Taiwan,which might indicate some regional differences in how the blocking is being applied.On the other hand,SleazyFork’s TCP Ping is normal across all regions,suggesting that the site is still technically reachable via TCP connections. This discrepancy could mean that while both sites face restrictions,the methods and effectiveness of these restrictions vary.It’s possible that GreasyFork is being targeted more aggressively in certain areas,while SleazyFork might be experiencing a more general but less effective block. We’ll definitely need to keep monitoring this to see if the situation changes or if there are any updates on the blocking methods being used. Some Pictures:(Note: The lightning mark indicates a partial timeout and has no significant impact)
mc-yzy15 |
|
It's an amazing situation |
|
I will sleep now. We will talk this task tomorrow. |
|
I'm in Beijing, so it should be the opposite of the time where you live (e.g. We are at night and you are at day). |
|
Bye. |
|
For an unrelated reason, traffic to the site is now routing through Cloudflare. It doesn't seem to have helped with this issue, but in case anyone is wondering why the IP addresses have changed. Because Greasy Fork is blocked and not Sleazy Fork, right now I'm thinking I'll set up a new domain for Chinese users to access. I expect that will work, at least temporarily. |
|
Could GreasyFork build a mirror site on Amazon AWS S3? Use the common domain s3.amazonzws.com would be helpful, like Psiphon mirror site. |
|
Is that any better than just setting up a new domain? |
|
Yeah! You can use dnsexit ， this free and so good. |
Why not use Amazon AWS S3? It even doesn't need a domain, and it's hard to block by gov's censorship firewall. Below is a mirror website of Psiphon: https://s3.amazonaws.com/psiphon/web/svxu-p5vk-d403/en/index.html |
|
https://cn-greasyfork.org/ is now up. It's intended to be a mirror with the following changes:
Let me know of any suggestions or bugs encountered. |
|
Sheas Cealer is a similar project to bypass-GFW-SNI and supports more websites. It is now working for greasy fork. |
Could also use this https://github.com/ValdikSS/GoodbyeDPI |
Thanks everyone. |
I will not close this issue for the time being, and it is convenient to work out solutions when there are new situations. OK? @JasonBarnabe |
|
OK, I have received your request and have written to the team, confident that they will be able to resolve it soon. |
Also, Accesser supports bypassing SNI block to greasyfork (Tested ealier today) But for now, seems greasyfork.org is not only being blocked by SNI, but also by its ip "96.126.98.220" cn-greasyfork.org seems also been blocked now: Update: |
|
Sheas Cealer has also supported cn-greasyfork.org 😄 |
|
https://cn-greasyfork.org is also banned by GFW.
|
Logging in with GitHub won't be possible on alternate domains as GitHub only allows you to associate with one domain. The option should not have been there; I've removed it. |
|
I think this may be blocked again |
|
To repost what I wrote here in case those who are interested can't access that:
|
|
可以通过使用这个项目在 Vercel 上部署一个自己的镜像站 https://github.com/gaowanlu/google 再绑定一个自己的域名 后面可能会有很多的镜像站出来，就像封禁 docker 时一样 |
|
为什么我镜像之后会瞬间重定向到 greasyfork.org |
|
我搭建了一个镜像网站，经过测试可以在 篡改猴 和 via 中正常安装拓展，不需要使用vpn 问题： 链接将会在dns完全指向cloudflare时发出来 |
|
中文: 新域名 https://nextgo.us.kg/ (此域名为中转,确保以后更换域名不用费劲心思再找) 它将有以下限制： 此域名为镜像 cn-greasyfork.org 下载地址为 update.greasyfork.us.kg
English: New domain: https://nextgo.us.kg/ (This domain name for the transit, to ensure that the future replacement of the domain name do not have to struggle to find again) It will have the following restrictions: 1.IP addresses from Japan will be blocked. This domain is a mirror of cn-greasyfork.org. The download address is update.greasyfork.us.kg.
最后，希望nextgo.us.kg不要被封 |
Thak you |
There is JS on the page to do that if you're not on an officially supported domain. This was done to stop a mirror a few years ago. I suppose I can remove it now if it's causing you trouble. |
不用了，经过测试发现一段时间后 https://www.greasyfork.us.kg 并没有自动重定向了，并且如果自动重定向 greasyfork.org 在中国会访问超时，用户有时间手动取消 No need, after testing, we found that after a period of time https://www.greasyfork.us.kg doesn't redirect automatically, and if it redirects greasyfork.org in China, the access will timeout, and the user will have time to cancel it manually. |
也有可能是因为 cn-greasyfork.org 已经删除了这个 js，但我最开始镜像的 greasyfork.org 并没有删除 It's also possible that cn-greasyfork.org has deleted the js, but greasyfork.org, where I first mirrored it, has not. |
更新长期地址自动跳转 请求地址 https://nextgo.us.kg/api 使用这个可以长期自动跳转到最新域名 |
|
请问在镜像后页脚需要加上什么吗？ Do I need to add anything to the footer after mirroring? |
|
如果域名被禁请在这里提issues https://github.com/fishcpy/greasyfork/issues |
Could you remove it now or add checks for Chinese users? thx |
|
I have removed the host name check. Please note that I do not officially support using mirrors set up by someone else, because there are potential security and performance issues. Use them at your own risk. |
Thanks a lot. If you're worried, you can also remove the check for cn-greasyfork.org only. |
|
I'll say it again for anyone who just scrolls to the bottom of this page... I'm not going to be making further attempts to bypass the block. With cn-greasyfork.org being blocked within a few days of being created, I don't see any point to creating any new domains. I don't see any other method of retaining the functionality of the site while allowing access to Chinese users. I support anyone who wants to use a bypass method (VPN, proxies, etc.) to access the site. I would recommend being careful about bypass methods set up by other people as you can't be sure of their security. |
|
@JasonBarnabe Could you try Amazon AWS S3? I don't think creating new domains is a right way, because it's easy to block. |
|
Now I'm sure that the access of main web is able for China Mainland users after turning up the ECH(set the secure dns which provide by cloudflare: https://1.0.0.1/dns-query).But the download page still didn't work(it didn't use cdn of cloudflare) |
CHS我的自建镜像站 特点
ENGMy Self-hosted Mirror Site Features
|
此域名已添加到fishcpy greasyfork镜像站监控列表 https://status.nextgo.us.kg/status/greasyfork |
Hi GreasyFork Team,
I'm writing to report that GreasyFork is currently inaccessible in mainland China due to SNI blocking by the GFW.This has been confirmed by multiple users and is causing significant inconvenience for those who rely on your platform for user scripts.
Current Situation:
• Users in China are unable to access GreasyFork directly.
• The issue is confirmed to be caused by SNI blocking, which prevents the site from being resolved correctly.
Impact:
• Users are unable to download or update scripts.
• Contributions from Chinese users are hindered.
Possible Solutions:
• Alternative Domains:Consider setting up alternative domains or subdomains that might not be blocked.
• Mirror Sites: Explore the possibility of creating mirror sites hosted on platforms that are accessible in China(e.g.,GitCode).
• Documentation: Provide guidance on how users can access GreasyFork using VPNs or proxies,while ensuring compliance with local regulations.
User Feedback:
• Many users have reported frustration with the current situation and are seeking alternative solutions.
• Some users have tried using VPNs or modifying DNS settings, but these methods are not always reliable.
Request:
• Could you please look into this issue and provide any updates or potential solutions?
• Any official statement or workaround from the GreasyFork team would be highly appreciated.
Thank you for your attention to this issue. We hope to see a resolution soon.
The text was updated successfully, but these errors were encountered: