Posts by theemstra

A bit more detail would be nice & required to look further into your issue.

Please run that command and then rerun

Post the results here

No result after reloading apache/php-fpm?

Have you tried

You can set the plugin status to disabled or uninstalled in the database table for plugins.
What is the error that is generated? You can see it at the ?-mark on the plugin page.

At this moment we don't support LDAP, so you could wait for a supported version of i-MSCP that provides an API, but it's not yet on the roadmat (maybe @Nuxwin) can tell what version it's planned for. I think 2.0.0.
In 2.0.0 there will be an API, the control panel talks with the API to perform it's actions.

So for now I guess your best option would be your first idea. Create a drupal module that writes to the database directly.
Maybe nuxwin has more thoughts?

Hello @skeptic,

Thanks for your request.
Feel free to create a ticket on our ticket tracker (https://youtrack.i-mscp.net).
Then the i-MSCP team (usually @Nuxwin or @Ninos) will take a look at it and decide whether to develop this now, or in a later version.
My educated guess is that it'd be the latter.

If you're a developer, feel free to look thru YouTrack and look for things to solve.

Are the cron items still listed in the interface or database?
After the upgrade, did you re-enable the plugin?

Nice, that solves my issue

Quote from kess

I dont agree with you, at least not totally.It works correctly if you have 1 single server.

Example:
Server 1 : server1.mydomain.tld
Server 2 : server2.mydomain.tld

At present I have a record in the registrar DNS that tells:
*.server1.mydomain.tld A 1.2.3.4
*.server2.mydomain.tld A 2.3.4.5
So it works without intervention because every vuxxxx.serverX.mydomain.tld are transparently "created" or better, automatically resolved.

But if you remove the subdomain alias from the panel address:
First Problem: If you want to act like the Change Request, you have to setup each vuxxxx.mydomain.tld individually in your registrar DNS (at least for my case)
Second Problem: Who grants that vuxxxx can't be on both systems ?

Do you see what happens ?

Display More

I'd like to reply to the comment of kess, with servers that have multiple IP's, this might bring troubles.

Imagine this:
server1 has 1.2.3.4 and 1.3.2.4
server2 has 2.3.4.5 and 2.3.5.4

Now you use the same DNS records as mentioned:
*.server1.mydomain.tld A 1.2.3.4
*.server2.mydomain.tld A 2.3.4.5

Domains that are configured for 1.3.2.4 and 2.3.5.4 will now no longer load, because apache is configured for requests to a specific IP.

An option to overcome this problem would be to use specific IP-related DNS records, for ex:

*.ip1.server1.mydomain.tld in A 1.2.3.4
*.ip2.server1.mydomain.tld in A 1.2.4.3
*.ip1.server2.mydomain.tld etc etc

Another possible solution is the idea of @theqkash, even though he might not have meant it this way.
It could be testdomain.com.server1.mydomain.tld.
You could allow alias domains and subdomains this way as well.

Anyone else any ideas?

Maybe @Ninos can help you in German, I don't speak/write German