ReadyNAS 6.10.3 - Broke Gmail (again)

[givememynamebak]

No longer receiving alerts!

I'm guessing some of my installation hangs to 6.10.3 are related to issues I am seeing with GMAIL timeouts.

I can't login to Gmail anymore with Alerts, and mails weren't going out after updating.

The error message is: 

Model: ReadyNAS 628X
Firmware: 6.10.3
Context: system_panel_support
Error:
1001000022

Settings --> Alerts --> Sign in with Google opens a new window to: http://192.168.1.100/emailservicecb.html

Page says "Redirecting. Please wait..." but you'll wait forever as it doesn't actually redirect to anywhere.

system.log indicates: 

Mar 29 12:42:15 ReadyNAS dbus[5172]: [system] Reloaded configuration
Mar 29 12:42:21 ReadyNAS apache2[9060]: [ssl:warn] [pid 9060] AH01909: REMOVEDMAC:443:0 server certificate does NOT include an ID which matches the server name
Mar 29 12:42:21 ReadyNAS apache2[9063]: [ssl:warn] [pid 9063] AH01909: REMOVEDMAC:443:0 server certificate does NOT include an ID which matches the server name
Mar 29 12:42:22 ReadyNAS apache_access[9065]: Admin session started from 192.168.1.176
Mar 29 12:42:22 ReadyNAS dbus[5172]: [system] Activating via systemd: service name='com.readynas.OAuth2Vault' unit='dbus-com.readynas.OAuth2Vault.service'
Mar 29 12:42:47 ReadyNAS dbus[5172]: [system] Failed to activate service 'com.readynas.OAuth2Vault': timed out
Mar 29 12:42:48 ReadyNAS dbus[5172]: [system] Activating via systemd: service name='com.readynas.OAuth2Vault' unit='dbus-com.readynas.OAuth2Vault.service'
Mar 29 12:43:13 ReadyNAS dbus[5172]: [system] Failed to activate service 'com.readynas.OAuth2Vault': timed out
Mar 29 12:43:13 ReadyNAS msmtpq[9379]: mail for [ -C /etc/msmtprc REMOVED@gmail.com --timeout=60 ] : send was unsuccessful ; msmtp exit code was 65
Mar 29 12:43:13 ReadyNAS msmtpq[9381]: enqueued mail as : [ 2020-03-29-12.42.47 ] ( -C /etc/msmtprc REMOVED@gmail.com --timeout=60 )
Mar 29 12:43:13 ReadyNAS dbus[5172]: [system] Activating via systemd: service name='com.readynas.OAuth2Vault' unit='dbus-com.readynas.OAuth2Vault.service'
Mar 29 12:43:38 ReadyNAS dbus[5172]: [system] Failed to activate service 'com.readynas.OAuth2Vault': timed out
Mar 29 12:44:38 ReadyNAS apache_access[9065]: 192.168.1.176 "POST /admin-cgi/localapp.cgi HTTP/1.1" 200
Mar 29 12:44:48 ReadyNAS apache2[10300]: [ssl:warn] [pid 10300] AH01909: REMOVEDMAC:443:0 server certificate does NOT include an ID which matches the server name
Mar 29 12:44:48 ReadyNAS apache2[10303]: [ssl:warn] [pid 10303] AH01909: REMOVED MAC:443:0 server certificate does NOT include an ID which matches the server name
Mar 29 12:44:49 ReadyNAS dbus[5172]: [system] Activating via systemd: service name='com.readynas.OAuth2Vault' unit='dbus-com.readynas.OAuth2Vault.service'
Mar 29 12:44:49 ReadyNAS apache_access[10305]: Admin session started from 192.168.1.176
Mar 29 12:45:14 ReadyNAS dbus[5172]: [system] Failed to activate service 'com.readynas.OAuth2Vault': timed out
Mar 29 12:45:14 ReadyNAS dbus[5172]: [system] Activating via systemd: service name='com.readynas.OAuth2Vault' unit='dbus-com.readynas.OAuth2Vault.service'
Mar 29 12:45:39 ReadyNAS dbus[5172]: [system] Failed to activate service 'com.readynas.OAuth2Vault': timed out
Mar 29 12:45:39 ReadyNAS msmtpq[10422]: mail for [ -C /etc/msmtprc REMOVED@gmail.com --timeout=60 ] : send was unsuccessful ; msmtp exit code was 65
Mar 29 12:45:39 ReadyNAS msmtpq[10424]: enqueued mail as : [ 2020-03-29-12.45.14 ] ( -C /etc/msmtprc REMOVED@gmail.com --timeout=60 )
Mar 29 12:45:39 ReadyNAS dbus[5172]: [system] Activating via systemd: service name='com.readynas.OAuth2Vault' unit='dbus-com.readynas.OAuth2Vault.service'
Mar 29 12:46:04 ReadyNAS dbus[5172]: [system] Failed to activate service 'com.readynas.OAuth2Vault': timed out

systemd_journal.log: 

Mar 29 12:45:14 ReadyNAS systemd[1]: Failed to start OAuth2 Vault Service.
Mar 29 12:45:14 ReadyNAS systemd[1]: oauth2-vault.service: Unit entered failed state.
Mar 29 12:45:14 ReadyNAS systemd[1]: oauth2-vault.service: Failed with result 'exit-code'.
Mar 29 12:45:39 ReadyNAS dbus[5172]: [system] Failed to activate service 'com.readynas.OAuth2Vault': timed out
Mar 29 12:45:39 ReadyNAS msmtpq[10422]: mail for [ -C /etc/msmtprc REMOVED@gmail.com --timeout=60 ] : send was unsuccessful ; msmtp exit code was 65
Mar 29 12:45:39 ReadyNAS readynasd[5915]: msmtp: envelope from address gary.tessman.devices@gmail.com not accepted by the server
Mar 29 12:45:39 ReadyNAS readynasd[5915]: msmtp: server message: 530-5.7.0 Authentication Required. Learn more at
Mar 29 12:45:39 ReadyNAS readynasd[5915]: msmtp: server message: 530 5.7.0 https://support.google.com/mail/?p=WantAuthError n7sm8198327pgm.28 - gsmtp
Mar 29 12:45:39 ReadyNAS readynasd[5915]: msmtp: could not send mail (account default from /etc/msmtprc)
Mar 29 12:45:39 ReadyNAS readynasd[5915]: NAS_SEND_MSMTP_RUN: Fail. (status=65. error_buf=(null))
Mar 29 12:45:39 ReadyNAS msmtpq[10424]: enqueued mail as : [ 2020-03-29-12.45.14 ] ( -C /etc/msmtprc REMOVED@gmail.com --timeout=60 )
Mar 29 12:45:39 ReadyNAS oauth2-vault[10426]: time="03-29-2020 12:45:39" level=error msg="Failed to decode config: EOF"
Mar 29 12:45:39 ReadyNAS oauth2-vault[10426]: time="03-29-2020 12:45:39" level=fatal msg="Failed to call LoadEmailService1Config: EOF"
Mar 29 12:45:39 ReadyNAS systemd[1]: systemd-journald-audit.socket: Cannot add dependency job, ignoring: Unit systemd-journald-audit.socket is masked.
Mar 29 12:45:39 ReadyNAS dbus[5172]: [system] Activating via systemd: service name='com.readynas.OAuth2Vault' unit='dbus-com.readynas.OAuth2Vault.service'
Mar 29 12:45:39 ReadyNAS systemd[1]: Starting OAuth2 Vault Service...
Mar 29 12:45:39 ReadyNAS systemd[1]: oauth2-vault.service: Main process exited, code=exited, status=1/FAILURE
Mar 29 12:45:39 ReadyNAS systemd[1]: Failed to start OAuth2 Vault Service.
Mar 29 12:45:39 ReadyNAS systemd[1]: oauth2-vault.service: Unit entered failed state.
Mar 29 12:45:39 ReadyNAS systemd[1]: oauth2-vault.service: Failed with result 'exit-code'.
Mar 29 12:46:04 ReadyNAS readynasd[5915]: Failed to issue method call: Connection timed out
Mar 29 12:46:04 ReadyNAS dbus[5172]: [system] Failed to activate service 'com.readynas.OAuth2Vault': timed out
Mar 29 12:46:04 ReadyNAS readynasd[5915]: Could not send email

Thoughts anyone?

[givememynamebak]

I'm rolling back to 6.10.2 since Netgear hasn't responded and I can't go without alert emails.

[givememynamebak]

OK, so as it turns out - this is a mess and is multiple bugs rolled up into into one nightmare with 6.10.3 as it pertains to ALERTS.

1.)  My /etc/msmtprc file somehow got corrupted by this content

defaults

tls off

tls_nocertcheck

logfile /var/log/frontview/msmtp.log

account default

aliases /etc/aliases

connect_timeout 10

host

port 25

from

Which led to the errors with the vault errors: 

Apr 03 18:36:49 ReadyNAS dbus[5089]: [system] Activating via systemd: service name='com.readynas.OAuth2Vault' unit='dbus-com.readynas.OAuth2Vault.service'

Apr 03 18:36:49 ReadyNAS systemd[1]: systemd-journald-audit.socket: Cannot add dependency job, ignoring: Unit systemd-journald-audit.socket is masked.

Apr 03 18:36:49 ReadyNAS systemd[1]: Starting OAuth2 Vault Service...

Apr 03 18:36:49 ReadyNAS oauth2-vault[13769]: time="04-03-2020 18:36:49" level=error msg="Failed to decode config: EOF"

Apr 03 18:36:49 ReadyNAS oauth2-vault[13769]: time="04-03-2020 18:36:49" level=fatal msg="Failed to call LoadEmailService1Config: EOF"

Apr 03 18:36:49 ReadyNAS systemd[1]: oauth2-vault.service: Main process exited, code=exited, status=1/FAILURE

Apr 03 18:36:49 ReadyNAS systemd[1]: Failed to start OAuth2 Vault Service.

Apr 03 18:36:49 ReadyNAS systemd[1]: oauth2-vault.service: Unit entered failed state.

Apr 03 18:36:49 ReadyNAS systemd[1]: oauth2-vault.service: Failed with result 'exit-code'.

Apr 03 18:37:14 ReadyNAS readynasd[5608]: Failed to issue method call: Connection timed out

Apr 03 18:37:14 ReadyNAS dbus[5089]: [system] Failed to activate service 'com.readynas.OAuth2Vault': timed out

Apr 03 18:37:14 ReadyNAS readynasd[5608]: Alert message failed to send.

Apr 03 18:37:31 ReadyNAS readynasd[5608]: Alert contact information was saved.

Apr 03 18:37:31 ReadyNAS readynasd[5608]: Alert settings are updated.

Apr 03 18:37:31 ReadyNAS msmtpq[13815]: msmtp queue purged (all mail)

-----------------------------------------------------

2.)  I copied over the contents of a /etc/msmtprc file from another readynas that had 6.10.1 running on it, that fixed the above errors.

3.)  With 6.10.3 - The Settings --> Alerts --> Email Server Account  (choose Google) does not work.  It sends you to

http://192.168.1.100/emailservicecb.html

Page says "Redirecting. Please wait..." but you'll wait forever as it doesn't actually redirect to anywhere.

4.)  With 6.10.1 - You'll get a nice message from Google that says its no longer supported.

5.)  Since I didn't manually type in settings this time, but copied over /etc/msmtprc - that fixed the vault issue but somehow my 

/etc/frontview/alert.conf contained the account of which I am using to SEND notifications from thus, adding that user to the "Alert Contacts" list which I did not want the same sender to be also a recipient (strange that this is coded and wrongly assumed that people would want that).   

6.)  IFF you remove the sender from the "Alerts Contacts" list - then reload the page, the User, Password, Email Provider, SMTP Server and SMTP port oddly become empty...  then, the SEND MESSAGE button becomes inoperable because "Smtp Server required to send message".  Sigh.  

So, for me to fix this.... I had to leave the sender also in the recipient list.   So now this works... but barely and my errors are gone but I am certain I am not the only one with these problems.  These are defects and Alerts needs much more attention please!

[givememynamebak]

@JohnCM_S or @Marc_V : Any thoughts as to the above bullet points and broken Gmail Authentication using the Gmail button in Alerts section?  What's going on with Netgear?  Did a bunch of people get laid off or something?  Seems to be a lack of responses, lack of updates being posted properly, lack of firmware updates/fixes with a new guy releasing fixes now?  I've been using the product since Infrant days, and the support has only gotten worse and less responsive.

[Kardano]

Hello.

I removed my sender gmail mail adress from Alert contact this way:

Downloaded (Backup) config (Miscellaneous settings only)

then edited (deleted my sender email adress from file alert.conf (in dir \etc\frontview) within config zip file)

imported changed config back to unit and restarted unit.

FW 6.10.3 , Unit was new. No such problems with earlier FW.

Alert is not sending do sender adress anymore.

[aprosnyak]

I had a similar problem and I solved it. Try to do the following:

1. SSH to your NAS

2. Goto /etc/frontview, delete (or move elsewhere) files .oauth2-vault-email.json and alert.conf

3. Re-login to your email account in Settings-Alerts

4. Enjoy ))