#Нow to disable all deploys or find which of the deploys is still working

1 messages · Page 1 of 1 (latest)

simple hemlock
#

Hello, I encountered such a problem, in the dashboard I have disabled all deployments, but the bot continues to work, if you add a new deployment, then it works in parallel with the old deployment of the bot, is it possible to somehow find this active code and disable it or is it possible to completely disable all options launched earlier, it will not be displayed in the list, everything that is all deleted, I already tried and disabled the project from the repository from the github and completely deleted the project, nothing helps

wary ravenBOT
#

Project ID: e81e13b1-1b73-4e4e-9994-f4df02472333

#

You can remove the deployment itself. No need to delete the entire service. Reactivating a previous deployment or pushing changes can also temporarily disable the trigger.

unique cloud
#

you're absolutely positive you're not running the bot somewhere else besides railway?

#

like accidentally in the background on your computer

simple hemlock
unique cloud
#

okay, please link your account

simple hemlock
#

I connected)

unique cloud
#

thank you

simple hemlock
#

Is it possible to fix this somehow or will I have to delete my account, or will this not help?)

wary ravenBOT
#

Flagging this thread. A team member will be with you shortly.

simple hemlock
#

ok thanks, I'll be waiting)

simple hemlock
#

I apologize for writing again, I would like to know if it will be possible to do something today?)

simple hemlock
#

If it’s possible to disable all versions of the bot so that I can enable the new version, now when you enable the new version, 2 options work at once, I tried to disable the github from the account and completely deleted the project, but it didn’t help, here’s the ID of the old project 548e4234-0783-4ae9-9bef-fd491030d8b8 , I think the old one works on it version

unique cloud
#

this is caused by a phantom container, no amount of deleting projects will help, I've asked the team. if you can't wait and want a solution this instance, regen your bot token and the bot that's currently running will eventually fail and be kicked offline

simple hemlock
#

well, thanks for the idea), I will wait of course and the answer from the team))

unique cloud
#

If I was you, id regen my bot token anyway

simple hemlock
#

ok

simple hemlock
#

unfortunately this method did not help, I updated both the tmi token and the id client, but the old bot continues to work(

unique cloud
#

@old trellis sorry for the ping

old trellis
#

no worries,

#

we actually are meeting about this topic right now as we speak

unique cloud
#

that's funny

simple hemlock
#

hello, I still don’t know what else to do to disable the old version of the bot, it still works, even changing tokens and id didn’t help, it’s very strange, this is the first time I’ve encountered this, before that everything worked fine for a couple of months.

woven jay
#

I updated both the tmi token and the id client, but the old bot continues to work(
Did you remove/invalidate the existing token? What bot is this?

simple hemlock
unique cloud
#

damn twitch you letting people use invalid tokens

simple hemlock
#

usually if the token is not the right one, it immediately gives an error when connecting, but it turns out that both the old one and the new one work, or the twitch saves the client id and tmi token until it is disconnected from it, even if a completely new one is created, very strange

glossy elm
#

Update on this. We were able to find the phantom container that wasn't properly terminated and stopped it. We're looking into why this one didn't get cleaned up properly