Tnx it worked.
Posts by web4you
-
-
After manual run
certbot renew
i got a new cert in /etc/letsencrypt/live/
checked with
openssl x509 -noout -text -in /etc/letsencrypt/live/admin.web4you-server-02.web4you-gmbh.ch/cert.pem
and this is valid till nov 23 but a check on ssl-trust.com is still showing my old cert.
-
Latest Release: 1.5.3 (2018120800)
New trouble with Letsencrypt. All standard domains are working well with Letsencrypt. But my admin panel does not:
After a manualy run of (as root)
perl /var/www/imscp/gui/plugins/LetsEncrypt/cron/renew.pl -dv
I cant login anymore to it. So i opened the database by shell.
select * from letsencrypt WHERE DOMAIN_NAME = 'admin.web4you-server-02.web4you-gmbh.ch';
tells me:
Challenge failed for domain admin.web4you-server-02.web4you-gmbh.ch
Some challenges have failed. at /var/www/imscp/gui/plugins/LetsEncrypt/backend/LetsEncrypt.pm line 834.
Letsencrypt_status is on "torenew"
Line 834 is:
: execute( [ $self->{'config'}->{'certbot_path'}, @certbotParams ], \$stdout, \$stderr ) == 0 or die( $stderr
$stdout );
Any hint?
-
Ok i fixed ist with
-
Latest Debian 9
All Updates
PHPSwitcher on php 7.3
Maybee not realy a i-mscp problem but i think so.
Last installed nextcloud 18.03. On the admin site i see "Es wurde kein PHP-Memory-Cache konfiguriert". "There is no memcache installed"
I used this manual: https://docs.nextcloud.com/ser…aching_configuration.html
I tryed apcu and redis. But no chance. Error is always:
Internal Server Error
The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.
And the nextcloud.log tells me:
/var/www/virtual/web4you-gmbh.ch/nextcloud/htdocs/status.php","line":38,"args":["/var/www/virtual/web4you-gmbh.ch/nextcloud/htdocs/lib/base.php"],"function":"require_once"}],"File":"/var/www/virtual/web4you-gmbh.ch/nextcloud/htdocs/lib/private/Memcache/Factory.php","Line":98,"Hint":"Is the matching PHP module installed and enabled?","CustomMessage":"--"},"userAgent":"Mozilla/5.0 (Linux) mirall/2.6.4git (Nextcloud)","version":"18.0.3.0"}
{"reqId":"SFR4hiQNskWG9pFNuEYF","level":3,"time":"2020-03-28T08:00:15+00:00","remoteAddr":"91.138.47.31","user":"--","app":"remote","method":"GET","url":"/status.php","message":{"Exception":"OC\\HintException","Message":"Memcache \\OC\\Memcache\\APCu not available for local cache","Code":0,"Trace":[{"file":"/var/www/virtual/web4you-gmbh.ch/nextcloud/htdocs/lib/private/Server.php","line":625,"function":"__construct","class":"OC\\Memcache\\Factory","type":"->","args":["11e55c1268545b94a0872bd893601f57",{"__class__":"OC\\Log"},"\\OC\\Memcache\\APCu","\\OC\\Memcache\\APCu",null]},{"file":"/var/www/virtual/web4you-gmbh.ch/nextcloud/htdocs/3rdparty/pimple/pimple/src/Pimple/Container.php","line":118,"function":"OC\\{closure}","class":"OC\\Server","type":"->","args":["*** sensitive parameters replaced
I tryed to install php7.3-apcu and this follows
apt-get install php7.3-apcu
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Hinweis: »php-apcu« wird an Stelle von »php7.3-apcu« gewählt.
php-apcu ist schon die neueste Version (5.1.18+4.0.11-1+0~20191219.13+debian9~1.gbpa99079).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
So i think php is using php-apcu instead of php7.3-apcu and this could be the case.
How to correct this ??
-
I have the same error here with this pyton version 2.7 also after update the certbot-auto. What realy can i do now?
-
Ok - die haben mich jetzt wieder freigeschaltet.
joximu Das wollte ich auch so machen. Habe aber ständig
dsn=4.7.1, status=deferred ....Relay access denied (in reply to RCPT TO command))
Meine smtp_aut
smtp.quickline.com:587 [email protected]:passwort
und die main.cf
#ohne MX-Auflösung:
relayhost = [smtp.quickline.com]
#SMTP mit SASL-Authentification verwenden
smtp_sasl_auth_enable = yes
#Die Passwort-Datei
smtp_sasl_password_maps = hash:/etc/postfix/smtp_auth
#Identifikationsmethode:
smtp_sasl_security_options = noanonymous
-
Ja klar. Ist noch in Arbeit. Das dauert ja ewig.
-
Ich habe neuerdings folgende Probleme mit Kunden, welche Emails an oder via Microsoft.com versenden. Meine Server IP wurde auf Microsofts Blackliste eingetragen und ich hab keine Ahnung weshalb. Nachdem ich das Formular auf microsoft augefüllt hatte bekam ich folgende Email:
Dear Juerg Schwarz
We have completed reviewing the IP(s) you submitted. The following table contains the results of our investigation.
Not qualified for mitigation
5.9.210.214
Our investigation has determined that the above IP(s) do not qualify for mitigation.
Please ensure your emails comply with the Outlook.com policies, practices and guidelines found here: http://mail.live.com/mail/policies.aspx.
To have Deliverability Support investigate further, please reply to this email with a detailed description of the problem you are having, including specific error messages, and an agent will contact you.
Regardless of the deliverability status, Outlook.com recommends that all senders join two free programs that provide visibility into the Outlook.com traffic on your sending IP(s), the sending IP reputation with Outlook.com and the Outlook.com user complaint rates.
Junk Email Reporting program (JMRP) When an Outlook.com user marks an email as "junk", senders enrolled in this program get a copy of the mail forwarded to the email address of their choice. It allows senders to see which mails are being marked as junk and to identify mail traffic you did not intend to send. To join, please visit http://support.msn.com/eform.a…s_form_byemail&ct=eformts.
Smart Network Data Services program (SNDS). This program allows you to monitor the ‘health’ and reputation of your registered IPs by providing data about traffic such as mail volume and complaint rates seen originating from your IPs. To register, please visit http://postmaster.live.com/snds/.
There is no silver bullet to maintaining or improving good IP reputation, but these programs help you proactively manage your email eco-system to help better ensure deliverability to Outlook.com users.
Was muss ich da machen?
Ach ja und hier die Fehlermeldung beim Kunden:
This is the mail system at host web4you-server-02.web4you-gmbh.ch.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<[email protected]>: host
hotmail-com.olc.protection.outlook.comhttp://mail.live.com/mail/troubleshooting.aspx#errors.
[HE1EUR01FT030.eop-EUR01.prod.protection.outlook.com] (in reply to MAIL
FROM command)
Reporting-MTA: dns; web4you-server-02.web4you-gmbh.ch
X-Postfix-Queue-ID: 59E69288009E
X-Postfix-Sender: rfc822; [email protected]
Arrival-Date: Thu, 30 May 2019 21:40:53 +0200 (CEST)
Final-Recipient: rfc822; [email protected]
Original-Recipient: rfc822;[email protected]
Action: failed
Status: 5.7.1
Remote-MTA: dns; hotmail-com.olc.protection.outlook.com
Diagnostic-Code: smtp; 550 5.7.1 Unfortunately, messages from [5.9.210.214]
weren't sent. Please contact your Internet service provider since part of
their network is on our block list (S3140). You can also refer your
provider to http://mail.live.com/mail/troubleshooting.aspx#errors.
[HE1EUR01FT030.eop-EUR01.prod.protection.outlook.com]
Return-Path: <[email protected]>
Received: from [192.168.0.150] (unknown [23.233.135.169])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
(Authenticated sender: [email protected])
by web4you-server-02.web4you-gmbh.ch (Postfix) with ESMTPSA id 59E69288009E
for <[email protected]>; Thu, 30 May 2019 21:40:53 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.11.0 web4you-server-02.web4you-gmbh.ch 59E69288009E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wips.ch; s=mail;
t=1559245256; bh=TA+GgCCq5UwKzJb6ZL6mcud2wcXFWfHxxzoLLLUoZs4=;
h=From:Subject:Date:References:To:In-Reply-To:From;
b=rSlzLUSnX7nj/UDWsxYvSLfFgKXnPq6XNOqx1xqcUNI/6E5mCBz95sr7wnu7B3JKQ
Vq89uFi0ewpFRCFVKULQWSM0YBrS/uOFTJVVAu+va3265anH8IaBTPLpQlkkJdLW+j
HG/jlmaIV39wMzeren9Rfk3bdICiUUbndwazhQ5M=
From: heidi <[email protected]>
Content-Type: multipart/alternative;
boundary="Apple-Mail=_C2E81791-47AE-4885-A443-3D6B3307E976"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: =?utf-8?Q?Re=3A_K=C3=BCchenchef_Stelle?=
Date: Thu, 30 May 2019 15:40:51 -0400
References: <[email protected]>
<CY4PR0601MB36989B827767CFCAF5D22782A9020@CY4PR0601MB3698.namprd06.prod.outlook.com>
<CY4PR0601MB3698435FC03EF55CDC11070DA9030@CY4PR0601MB3698.namprd06.prod.outlook.com>
<CY4PR0601MB36989B8DABEB3F14EFEBF55FA91C0@CY4PR0601MB3698.namprd06.prod.outlook.com>
<CY4PR0601MB3698823C24AF49040BD229C5A91E0@CY4PR0601MB3698.namprd06.prod.outlook.com>
<CY4PR0601MB3698F84054D24E8D759DDA03A91E0@CY4PR0601MB3698.namprd06.prod.outlook.com>
<CY4PR0601MB3698061E033C335E4BB95269A91E0@CY4PR0601MB3698.namprd06.prod.outlook.com>
To: mariano liuzza <[email protected]>
In-Reply-To: <CY4PR0601MB3698061E033C335E4BB95269A91E0@CY4PR0601MB3698.namprd06.prod.outlook.com>
Message-Id: <[email protected]>
X-Mailer: Apple Mail (2.3273)
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,
T_KAM_HTML_FONT_INVALID,URIBL_BLOCKED autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
-
Das Roundcube Plugin. Und dort muss in der config.php der Punkt "managesieve" auf "yes" gestellt werden.
Wenn Du das Plugin schon installiert hast aktiviere den Punkt in der config.php und klicke im Panel unter "Plungin Verwaltung" auf "Plugins aktulisieren".
Danke - das hatte ich alles schon durch. Nach einem erneuten aktualisieren mit 'no' beim managesieve_plugin hatte ich dann mal nicht mal mehr den Filter zur Auswahl. Erst nach einem weiteren 'yes' war dann auch der Urlaub wieder da.