-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
why Userstyles.world does say 403 forbidden? #321
Comments
Hi! No, it's not. It looks like the recent anti -abuse/-spam measures have a false-positive. Sorry about that! Those were experimental, I hope we'll be able to fix this soon. |
I got the same issue from Vietnam, don't know whether firewall detect IP in blacklist or something else? |
It also happens in thailand too |
This comment has been minimized.
This comment has been minimized.
I no longer hope we'll be able to fix this soon, still hoping we'll fix this eventually. I do not control the server. |
the only option is a vpn |
ummmm yeah, you need to Use vpn if you don't want to wait until Developers fix the userstyles.world nginx problem |
it's been a long time and still not fixed |
Sad Mario |
Have same issue in Singapore. Tested with multiple devices under different ISPs. ALL 403! |
Which means this issue happened from all Southeast Asia countries? |
So we had Thailand, Vietnam and Singapore... Can't speak for other countries though. |
Hey guys, check my proxy with Cloudflare worker out. It works for me! |
But when I entered the Userstyles world with Cloudflare proxy, it still didn't work on thailand |
It isn't very stable for me either especially on Firefox. MS Edge has better success rate - probably they prefer Chromium. |
i tried to do the same on MS edge, but still didn't work |
works for me |
So how do you get the Userstyles world work? |
i use thorium (chromium fork) |
What does thorium do? |
idk, but the proxy for userstyles world somtimes doesnt work (403 forbidden) |
I think I'm going to switch default Chromium browser superrmium to Thorium |
but the site says 403 Forbidden, nginx.
The text was updated successfully, but these errors were encountered: