Search results

Came here to report the forwarding issue. Yes, clicking the add works, but it is very confusing to have to press that Add button at the top, if you're not going to add another forwarder.

It's not like they break the typical LAMP stack.. oh wait :unsure:

Yes, the problem here is that this falls outside of DirectAdmin and that you need to have shell access. Plus know a little bit about how Linux works.. Here's an example of how the public_html folder was set up for a customer of mine that uses Laravel: $ ln -s laravel/public public_html...

Hi, Laravel expects a different folder structure than the one that DirectAdmin creates. In DirectAdmin delete the "public_html" folder and then create a symbolic link from "laravel/public" to "public_html". -- Wil

LOL

You got at least one thing right.. this is about trust.

Well they do manage to alienate an existing customer base, personally going from "fan", to "never again", so that's at least a win.

It starts with MariaDB and before you know it, it will apply to other parts as well. It won't stop at MariaDB.

Not me.. it's their server. I just recommended to them to use DirectAdmin for easier management. They can use it, but it has been artificially limited. I never complained about the money. They would happily pony up more, but not if you change the terms one sided on existing contracts. It might...

Just checked a server of a customer of mine. They are on a Personal license, valid until 06/24/2024 The license reads "Legacy license", so they are in this too? I won't be able to explain that to them. Guess I'll end up moving them off DirectAdmin as they don't really need it anyways.

Make it yearly and I'm in. Also communicate upfront about this type of thing. Finding out about this mess in the forum is really not the way to notify your customer base about changes in licensing. This is stressful for everyone involved.

Well I can live with having to pay some money to keep the legacy "lifetime" licenses supported. Nobody can work "for free" and I think many will understand that lifetime licenses must have a limit somewhere. But this is not the way to communicate that.... the main issue I see here is how it is...

It's a breach of trust. So even if we buy the upgrade who is guaranteeing us that they will not play a similar shenanigan again? This not bode well for trusting a solid future. And all of that's on top of the current unstable upgrade scheme's we are already facing. It was a SUPER stable...

Another vote to keep cURL as it was. IMO it falls in the same category as apache. The OS supplied cURL version is too far behind feature wise. There are new features all the time.

@sparek, some more discussion in this forum about autopatch, see https://forum.directadmin.com/threads/directadmin-v1-643-has-been-released.67014/post-352620

lol, OK. It was probably the first thing I noticed on what changed.

I did actually read the "list of changes" for 1.643 before I posted that. Was that missed or did I overlook something?

FWIW, since 1.643 the browser session no longer times out for me. Not even after not using the browser tab for a whole day. Coming back to it, the next day I can just continue where I left off. Kind of convenient, but.. might not be as safe as an automatic logoff after nnn minutes. Firefox...

OK..I suppose I can live with that, as long as it is a hot patch for the same release. But please do store this in logs and the message system. Without that we are driving blind.

I see the same on 2 servers.. nothing in the logs and I NEVER have automatic updates as I want to know when to update so I can plan updates. This is not OK.