hosted bot is down

[kekkodance]

it seems like the bot went offline for a few days already, does this mean it's done for?

[brandongallagher1999]

Nope, I will redeploy the far stabler bot today. I deleted my discord recently and that's why I haven't been able to follow it's upstatus.

[kekkodance]

hope you'll come back in ripped

[brandongallagher1999]

Thanks, but I don't think I'll be reinstalling Discord again. If I do on the odd chance, it will only be for managing the bot.

[brandongallagher1999]

Deploying today. Just have to spin up a new VM in terraform as I lost the PEM file for SSH :/

[brandongallagher1999]

Actually, I found out that my Azure account has been shut down by the previous School email, and I currently do not have the funds to host 1337x.

This is unfortunate news, but both repos have steps to host the bot on their own @kekkodance

[brandongallagher1999]

That's why the bot shut down a few days ago, because that account was killed.

[Jadensc98]

I have a bot up using your code, could this be why it's stuck typing and not sending anything in Discord? @brandongallagher1999

[brandongallagher1999]

It could be something cloudflare related as was the problem before which is unfixable on 1337xs website side.

…

On Tue, May 3, 2022, 10:38 AM Jaden Scott ***@***.***> wrote: I have a bot up using your code, could this be why it's stuck typing and not sending anything in Discord? @brandongallagher1999 <https://github.com/brandongallagher1999> — Reply to this email directly, view it on GitHub <#15 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIYM5JZI232HVWZWCCRZ4FTVIE26TANCNFSM5UZ5YFCQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[kekkodance]

It could be something cloudflare related as was the problem before which is unfixable on 1337xs website side.

this was fixed in a recent commit pointed out by #17 @Jadensc98

[Jadensc98]

It could be something cloudflare related as was the problem before which is unfixable on 1337xs website side.

this was fixed in a recent commit pointed out by #17 @Jadensc98

Works now, Thanks!