Beiträge von ñull

In LC ist es unmöglich nachträglich die Verzeichnisse von die FTP Konten zu wissen, weil sie nicht aufgelistet werden und auch nicht nachträglich veränderbar sind. Könnte man das bitte nachbessern?

+1 Stimme

Habe ich auch bemerkt und diese Möglichkeit vermisse ich auch.

Hier wird Bind noch immer nicht LC gesteuert u.A. durch diese unbeantwortete Frage. Diese Einträge nachträglich bei viele Domains einbringen bedeutet viel Arbeit.

Yes as workaround the "string" format can be chosen. The 500 error was caused by something else.

I try to use the php.ini manager to set always_populate_raw_post_data = -1, as the php documentation is instructing me to do here: https://php.net/manual/en/ini.…ys-populate-raw-post-data

Unfortunately LC is not able to create a valid value because the site fails with an error 500. This most likely needs to be a number without quotes (not a string) and the manager fails to accept negative numbers.

Now I need to compile a lower PHP version to make this work, because the impossible permissions make it very unpractical to change the the conf/php.ini manually.

Dear KK,

Some of us use custom settings or overridden LUA functions. Would it be possible in future tickets and changelog to include the LUA file name that changed? This is important to keep customisations in sync with the update.

Thank you,
ñull

Danke! Das sieht viel versprechend aus.

Ich habe gerade das hier entdeckt. Wäre schön wenn auch LC das unterstützen könnte.

Wie begrenzt man am besten in oder mit LC den Zahl der php-cgi die gleichzeitig laufen und dem Speicher verbrauchen.

I notiice that before a newly upgraded LiveConfig is started a security backup is made of the SQLite database, even when LiveConfig is configured to use a MySQL database. It would be nice this backup code would check the database that is actually used and then use the right database when making the backup.

I noticed one problem. For some weird reason apparently the MySQL database connection was broken (did I reset the password; I don' t remember). For this reason the databases of the contract were not deleted. May be this was the cause that contract delete errored out and did not finish successfullly, but in the front end I did not see any error of this. I should have been warned that something is wrong and the contract should not be deleted.

I don't remember, but I might have deleted the databases manually before deleting the contract.

Further information for this bug.

Liveconfig's database is under MySQL and when I look in the table HOSTINGCONTRACTS then I can find back a row for this client. So what happens is that in the web frontend the contract disappears from the list but the backend the ccontract still exists. I will change the title accordingly.

It says: To delete this customer, you first need to delete all assigned subscriptions.

... but the list of subscriptions is empty.

How would you safely delete the related contacts? Contacts can be in use for other clients.

When you create a new FTP account, you can indicate, beside username and password, also the path. When the FTP accounts is already created, there is no way to verify the path because it is not listed, nor visible when you edit the password. Please could you add this small feature? It will help us in user support and it will help the user to know where he will access the server.

Two use cases:

• The typical emails automatic notification emails with no-reply@emailaddress.com. Probabably will have a reply-to header, but some user can still start using it and I just don't want to clean out the mailbox
• A billing software like WHMCS can only associate clients with email addresses. Some clients just don't want to receive emails or don't want to give an email address. I create a unique email for them, because WHMCS cannot do without, but I don't want to see emails nor see them bounce.

Both make sense to me and while they might be illegal in the strict sense, nobody is really bothered by this use.

Meanwhile I found a way to create a blackhole address:

• Add this line to /etc/aliases:
  
  
  Code

  null: /dev/null

  
  

• Compile the changes by running:
  
  
  Code

  newaliases

  
  

• Make a custom virtual alias file /etc/postfixt/virtual_alias_custom with:
  
  
  Code

  null@existingmaildomain.com  null@localhost

  
  

• Take care that the file permission and owner are the same as /etc/postfix/virtual_alias and then run in the /etc/postfix directory:
  
  
  Code

  postmap virtual_alias_custom

  
  virtual_alias_custom.db should appear now.
  

• Modify /etc/postfixt/main.cf to include this new file:
  
  
  Code

  virtual_alias_maps = hash:/etc/postfix/virtual_alias hash:/etc/postfix/virtual_alias_custom

  
  

• Restart Postfix

I would like to create a black hole email address. Can you do that with LiveConfig? How?

If I would follow these instructions would LiveConfig accept a redirection to devnull ?

When a administrator or reseller logs-in as other user, in the right top corner appears the "abmelden" button and this is not translatable, at least, I could not find it in the pootle site.

The translation of this is impossible in Spanish and even in English it is shaky, especially when the variable is used. As example translation of the string "Invalid secondary name server #%i selected".

In English it is linguistically weird to speak about a primary, first secondary, second secondary or third secondary server. It would be better to speak about first, second, third, fourth etc.

What is weird in English is utterly rediculous in Spanish. In Spanish nobody says first secondary, second secondary. Unless you change things I cannot find a good way to the example string to Spanish and I am sure there are other languages where is not acceptable.

Because of the previous bug I wanted to password protect my database maintenance tool which is installed as an application. "Password-protected directories" does allow you to enter an absolute path /var/www/user/apps/myapp (I did not see any error message) but this won't protect it.

Could you please add a feature to also protect application paths?

Now even when you fully disable HTTPS, it still responds with the same database administrator. This means that just https access to any domain will show my database administrator. I consider this is a security risk.