-
Notifications
You must be signed in to change notification settings - Fork 731
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Colab Account Access Blocked due to "suspected abusive activity" #4979
Comments
+1 Same here Yestreday I started my first colab project. I uploaded 10 training image data using YOLO8. I started my Jyputernotebook instructions from the beginning. In few minutes I got the above error that account is blocked. |
Same issue here. Just started Yolo and getting :
|
Same issue here. YOLO model.tune run... |
Same issue here I was running Yolov8 and all of the sudden I had this issue.Just 10 mins before I have subscribed to Google Colab Pro for the utilisation of GPU and this what happened |
Same issue. Model training. Unacceptable. |
Same issue here! Basic model training is suspected abusive activity |
Same issue, running YOLO11, not even five minutes after I started working on it. |
same issue here |
Same issue happened here in the middle of doing a run that uses YOLOv8 on 4th December 20:00 UTC |
same issue here |
The same problem |
I have the same issue I was running YOLO and I just got blocked when I have a hard immediate deadline! This is not acceptable Google should take full responsibility for all these problems it is causing for a bug! This is causing serious problems for me. I am also a Colab Pro user! |
same issue here |
Same issue here |
same here |
same issue here |
1 similar comment
same issue here |
Same issure here.. can someone help me understand whats happening... because i just got banned from both Kaggle and colab... |
Me too. i got banned both too |
i was training a model to detect guns in footage... is the ban due to that or something |
Me too. I was using a dataset from Roboflow and training a YOLOv11 model for car damage detection. |
I just started testing the platform and within a few moments got that same message |
I was just trying to start training the yolov8n model, but I received a message that my account was blocked. |
When I work with the .yaml file in the data downloaded from Roboflow, my account is immediately blocked. |
Same here, account banned for trying to do a simple prediction model on |
same here, I was trying to load the YOLO11 model. (Colab Pro sub) |
Same for me! very frustrating. any solution? Trying to just load pretrained yolov8 model. |
Same here, I'm also using the YOLOV8 model. |
me too! I was training using yolov8 and a custom dataset from roboflow, suddenly the runtime was interrupted at the moment “Overriding model.yaml nc=80 with nc=54”.
even though last night I ran the same notebook without any problems |
Please uninstall Ultralytics To uninstall ultralytics:
You can safely install Ultralytics through the following commands:
or:
Just fyi, I'm from Ultralytics, we just recently found out about this issue. |
thank you but my colab account is still banned.
|
@williamsaung I am not from google colab, I sadly can't do anything about your account being banned. |
Same here, my account is still banned... |
again banned after an hour |
@praths71018 Please see my comment here: #4979 (comment) |
anyways , it works after i tested again with my alt account. Thanks |
How to get an account unblocked due to this annoying error? Or is the account blocked forever? |
The compromised Ultralytics package version has been removed from PyPi, it should be safe to install Ultralytics again. |
I'm able to run notebooks on Colab Pro+ again. Thanks @Skillnoob for the updates and transparency on the situation. |
How to get an account unblocked due to this annoying error? Or is the account blocked forever? |
why my account is not unblocked then? |
@cperry-goog How to unblock the account which got banned cause of this error? |
I submitted an appeal yesterday at 20:00 UTC. Did you submit an appeal and when? I also didn't try to run anymore notebooks on Colab since 00:00 UTC, so it's been 9 hours without activity on Colab for me. |
How can I get my account unblocked? I recently purchased computing units and would like to regain access to use them. |
yes i did file an appeal. its been 4 hours |
My account is still blocked |
Just got to have patience it will be resolved, unfortunately someone put malicious code into something for some mining. |
My account is still blocked colab and kaggle |
Thanks to Ultralytics, you all just tried to run a crypto mining through Colab, it's not like you be magically unbanned |
The current package on PyPi is safe, more informatio can be found here: |
Do we also get a public response what the f happend? Still, great problemsolving! |
Considering I've been banned twice now, you're absolutely sure that the current package is safe, right? |
If you want to be extra sure, you can install ultralytics from GitHub source code instead: !pip install git+https://github.com/ultralytics/ultralytics |
IMPORTANT: Delete any ultralytics==8.3.41 and ultrlaytics==8.3.42 versions that may be installed locally as these are both affected. ultralytics<=8.3.40 is safe. |
Yesterday ultralytics released 8.3.41, which contained malicious code that could be used for cryptocurrency mining. Automated Colab abuse detection picked this up and began banning unsuspecting ultralytics users who installed 8.3.41 and started training with that version. We noticed this uptick in bans, but we had made no recent changes to our configs, so were unable to immediately diagnose the issue. Late in the day our Backend TL hopped on while on vacation and root-caused the issue and reported it upstream: ultralytics/ultralytics#18027 - ultralytics subsequently removed 8.3.41 (and briefly, 8.3.42) from PyPI. We have unbanned all users impacted yesterday, and this issue should be resolved. A big thank you to all users who reported this. We'll have an internal post-mortem to see if we can better avoid these types of attacks in the future. |
I'll keep this issue open for another day or two just in case we see a repeat, please do comment if you see issues. |
Curious did this help Bitcoin hit it's milestone?
…On Thu, Dec 5, 2024, 11:54 cperry-goog ***@***.***> wrote:
I'll keep this issue open for another day or two just in case we see a
repeat, please do comment if you see issues.
—
Reply to this email directly, view it on GitHub
<#4979 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5KVBEYUWYLQEEETHOLKOA32ECHOPAVCNFSM6AAAAABTBIWZ6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRRGA3DAMZTHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
my account is still being blocked, please assists |
Im still not able to connect to a Colab runtime. I filed two appeals yesterday. Is there anything else I can do to get my account unblocked? |
For the last few days, I've been running two different machine learning tasks, for two projects I have due in the next few days. One was a notebook fine tuning a reinforcement learning agent I've been training on the game 2048, and the other was a notebook that loaded and ran a YOLO image detection model from ultralytics. The latter program also loads a dataset of images from the Places2 challenge website, which is about 20gb of images. However, since I was using Colab paid units, and as of today I still have over 100 of them, I was under the impression that this was okay.
Today, about 10 minutes into running the program, I was suddenly cutoff from the runtime and received the following message:
Connection failed
This account has been blocked from accessing Colab runtimes due to suspected abusive activity. This does not impact access to other Google products. If you believe this has been done in error, review the usage limitations and file an appeal.
I've submitted an appeal, but haven't received any confirmation of it having been received or acknowledged, and I need to be able to access Colab runtimes for my schoolwork. Is there any way of finding out more about this issue, and how I can get it fixed?
The text was updated successfully, but these errors were encountered: