500 is internal.
me too, and when you add /queue it gets sent to the proxy, but hangs and is never sent to the actual server
yes, with this proxy it returns Http 500 more often than not, switched it out for another proxy (found on the devforum, in a random thread) as a test and didnāt run into this whatsoever
Did you try my url, it uses the same system.
People who complain about Lewisās system not working, sometimes tell me that it works when they try my URL.
Iām not sure if Lewis has his setup more behind Cloudflare than I do.
https://webhook.newstargeted.com/
doesnāt work for me, both studio and in game
just tried it, works fine, using the proxy relevant to this thread, 9/10 times returns Http 500
Hi everyone, been able to actually sit down and look at this. Apologies for the delay.
The errors that have been seen are due to the proxy hitting the Cloudflare ratelimit of Discord, which is 50 req/s per IP address, which we have recently started exceeding (since the proxy eats requests that are bad, this means that the legitimate request count has started to exceed the ratelimits set by Discord). I have started talks with Discord to try and get the ratelimits increased for the service and try to provide relief in regards to the issue.
In other news, the proxy now handles roughly ~5.5k requests per second, which should be plenty of context for why the issue is occurring now.
I have also posted an announcement on the website. To remedy this temporarily, I have reverted the proxy to the version without the ratelimit ban. If I get a positive response from Discord, I will remove ratelimit bans again.
Cheers, and thanks for all the fish.
Recently Iāve been using your Webhook proxy to send and edit messages that it sends. But Iāve kind of come into a hold of some sorts. So currently you stated that /queue wont work with ?wait = true which Iām using to recieve back the data of the message and get the message ID so Iām able to edit the message later on. And at the same time I want a reliable place to make the messages which I already Rate Limit in my code to be queued in your system.
?wait=true
is inherently incompatible with the queue system because it requires the message to actually be sent before you can get a response. The queue system, as the name implies, puts your request into a queue to be dealt with at some point in the future, and sends back an acknowledgement that itās been queued. There is no workaround for this and I canāt determine what the message ID will be before it has been sent. It is only reliable in the sense that it will send in the future, not that it will guarantee it gets sent immediately. You will have to work out another solution.
Alright thanks for the reply, Iāll think of something to counter this off and Iāll let you know if I have any solutions so other people can use it.
@lewisakura Thank you for this awesome service, Iāve been using it for a couple of months, but at the moment it seems to be down? Getting error code HTTP 524.
Error 524 usually indicates that Cloudflare successfully connected to the origin web server, but the origin did not provide an HTTP response before the default 100 second Proxy Read Timeout
Iāve been receiving a lot of 500 Internal Server Error responses from the proxy for around a week now, could you please look into this?
The HTTP 500 errors come from Discord themselves ratelimiting me which is an unexpected API response (so it throws an error internally, itās expecting a valid webhook message), and whilst I did try to have a discussion with them they unfortunately said they canāt increase the ratelimits for the webhook endpoints.
The short version of it is that the service has grown to a level I didnāt really expect it to and I donāt have the money to increase the scale to fix this (it makes nothing despite being used by hundreds of games, and Iāve been running it out of pocket for a long time), so I would strongly recommend you host your own proxy instance or find another workaround. This will probably be a common occurrence on the public instance. Sorry.
Alright no worries. Thank you for the explanation.
I have a queue system already set up that uses both my site and Lewisās site if needed.
It will return output in the console if there are any issues, all error codes related to the proxy are also listed on the webhook site URL below.
If you want to see if thereās a new WebhookService module, it can be found on the site below, click āGet Startedā, and it will be a download link at the bottom.
WebhookProxy - NewsTargeted.com
WebhookService is the Module, that you put inside of the Send-Proxy-Queue script.
As an example.
That way, you can use /queue after the webhook URL, and send the embed to discord using proxy:Queue for the embed
Using the queue, you donāt need to add a delay.
Since the WebhookService will make sure all requests are queued both roblox and discord will be happy.
And you get ALL requests valid to Discord. (There is no guarantee, that your request will be received on Discord right away.)
Download WebhookService (newstargeted.com) (6.4 KB)
Send-Proxy-Queue.lua (2.0 KB)
Thanks for your resource, but Iām getting this error at the same time in which your website is down. What is the cause of this?
Also unrelated and nothing major, but the function āsendAuthorEmbedā is duplicated in the Webhook Service script.
Currently doing an OS upgrade from Almalinux 8 to Almalinux 9, it could take a few hours.
Doing status updates on the discord server.
i guess this post is outdated. We can call discord domain and it works.
You canāt in a live game.
So it isnāt outdated.
You can do it from the studio, from time to time yes.
Because then it will use your IP and heading, not robloxās.