Beiträge von ñull

Bei aptitude safe-upgrade sehe ich jetzt:

# aptitude safe-upgrade
Resolving dependencies...                
The following NEW packages will be installed:
  liblua5.1-0{a} libopendbx1{a} libopendbx1-mysql{a} libopendkim9{a} librbl1{a} libunbound2{a} libvbr2{a} 
  opendkim{a} 
The following packages will be REMOVED:
  libapache2-mod-php5{u} 
The following packages will be upgraded:
  liveconfig-meta 
1 packages upgraded, 8 newly installed, 1 to remove and 0 not upgraded.
Need to get 603 kB of archives. After unpacking 7,875 kB will be freed.
Do you want to continue? [Y/n/?] n
Abort.

Nicht so schön wenn einige Kunden davon abhängig sind.

When logged in as admin, you can set the contact and associated email of the admin login user. This contact email is also the sender address of the password reset email. Not only for the admin but for all users that request a password reset. If you set your admin contact email for instance to a gmail address and someone with a gmail address tries to reset his password, he will get an email with:

from: my@gmail.com
to: client@gmail.com
etc.

When you client@gmail.com receives the password reset email it will end up in the SPAM box. When POP3 service is used to retrieve client@gmail.com emails, then it will go unnoticed. When IMAP is used the message will silently go in the SPAM folder and there will be no notification of new mail (bold folder name in Thunderbird; it is SPAM therefore no notification needed, right?) With large hosting companies, with many password resets, the server might even end up being blacklisted.

My suggestions to improve this to either have a full blown smtp client in Liveconfig that would allow sending email from any smtp server or an extra Sender address setting for password reset emails. May be the Sender email should be part of the email template configuration?

I can confirm that this bug is apparently fixed. At least I cannot reproduce it any longer.

Still doubting if that is the cause. It fails to reset correctly even with more complex passwords. I am glad that at least "PaSsWoRt" keeps working.

No two factor authentication and yes the latest version. But I now discovered the reason why command line password reset failed. Apparently it now tests for how complex the password is. I used a lowercase only password and it failed, without notifying. Then I used the PaSsWoRt like in the example and voila I could suddenly log-in. So please could you check that and let the comman-line password reset give an error message when the password is weak and not the - /usr/sbin/liveconfig: Password updated successfully.

This issue remains unsolved and is becoming more urgent now. It has repeated itself on a second test server, where the admin password spontanuously stopped working. Happily I could reset the password there from the command line. On my first test server it still fails to reset.

I just generated a new Let's Encrypt certificate at 7:21 UTC (that's what "date" returns from server command line) and in the SSL manager it appears as 6:21

Not very important because the certificate works ( I don't need to wait an hour).

SPAM abuse email comes in for my server IP. I need to respond quickly to build up my reputation. Would be nice to have some tools available for this. For instance:

• Easy access to mail account with high I/O traffic
• Ability to suspend mail account separate from subscription, if possible only blocking outgoing mail.
• Email template for "suspend mail" notification to client that is automatically sent when the mail account is suspended.

Logged in as administrator I go to Reports > Top-10 Subscriptions. In any of the three available displays when I click a subscription link I see:

Zitat

Error 500: Internal Server Error

An error occured while processing your request: Customer not found

Would be nice when that worked to quickly jump to email abusers.

Zitat von lebenszeit

Maybe old cookies?

No, to be sure I deleted these.

An old VertualBox developer LiveConfig was upgraded together with a lot of other packages. Then I tried to log-in as admin but it failed with the browser stored password. So I reset the password from the command line like instructed, with positive feedback that the password was reset. Then I try to log-in again but the failure persists. What to do now?

I wollte gerne einen Vertrag umändern mit nur Mailweiterleitung ohne Mailquota oder Postfächer aber wenigstens mit "abweichend" geht das leider nicht. Ich komme runter bis 1MB und 1 Postfach und kann deshalb kein Vertrag mit nur Weiterleitung machen. Stimmt auch nicht das keine Fehlermeldung oder Warnung kommt; Einstellungen werden einfach und lautlos ignoriert.

Ein Kunden hat zwei Verträge, einen Normalvertrag und einen Wiederverkaufsvertrag, was mich ermöglicht zu vergleichen was Mein Hosting so zeigt.

Bei einem Normalvertrag sehe ich Mail-Quota aber bei einem Wiederverkaufsvertrag fehlt es. Wie soll einen Wiederverkäufer jetzt wissen wie viel Mail-Quota ihm noch bleibt?

Wenn es möglich ist bitte diesen Fehler beheben.

In response to the security warning

https://www.imagemagick.org/di…viewtopic.php?f=4&t=29588

I wanted to proceed and deinstall php5-imagick but could not because I had this server installed with the liveconfig-meta package. Very handy to get a server up and running quickly, but see the disadvantage:

$ aptitude remove php5-imagick
The following packages will be REMOVED:  
  php5-imagick 
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 558 kB will be freed.
The following packages have unmet dependencies:
 liveconfig-meta : Depends: php5-imagick but it is not going to be installed.
The following actions will resolve these dependencies:


     Remove the following packages:
1)     liveconfig-meta             






Accept this solution? [Y/n/q/?]

Removing liveconfig-meta, as suggested, likely will remove all dependencies with it. In search of solutions I came accross this article: https://tanguy.ortolo.eu/blog/…e8/uninstall-meta-package

So it suggests me to do:

$ aptitude unmarkauto '?reverse-depends(liveconfig-meta) | ?reverse-recommends(liveconfig-meta)'
$ aptitude remove php5-imagick

This would get rid of the dependencies until the next update of liveconfig-meta. To prevent that future upgrades re-install php5-imagick I likely need to:

$ aptitude remove liveconfig-meta

I did not want to experiment with this on a production server, so I renamed /etc/php5/apache2/conf.d/20-imagick.ini and restarted apache

End of my adventure, but there remains the question, if there could be a package that installs everything but then does not oblige all packages to be present?

Thanks for fixing this.

When I reset the password on the command line or in the Web GUI to a very lengthy one (for security reasons), LC will not warn when it goes over the limit. The stored password is silently cropped and login will fail.

Instead of silently cropping, it should warn and refuse to reset. When there is a form limit in the GUI, then still a JS warning is appreciated because you won't notice this when pre-generated password is pasted.

Vertrag "Zurücksetzen" geht nicht weil Vertrags ID noch existiert (wie vorher schon gesagt, existiert noch in LC Datenbank). Habe auch probiert den Feld HC_DELETED auf 0 zu setzen. Vertrag erscheint dann wieder aber nach erneut löschen ergibt sich wieder dasselbe Problem das man den Kunden nicht Löschen kann.

Anscheinend geht was schief mit der Müllentsorgung, weil z.B. den wiederherstellte Vertrag Datenbänke wie gelöscht listet (durchgestrichen und mit Mülleimersymbol). Das heißt die Datenbänke dieses Vertrags waren auch noch immer da.

Ich musste LC Datenbank vom Backup wiederherstellen und Apache Konfiguration neu schreiben lassen. Ich wird aber nicht noch ein mal probieren den Kunden zu deaktivieren. Ist das überhaupt notwendig?

LC war nicht Deaktiviert, aber einen Proxy zu LC war zusammen mit alle andere Kundendomains deactiviert worden. Auf die richtige Adresse war er glücklich noch aktiv. Immerhin musste ich den LC Datenbank vom Backup wiederherstellen und LC die Apache Konfiguration neu schreiben lassen. Pfff..

Begreife aber noch immer nicht was schief gegangen ist.

Nach Deaktivierung einen nicht benütztes Kundenkonto sind jetzt alle meine Kundendomains deaktiviert und auch LiveConfig kann ich nicht mehr erreichen. Alles zeigt

Zitat

Webseite deaktiviert.

Diese Website wurde deaktiviert. Falls Sie der Betreiber sind, wenden Sie sich für weitere Informationen bitte an den Support.

Kann leider Keppler IT auch nicht erreichen. Wird schon eine traurige Nacht für mein Kleinbetrieb.