webtiva said:Same thing. Going in under :2086 and resetting does nothing... Logging a ticket...
if you need stability then running EDGE isnt advisableOCX said:please let me know if your issue gets resolved and how they did it.
this is getting to be PURE BS!!!
i got clients up my ass because cpanel cant leave workin scripts alone or code it correctly and test before they release..
im reallllllllllllllllllly ready to go to another controlpanel system..
I just happened to upgrade some of my servers almost immediately after they released a new build; I noticed a bit too late they fubared the update. It seemed to cause a problem with some SSL libraries (libssl).chirpy said:I had this too when I upped all my servers. Had to put them back down to RELEASE to get into WHM on about 75% of them. Ah, the joys of bleeding-edge. If you need to run EDGE, log a ticket with cPanel/create a bugzilla entry.
Running bleeding edge software is so much fun (sarcastic :p); hooray for EDGE (perhaps it's best left to our personal servers).chirpy said:Indeed. EDGE is EDGE and you accept the risks if you decide to use it.
I usually lean towards the CURRENT builds as for myself.dave9000 said:looks like they borked several things in the latest edge, rolling mine back to release
I got hit with this one on a few boxes. True EDGE is EDGE ..it's not unstable ..it's just you never know what you are going to get when you update it.chirpy said:Indeed. EDGE is EDGE and you accept the risks if you decide to use it.
Out of interest Dave, how did you find this information. For years I've looked at the changelog but it seems to be pretty much dead now adays.dave9000 said:usually I have little to no problems with EDGE but lately they are trying to get everything ready for apache2 and clustering and lots of bugs getting through to EDGE
This latest update is a disaster which is unusual for cpanel. I figure they will get it sorted out in a few days and then I will go back to edge