This is the answer to the situation.
Because of people using discord logging when they are not stated to.
Hopefully it wont be long before they unban it, once again as this has happened in the past and it got allowed / re-added, once again.
This is the answer to the situation.
Discord just banned Roblox from sending requests to their severs, meaning you can’t use discord webhook in your games anymore.
This is not deep example + Roblox not using free cloudflare So the problem isn’t from roblox The problem from discord api Because discord using Premium cloudflare but roblox using enterprise
There is a work-around to this issue, which is a bit more tedious and annoying but if you still want to use discord logging follow this route.
Create an API with this,
Ensure to add into the api once the data is gotten it posts through a webhook (discord), like you would normally.
Then all you have to do to ROBLOX’s script, is send the data to that API and then it works, though this workaround is annoying this is the only current way I can think of.
Outbound HTTPS requests dont go through a DNS. DNS resolution is used for inbound requests so it can route a URL to an IP.
Discord has put a rule in place on their Cloudflare portal that blocks any incoming request with the UserAgent of Roblox/Linux
For example, DNS will let your route example.com to 1.2.3.4 through an A record while still masking the IP
I’m discord.js Developer And I have handle with a lot of problem in their api Their api is so bad
So UserAgent Is keep reset to automatic like unkown useragent They can’t select roblox from their usergent useragent is not stable thing they can by IP Only Also IP Not very stable But they can
This is because Studio has its own User-Agent.
This makes me wonder if RequestAsync
lets you specify a custom user-agent, potentially getting around the block? (Although iirc a number of headers are ‘protected’ so probably not)
@ContemporaryMoment @saouvs please take it to DMs to save everyone else + Roblox staff some reading time, this is not immediately relevant to the issue.
I thought I was the only one who’s having this problem.
Just a word of advice, using Discord webhooks for logging proposes is not allowed and can get your Discord account banned! (They might have changed this since I last checked)
Time to construct your own proxies, have fun! Hopefully this isn’t a permanent change, then again using discord for logs is against TOS.
discord has banned webhooks from roblox again
We will have to wait apparently until then you could try discordapp.api instead discord.api should work.
15 posts were split to a new topic: Off-topic posts on “Discord webhooks don’t work ingame”
Use Likes instead of replying to support a previously made point.
This is a bug report. Don’t reply discussing about proxies and other workarounds. Create a discussion topic elsewhere.
Confirming that this works!
We don’t use Discord to log data like errors or anything, but we do use Discord webhooks for other purposes, like player feedback.
I didn’t think this would work, but I’m surprised it did!
Just change your webhook URL (if you use that) to discordapp.com/api and not discord.com/api
Stop liking this it doesn’t work anymore.
Use a proxy. This one respects rate limiting at works like an absolute charm.
You can also use Guilded.gg. It’s owned by Roblox, and hasn’t blocked Roblox. The format for messages/embeds is the exact same as Discord
Now that I remember, somewhere in the official API documentation says that they are changing the api url from “discord.com” to “discordapp.com”, they were deprecating the “discord.com” url and they would eventually remove them, if this were the case then it is not related to Discord banning Roblox again!
EDIT: NOT THE CASE, the “discordapp.com” api is the deprecated one, it may be possible that Discord actually banned Roblox’s useragent but forgot to ban it on the deprecated url
Here’s how to bypass the blocks
1
2 How your API Will work
If you don’t know how to make api No worries I will make a plugin soon Will contain everything you just put your script and more info
Just an update on this: Can confirm, it’s not anything we did on our side. We’re still looking into what we can do about it.