Richard G
Verified User
I thought we all already agreed that this period is very short and possiby DA did not think that over well enough.
Important: Upgrade your DirectAdmin to ensure compatibility with our new licensing system
- Thread starter DirectAdmin Sales
- Start date
Thats the thing it hasn't been one month.. its been 9 years.
The question isn't about working. Its about supported. Who cares how long it worked that is no measuring stick..
There are plenty of cars still running without a warranty, when it breaks and you need something fixed. They might say we cant or it going to cost you this or buy another car.. your standing on the side road saying "it worked the last 300,000 miles" I don't want to get a new car...which doesn't solve the problem you have..
The answer is make a choice.. you have a delema to solve. Instead of talking to me you need to start planing on what to do..
Don't change anything if you don't want to... I get your frustration but the frustration is not DAs fault. Even if it was DAs fault you still have to do something.
yes, it`s DA fault. My licence last time updated 31 January for 30 days. I don`t read every post in this forum. At DirectAdmin system there are message about DA updates only: "This OS is now end-of-life. Future automated updates may fail.". I didn`t have any information about licence updates end-of-life. So I have 1-2 days to find solution, because customer will see "License has expired" message and you think this is normal?
Like I said it really doesn't matter what I think.. I am just a customer like you. I just happen to believe in staying updated and other people don't. Since I beleive in this I am not running around all mad and worried.
That is your choice. Are you not reading redhats, cpanels, whmcs, debians, freebsd and others information? If not you should but again you don't have to do anything.
You have had 9 years. You are on CentOS4 even if you didn't read this forum. You knew or know that version is EOL and has been for 9 years. If you didn't ever think this day would come well that a bit short sighted.
Again since you dont have alot of time I would stop posting and get busy doing something.
question is just about DA support position. I think there are many solutions help DA users to solve this problem with licence update and keep older DA version working like other EOL software (CentOS, Apache, PHP, etc.).
Richard G
Verified User
I think that is not completely correct. If you look at the announcement about the license change which creates this issue, that announcement is from December last year, so until this came in effect it's only 1 month. And that's a short period. Especially if you know that it's quite normal for a business not to visit a forum very often. Especially if the software is working nicely and people think they have a lifetime license which they don't expect to suddenly stop to work (stop to update yes, but not stop to work).
As you can see from my post I disagree. I am willing to listen to you about why.
The issues is created by the inability of people to keep the systems in their care updated. If the systems in question were on a supported OS there would be no issue. So therefore the issues is not the announcement or the application.
Again that is the Application of DirectAdamin and it requires a current supported OS. I have many Lifetime Licenses and I don't expect any of them to work on CentOS 6 or lower. Nor would I even uses these old ancient OS's. I also don't expect them to work on FreeBSD anymore.
DA even went backwards an entire OS level to help even though these OS's are EOL. "Please note: 1.63.X binares are available on CentOS 6 and Debian 8." They were very clear here "Upgrading your operating system to one we support is the only solution." even though they didnt have to be.
I was mad went FreeBSD was dropped. I moved on I switched to Debian. Did I like it no.. Did have to move on yes..
Sorry I don't get the argument.
Richard G
Verified User
Yes for support and updates. Not just to function. Seems various users were able to just have this running on older OS versions, so Centos 6, 5 and even 4.
Ofcourse there are multiple kinds of lifetime licenses in the world.
But since this was possible, it gave the (wrong) impression to the users, that if you did not update, the current version (whatever version that was) would work lifetime.
As also is the same with the lifetime license of vBulletin which I had, until VB declared it end of life with version 3.8. However, my license still is lifetime and there will be no support and upgrades, but I could still install and use VB 3.8 on a server with php 5.6 or 5.7.
So it's not that odd that people thought it would keep working this way, since it has been working like that for a long time for some.
And looking at it this way, it's only a 1 months notice.
You know I agree with you that people shouldn't use old stuff and keep up to date, but even I did not expect that suddenly an older DA lifetime version (like for example 1.25.4) would just really totally stop working, because of a license check change.
And that is the big change which was only a month notice. So maybe now you understand why.
Also, it was never that clear that older versions of lifetime licenses would stop working. I can't remember any earlier announcements about that either, especially not in the topic about the announcement that lifetime would not be sold anymore, which also gave 3 or 6 months time to still buy them.
Again, I'm not saying DA should keep supporting that, but at least find some method so they can use it longer, to be able to make the necessary changes to be compatible with the new key system.
I think it is ok that DA stops supporting the old licensing system. But it would be nice if they warned it a little bit earlier that this day was coming. Just received a message from my server a few weeks ago. I’m happy the license that I got is still good till 23th of March.
One server i missed and is now expired. Sadly unable to download a new license. But only contains a few sites which I will move to my new server this week.
My plan was already to empty those servers this year because os was EOL.
But DA can see that I still have active servers that will not supported anymore. Why did they not mail those people a few months ago? Just to give people some time to upgrade things.
I also wonder is it safe to manual upgrade directadmin on a expired os? Just to get controlpanel working for a short period? I see it has instructions how to do a manual upgrade. But they also warn not to do that on expired OS.
One server i missed and is now expired. Sadly unable to download a new license. But only contains a few sites which I will move to my new server this week.
My plan was already to empty those servers this year because os was EOL.
But DA can see that I still have active servers that will not supported anymore. Why did they not mail those people a few months ago? Just to give people some time to upgrade things.
I also wonder is it safe to manual upgrade directadmin on a expired os? Just to get controlpanel working for a short period? I see it has instructions how to do a manual upgrade. But they also warn not to do that on expired OS.
Not really okay tbh. We are an ISP, and as much as we want to keep everything up to date, there are always customers that refuse to upgrade their VPS. If we knew about this, we could have informed our customers of those setups that their control panels would become inaccessible in the near future, and they would've been able to make a (forced) decision to migrate or not.
Now they don't even have access to their control panels anymore, so can't make a backup that way etc etc...
Now they don't even have access to their control panels anymore, so can't make a backup that way etc etc...
You may do the backup using command-line, like this:
https://forum.directadmin.com/threa...ot-working-license-expired.64928/#post-338103
Everyone should have received a message to their message system in DirectAdmin (January) and it automatically sends an email to admin's email as well.
we didn`t received any message to "Message System". So what will be workaround with licence update, if we can`t or don`t want to update DirectAdmin, but still want to use DirectAdmin features like "File Manager" etc.? It is possible to get custom licence.key from DA support for old DA system?
Base on how I read the documentation does require that. Maybe in the past they were nice and allowed people to unmaintain their system. Yes that lulled them into a false sense of security. So in that respect I agree with you its short notice.
Here is the only thing else I will add. DA should have sent a MASS email to all their customers about this. I do agree just posting in the forum isnt good enough.
In general though you shouldn't count on companies to have Your best interestat heart. We have countless examples of this.
Last edited:
yes, Microsoft could inform, that after 1 month all computers with Windows XP, Windows 7 or 10 will be EOL and stop to work, so you should buy new computer with Intel 8th Gen CPU, which support Windows 11
They could actually.. they own the licence and the system. We don't own the company. Companies do things they feel is in the best intrest of there business. XP and 7 are eol and have been for a while. So again no one should be using those systems. If they are well again its their fault.
But again your comparing apples to oranges.
Your running windows 98 and wondering why it stoped working. When MS told you years ago its EOL and not supported. Then 9 years after that they choose to really cut you off you had 9 years of Grace.
Again your wasting time you could have rebuilt several systems by now.
Last edited:
I already found solution, Portioned Licence appeared from 1.4x version, so there problem with 1.4x-1.63.4 DA versions only, all DA versions below 1.4x will work fine, because are valid till 2038 year and not require licence renewals as these new licences from 1.63.7 version. But I worry about DA cooperation in the future.
Well that might buy you some time to upgrade. So you went backwards to an even older DA codebase?
You should always worry about any companies cooperation and plan with that in mind.
IT_Architect
Verified User
- Joined
- Feb 27, 2006
- Messages
- 1,091
It is cruel to pull the rug from under people without having a preceding notification or license bump a couple months in advance to make ensure that people are notified.
I gotta say, this was my least favorite way to find out that you were going to break my production servers, after it happened. I guess refraining from updating DirectAdmin until I've thoroughly read the forum is the new procedure. Not cool. I updated all of my servers like a week or so ago and one of them just broke. CentOS 7, everything updated recently, server still broke until I ran getDA.sh current + ran the update licensing commands.
Edit: I posted quickly and I may have a modifier. I'm wondering if my DA updates had failed, it was run fleet wide and a two month old update (when not a security update) isn't really that long ago. With me being out so much in January (sick), maybe it's possible that I don't recall when I last confirmed an update, maybe I'm mixing up some memories?
Edit: I posted quickly and I may have a modifier. I'm wondering if my DA updates had failed, it was run fleet wide and a two month old update (when not a security update) isn't really that long ago. With me being out so much in January (sick), maybe it's possible that I don't recall when I last confirmed an update, maybe I'm mixing up some memories?
Last edited:
We have seen a few CentOS 7 cases where things just didnt take..
Try doing
yum update and upgrade
then run
./build update
./build update_da
I hope you are feeling better..
Maybe depends on your age...
