Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
20.7 Legacy Series
»
Sensei Scheduled reports FAIL
« previous
next »
Print
Pages: [
1
]
Author
Topic: Sensei Scheduled reports FAIL (Read 3211 times)
Darkopnsense
Full Member
Posts: 148
Karma: 6
Sensei Scheduled reports FAIL
«
on:
August 06, 2020, 06:54:02 am »
Hello,
There is a malfunction for the Daily Email Report only on machines using the MongoDB engine.
sensei-> configuration -> reporting & data-> mail verification problem "unable to verify your mail configuration. Please try again later"
The configuration of these machines are respectively:
OPNsense 20.7.1 + Sensei 1.5.2_1 + APP and rules 1.5.20200612133834 (mongodb) APU4c machines, 4 GB RAM, 120 GB, 4 Lan
OPNsense 20.7.1 + Sensei 1.5.2_1 + APP and rules 1.5.20200724174736 (mongodb) X7SPA-HF machines, Intel (R) ATOM (TM) D525, 4 GB RAM, 320 GB, 2 Lan.
However, it works on OPNsense 20.7.1 + Sensei 1.5.2_1 + APP machines and 1.5.20200612133834 (Elasticsearch) rules.
I have already made a bug report for each machine, I still have no feedback from you.
Regards,
French mother tongue
«
Last Edit: August 14, 2020, 10:38:41 am by Darkopnsense
»
Logged
Depuis 2017
X7SPA-HF, Intel(R) ATOM(TM) D525, 4Go RAM, 120Go, 2 Lan 24.1.2_1
APU4c, 4Go RAM, 120Go, 4 Lan 24.1.10_8
APU3a, 2Go RAM, 60Go, 3 Lan 24.1.2_1
APU2c, 2Go RAM, 60Go, 3 Lan 23.7.1_3
BIOS A JOUR (v4.19.0.1).
mb
Hero Member
Posts: 941
Karma: 99
Re: Sensei Scheduled reports FAIL
«
Reply #1 on:
August 14, 2020, 08:41:23 pm »
Hi @Darkopnsense,
Do a re-install of os-sensei and see if this solves your problem:
pkg install -f -y os-sensei
Please be noted that ticket support for free/home/soho editions is complimentary as of now and tickets are processed on a priority basis. Especially with bug reports, we take it very seriously but it might take some time to get back.
«
Last Edit: August 14, 2020, 08:45:05 pm by mb
»
Logged
aimdev
Full Member
Posts: 126
Karma: 5
Re: Sensei Scheduled reports FAIL
«
Reply #2 on:
September 09, 2020, 07:43:11 pm »
Mon port standard 25 aucune configuration d'authentification a récemment échoué sans raison apparente
Votre configuration de messagerie n'est pas valide! [/ b]
Réponse: Smtp: l'extension AUTH SMTP non prise en charge par le serveur.
Aucun autre e-mail provenant d'autres serveurs n'a rencontré de problème.
Ramener sensei au point où il a fonctionné n'a pas résolu le problème.
Rétablir l'opnsense au moment où cela fonctionnait n'a pas résolu le problème.
La base de données est mongodb.
Je voudrais savoir comment configurer l'e-mail de sensei en utilisant smtps ou starttls où le serveur de messagerie est local, c'est-à-dire un certificat auto-signé.
Cette déclaration est inutile.
Veuillez noter que le support des billets pour les éditions free / home / soho est gratuit à partir de maintenant et que les billets sont traités en priorité. Surtout avec les rapports de bogues, nous prenons cela très au sérieux, mais cela peut prendre un certain temps pour revenir. [/ I] [/ b]
car les utilisateurs non payants donnent au fournisseur un avertissement précoce sur les problèmes, gratuitement.
Notre temps coûte.
Anglais
My standard port 25 no authentication setup has recently failed for no apparent reason
Your mail configuration is invalid!
Response: Smtp :SMTP AUTH extension not supported by server.
No other emails from other servers have experienced an issue.
Rolling back sensei to the point it has worked has not rectified the issue.
Rolling back opnsense to when it worked has has not rectified the issue.
Database is mongodb.
I would like to find out how to setup the email from sensei using smtps or starttls where the mail server is local, ie self signed certificate.
This statement is unhelpful.
Please be noted that ticket support for free/home/soho editions is complimentary as of now and tickets are processed on a priority basis. Especially with bug reports, we take it very seriously but it might take some time to get back.
as the non paying users give the vendor an early heads up on issues, free of charge.
Our time costs.
Logged
Darkopnsense
Full Member
Posts: 148
Karma: 6
Re: Sensei Scheduled reports FAIL
«
Reply #3 on:
September 24, 2020, 11:44:45 am »
Hi mb,
I have not reinstalled os-sensei, the sensei 1.6 update reversed the problem and your update strongly questions me you will find attached my current configurations.
Explain to me why the "APP & Rules DB Version" is not uniform
The configuration of these machines at the time of this writing are respectively:
OPNsense 20.7.2 + Sensei 1.6 + APP and rules
1.5.20200612133834
(mongodb) Machine APU4c, 4 GB RAM, 120 GB, 4 Lan. (I get the report)
OPNsense 20.7.2 + Sensei 1.6 + APP and rules
1.6.20200910121420
(mongodb) Machine X7SPA-HF, Intel (R) ATOM (TM) D525, 4 GB RAM, 320 GB, 2 Lan. (I get the report)
OPNsense 20.7.2 + Sensei 1.6 + APP and rules
1.5.20200612133834
(Elasticsearch) Machine Veriton X2630G, Intel (R) Core i3-4130, 8 GB RAM, 500 GB, 2 Lan. (I get the report)
However, it no longer works since the update on the machine.
OPNsense 20.7.2 + Sensei 1.6 + APP and
1.5.20200612133834
(Elasticsearch) Machine Intel (R) Xeon (R) CPU E3-1225 V2, 8 GB RAM, 1TB, 2 Lan1000, 1 Lan100, 1 Wlan. (I am no longer receiving the report, Unable to verify your email configuration. Please try again later.)
Checking for updates the message: There is no update available on the selected mirror.
Regards,
French mother tongue.
Logged
Depuis 2017
X7SPA-HF, Intel(R) ATOM(TM) D525, 4Go RAM, 120Go, 2 Lan 24.1.2_1
APU4c, 4Go RAM, 120Go, 4 Lan 24.1.10_8
APU3a, 2Go RAM, 60Go, 3 Lan 24.1.2_1
APU2c, 2Go RAM, 60Go, 3 Lan 23.7.1_3
BIOS A JOUR (v4.19.0.1).
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
20.7 Legacy Series
»
Sensei Scheduled reports FAIL