I'm getting a 403 error on any `fetch` call

This is the raw error that I'm getting:

<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta content="text/html; charset=utf-8" http-equiv="content-type" />
<style type="text/css">
body {
font-family: Arial;
margin-left: 40px;
}

img {
border: 0 none;
}

#content {
margin-left: auto;
margin-right: auto
}

#message h2 {
font-size: 20px;
font-weight: normal;
color: #000000;
margin: 34px 0px 0px 0px
}

#message p {
font-size: 13px;
color: #000000;
margin: 7px 0px 0px0px
}

#errorref {
font-size: 11px;
color: #737373;
margin-top: 41px
}
</style>
<title>Service unavailable</title>
</head>
<body>
<div id="content">
<div id="message">
<h2>The request is blocked.</h2>
</div>
<div id="errorref">
<span>20240123T175016Z-6s0u518e7h2pt42kzzn145e7b40000000440000000008e5v </span>
</div>
</div>
<script defer src="https://static.cloudflareinsights.com/beacon.min.js/v84a3a4012de94ce1a686ba8c167c359c1696973893317" integrity="sha512-euoFGowhlaLqXsPWQ48qSkBSCFs3DPRyiwVu3FjR96cMPx+Fr+gpWRhIafcHwqwCqWS42RZhIudOvEI+Ckf6MA==" data-cf-beacon='{"rayId":"84a1e0c7d2f36689","version":"2024.1.0","r":1,"token":"13614ec38c8f4745858fd4cc49cdd888","b":1}' crossorigin="anonymous"></script>
</body>
</html>

<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta content="text/html; charset=utf-8" http-equiv="content-type" />
<style type="text/css">
body {
font-family: Arial;
margin-left: 40px;
}

img {
border: 0 none;
}

#content {
margin-left: auto;
margin-right: auto
}

#message h2 {
font-size: 20px;
font-weight: normal;
color: #000000;
margin: 34px 0px 0px 0px
}

#message p {
font-size: 13px;
color: #000000;
margin: 7px 0px 0px0px
}

#errorref {
font-size: 11px;
color: #737373;
margin-top: 41px
}
</style>
<title>Service unavailable</title>
</head>
<body>
<div id="content">
<div id="message">
<h2>The request is blocked.</h2>
</div>
<div id="errorref">
<span>20240123T175016Z-6s0u518e7h2pt42kzzn145e7b40000000440000000008e5v </span>
</div>
</div>
<script defer src="https://static.cloudflareinsights.com/beacon.min.js/v84a3a4012de94ce1a686ba8c167c359c1696973893317" integrity="sha512-euoFGowhlaLqXsPWQ48qSkBSCFs3DPRyiwVu3FjR96cMPx+Fr+gpWRhIafcHwqwCqWS42RZhIudOvEI+Ckf6MA==" data-cf-beacon='{"rayId":"84a1e0c7d2f36689","version":"2024.1.0","r":1,"token":"13614ec38c8f4745858fd4cc49cdd888","b":1}' crossorigin="anonymous"></script>
</body>
</html>

It worked previously, so I have no idea what the problem could be sad

I attached the code that I'm using.

13 Replies

Cyb3r-Jak3•11mo ago

Mojang rate limits on IP so workers can get rate limited easily

CelesteLoveOP•11mo ago

Yeah I know but I changed the IP to another one hosted in my server and I get the same error And the error says cloudflare even when calling external websites that don't use thinkingpug

Cyb3r-Jak3•11mo ago

What do you mean you changed the IP?

CelesteLoveOP•11mo ago

I tried using https://minecraftapi.eufonia.studio/KernelUwU it works anywhere except in the worker And it shows the same error

Cyb3r-Jak3•11mo ago

Do you have Cloudflare in front of yours? If so then it could be your WAF blocking the sub request

CelesteLoveOP•11mo ago

I have it only for the second API But the error is the same for both of them

Cyb3r-Jak3•11mo ago

Unfortunately don’t know then. I might be able to try it out later to see if I have the same issue

CelesteLoveOP•11mo ago

Don't worry, thank you for your help!

Erisa•11mo ago

Possible you're missing a header like User-Agent? Not sure how your proxy works however

CelesteLoveOP•11mo ago

That's an interesting theory yes, I will try that later

conor•8mo ago

@CelesteLove same issue, did setting UA help?

CelesteLoveOP•8mo ago

It didn't, I had to set up a proxy on my own infra, my theory is that mojang blocks cloudflare IPs

conor•8mo ago

Cool thanks

Gaming

Programming

I'm getting a 403 error on any `fetch` call