I’m using the webhook.lewisakura.moe. Rarely works unfortuately 
Thank you for your service. I have used this for over a year.
The algorithm has blessed me with a surge of new users in the last 3 weeks, and just today I’ve switched to Amazon Web Services to handle my webhook.
Somehow I coincidentally saw this post again the same day.
3 Likes
Did u make ur own webhook on AWS or u forked another proxy?
I hosted my own Flask application on AWS Elastic Beanstalk and used it as a proxy to send chat logs from my game to my discord server through a discord webhook for moderation purposes.
@lewisakura Is there a way to limit the CPU usage for the webhook service?
It seems like it is running as fast as it can go, and takes up 100% of the CPU from time to time.
I have tried running as 1 fork.
I have tried using a cluster, up to 4 clusters.
It doesn’t seem to help at all.
2 Likes
Webhooks seem down currently. We recently started using this for our game Anime Card Battle.
1 Like
Lewis’s or mine?
Mine is still up.
Just tested, and it works.
Looks like Lewis’ webhook proxy got shut down by Discord. A shame, I was just getting started with it.
Guess I’ll have to find a new proxy service till Lewis can get this one back.
My site uses Lewis’s engine, it works just like lewis’s site.
https://webhook.newstargeted.com/
1 Like
Currently I’m running kingermanpublic and it’s been working quite well, but if that goes down I’ll look into your site!
There seems to be an issue with the prisma when trying to install it on almalinux 9.
The prisma only supports query-engine-rhel-openssl-1.1.x not anything later.
Tested it on Almalinux 9, got this:
npx prisma --version
Error: Unknown binaryTarget rhel-openssl-3.2.x and no custom engine files were provided
is there a way to view the queue for your hooks?
Are you asking about the amount that is in the queue, i cannot see the content of requests in the queue my self, can however see how many requests are in the queue at any time.
But i am running the system in a cluster, making it run faster (If it works).
wrong reply sorry, but I was asking If there was a thing to see how long the queue is or something like that
I’m not quite sure how long of a delay most queues are.
But around 22k requests come into the queue from time to time.
Someone keeps spamming the queue with both valid and invalid requests.
I attempted to submit a request using the /queue command with both proxies (Lewi and News). However, after 30 minutes, the request has not appeared on Discord.
How are you sending these requests?
Are they being sent at a high rate?
It looks like someone is attempting to DDoS the service by flooding it with too many requests per minute. This could be the reason for the delay.
I’ve increased the queue capacity to handle a larger volume of requests, and until now, the service has been running smoothly without issues.
I’ve cleared the queue, so performance should be back to normal—unless the service gets spammed again.
1 Like
I just added the /queue to the url. Sending without the /queue delivered the message in the discord instantly. But the one with /queue never came. I sent like 5 times with a delay of 1 minute between each request.
You might want to find a way to block those doing too much requests. I think the WebhookProxy should have some type of authorization key to identify the requests.
I am using Lewis’s setup.
But it does have ratelimit and auto ban enabled.
But i do see someone sending more than 200 requests each second, making it end up with a lot of queued messages, that takes a long time to get through.