Did you look at the screenshot? There are no quotas. Your data is wrong.As far as the incorrect data, are both accounts in your screenshot not near the 512M quota?
So cPanel is now forcing upgrades to Edge releases?I spoke with the User Interface team and confirmed there is not currently a way to remove that option. That sounds like it would make for a good feature request if you would like to submit on using the link in my signature.
RELEASE | 104.0.4 | A version that is feature-complete and well tested | ||
CURRENT | 104.0.4 | A “release candidate” version that is tested but may not be feature-complete. | ||
EDGE | 104.0.4 | A development version for testing only and not for production servers. |
What about the wrong data?No, it's just that we haven't released a new Edge version yet and 104 has moved up into the more stable tiers. 106 will be coming along soon for Edge. This just happens to be one of those times when a lot of the tiers have the same version since 102 was recently promoted to LTS.
judging by the likes of my first post it's not just my machines (its happening on both servers). It's SUPER weird that this "upgrade opportunity" is implemented with no way to disable it. If your user interface team wants me to ignore the incorrect data, they should widen the data cell so it does not make a mess in the listing of accounts. Thanks.Since it was only a partial screenshot I couldn't tell there were no quotas. I did setup a test machine without quotas and I'm not seeing that message on my end when there is an account using 512M, or more, of disk space.
Since we might need to see this in action on your specific machine, could you submit a ticket to our team so we can check that?
did you set up the accounts under 102 and then upgrade to 104? Thats the only way to truly test it. Thanks.I did setup a test machine without quotas and I'm not seeing that message on my end when there is an account using 512M, or more, of disk space.
ok.. I will figure it out eventually. Thanks.Yes - this has been a test server for a bit and was on 102 previously.
ok, the "bandwidth exceeded" warning can be fixed by unticking the "unlimited" setting in a package and setting a super high limit. save it. then go back and click "unlimited" again and save. 104 does not seem to be respecting the "unlimited" tick after an upgrade. This fix does not work for the "5120000 blocks exceeded" warning. Hopefully this will be fixed in an update as it looks sloppy.Yes - this has been a test server for a bit and was on 102 previously.
Yep I have the same issues with incorrect bandwidth exceeded warnings...which is something I never wanted to be notified of anyway. I also see this 5120000 blocks exceeded which is useless to me... seems like this particular warning should be more obscure. I don't know who is in charge of product design over at cPanel, but I would like to have a serious conversation with themI'm in the same boat as the rest, I have a few domains that show incorrect data such as bandwidth exceeded when in fact those domains hasn't been use for the last 2 months, plus the "5120000 blocks exceeded", that got my eye twitching, what is this refers to? is this like the node cap on cloud linux? if so, then is more wrong because we/I don't use cloud...
Thread starter | Similar threads | Forum | Replies | Date |
---|---|---|---|---|
S | cPanel 102 EOL | Installation & Updates | 3 | |
G | Cpanel elevate Alma Linux 8 | Installation & Updates | 1 | |
S | cPanel DNS Confiuration - OVH VPS with AlmaLinux 8 | Installation & Updates | 1 | |
Y | Imagemagick on cPanel | Installation & Updates | 2 | |
W | SOLVED Cloudlinux 9 and cPanel | Installation & Updates | 3 |