Just started using this since Hyra (hooks.hyra.io) shut down. Hoping to see less of the outages that occurred with Hyra!
Any ideas, why this error suddenly came?
Is it because the IP is trying to send a too large embed?
error encountered: PayloadTooLargeError: request entity too large
4|webhook-proxy | at readStream (/Path/webhook-proxy/node_modules/raw-body/index.js:155:17)
4|webhook-proxy | at getRawBody (/Path/webhook-proxy/node_modules/raw-body/index.js:108:12)
4|webhook-proxy | at read (/Path/webhook-proxy/node_modules/body-parser/lib/read.js:77:3)
4|webhook-proxy | at jsonParser (/Path/webhook-proxy/node_modules/body-parser/lib/types/json.js:135:5)
4|webhook-proxy | at newFn (/Path/webhook-proxy/node_modules/express-async-errors/index.js:16:20)
4|webhook-proxy | at Layer.handle [as handle_request] (/Path/webhook-proxy/node_modules/express/lib/router/layer.js:95:5)
4|webhook-proxy | at trim_prefix (/Path/webhook-proxy/node_modules/express/lib/router/index.js:317:13)
4|webhook-proxy | at /Path/webhook-proxy/node_modules/express/lib/router/index.js:284:7
4|webhook-proxy | at Function.process_params (/Path/webhook-proxy/node_modules/express/lib/router/index.js:335:12)
4|webhook-proxy | at next (/Path/webhook-proxy/node_modules/express/lib/router/index.js:275:10)
4|webhook-proxy | at internalNext (/Path/webhook-proxy/node_modules/helmet/dist/index.js:142:6)
4|webhook-proxy | at xXssProtectionMiddleware (/Path/webhook-proxy/node_modules/helmet/dist/middlewares/x-xss-protection/index.js:6:3)
4|webhook-proxy | at internalNext (/Path/webhook-proxy/node_modules/helmet/dist/index.js:145:6)
4|webhook-proxy | at referrerPolicyMiddleware (/Path/webhook-proxy/node_modules/helmet/dist/middlewares/referrer-policy/index.js:24:3)
4|webhook-proxy | at internalNext /Path/webhook-proxy/node_modules/helmet/dist/index.js:145:6)
4|webhook-proxy | at xPermittedCrossDomainPoliciesMiddleware (Path/webhook-proxy/node_modules/helmet/dist/middlewares/x-permitted-cross-domain-policies/index.js:15:3) {
4|webhook-proxy | expected: 306694,
4|webhook-proxy | length: 306694,
4|webhook-proxy | limit: 102400,
4|webhook-proxy | type: 'entity.too.large'
Whatever is sending that is sending something over 100KiB in size? Thatâs absolutely huge for a request body.
oh what the heck?!?!?!? i thought hooks.hyra.io was still alive
I literally switched to https://webhook.lewisakura.moe/ right before hooks.hyra.io shutdown (i didnt even know that its gonna shutdown)
I guess im lucky enough my projects safe now because they dont use hooks.hyra.io anymore
1 Like
Always a good idea to have redundancy backup solutions 
I always make sure all my setups have at least 1 or 2 backups.
1 Like
a bit of a bump but this is currently giving 403 errors, it works in studio but not in an actual server. im not sure whats going on, but nothing is changed between studio and the server.
2 Likes
can bump this, returning 403 on multiple games since around 7pm cest
1 Like
Most likely roblox related.
They stated in another http thread that they are trying to track HTTP issues.
Thought it was just me! Hopefully itâs fixed soon
99% of the time its giving 403 but sometimes 1-2 posts will go through and nothing else will for multiple hours. Started around 8-9 hours ago. Could this be linked issues with Roblox releasing on PS?
Unsure honestly. But yeah same thing happens to me, very little webhooks get sent through, most just error.
Good to know that Iâm not the only person having this issue, I thought I somehow screwed something up even though I hadnât touched the script nor the actual webhook for a few weeks.
Seems to be working again, not sure what happened. It will remain a mystery for now until we get an official response.
weird, it doesnât work for me still.
Yeah barely works, one post went through around 2 hours ago out of the 25ish that were meant to do
Now returning HTTP 503 
Just got HTTP 530, proxy service seems to be completely down now. It did work for like an hour before this.
Argo Tunnel error | webhook.lewisakura.moe | Cloudflare
Sorry that was what I meant earlier, yeah itâs completely down BUT it seems to be working for some games that use the same proxy
Can bump on the 403 errors, however they are not consistent for me. Sometimes the webhook works and sometimes it doesnât, seems to depend on the server that roblox is using to send the request.
1 Like
I got the same weird HTTP 403 Error in regular in-game servers but not in Studio. Webhooks keep coming up as {"proxy":true,"message":"Unknown endpoint."}.
I am trying to find a solution currently.
2 Likes
I can attest to this. It is very inconsistent and doesnât work most of the time.