motioneyeos icon indicating copy to clipboard operation
motioneyeos copied to clipboard

Notification email failed: timed out!

Open cbrtumkur opened this issue 6 years ago • 10 comments
trafficstars

Preliminary Docs

I confirm that I have read the CONTRIBUTING guide before opening this issue.

I confirm that I have read the FAQ before opening this issue.

motionEyeOS Version

I am running motionEyeOS version: (insert your version here, e.g. 20180314).

Board Model

I am using the following board/model: (insert your board model here, e.g. Raspberry PI 3B+).

Camera

I am using the following type of camera: (choose from V4L2, MMAL, Network Camera, Fast Network Camera and Simple MJPEG Camera).

My camera model is: (insert your camera model, e.g. Logitech C290).

Network Connection

My motionEyeOS unit is connected to the network via: (choose your network connection, e.g. WiFi, Ethernet).

Peripherals

I am using the following peripherals that I consider relevant to this issue:

  • (e.g. USB WiFi adapter)
  • (e.g. External Hard Disk)

Log Files

I consider the following log files relevant to this issue:

  • (attach e.g. motioneye.log)
  • (attach e.g. boot.log)

cbrtumkur avatar Nov 14 '19 10:11 cbrtumkur

Preliminary Docs

I confirm that I have read the CONTRIBUTING guide before opening this issue.

I confirm that I have read the FAQ before opening this issue.

motionEyeOS Version

I am running motionEyeOS version: 20200606.

Board Model

I am using the following board/model: Raspberry PI 3B+.

Camera

I am using the following type of camera: V4L2

My camera model is: Aukey Webcam Full HD 1080p

Network Connection

My motionEyeOS unit is connected to the network via: WiFi.

Peripherals

I am not using others peripherals.

Log Files

I consider the following log files relevant to this issue:

motioneye.log boot.log image

Vilquid avatar Feb 05 '22 14:02 Vilquid

ERROR: failed to send mail: (535, '5.7.8 Username and Password not accepted. Learn more at\n5.7.8 https://support.google.com/mail/?p=BadCredentials v18sm1790178wrm.105 - gsmtp') indicated you don't have correct username or correct password for the account being used. The correct setup is: tempsnip I use the same email address: [email protected] for Email Address, SMTP Account, and From Address. For gmail, I use SMTP Port 587, and Use TLS ON. (Attached Pictures Time span is up to you, I never use more than 2-5 seconds...

starbasessd avatar Feb 05 '22 15:02 starbasessd

So, the correct completion is ? : Email addresses : [email protected] SMTP Server : smtp.gmail.com SMTP Port : 587 SMTP Account : [email protected] SMTP Password : [email protected] From Address : [email protected] Use TLS : ON Attached Pictures Time Span : 3

Vilquid avatar Feb 05 '22 15:02 Vilquid

That should work, but the from & SMTP names are usually the same...

starbasessd avatar Feb 05 '22 15:02 starbasessd

I have this error message : image I don't know how it can help me because [email protected] and [email protected] are correct.

Email addresses : [email protected] SMTP Server : smtp.gmail.com SMTP Port : 587 SMTP Account : [email protected] SMTP Password : [email protected] From Address : [email protected]

Vilquid avatar Feb 05 '22 15:02 Vilquid

There are issues with some 'special' characters in the password in motionEye & motionEyeOS. And you don't tack on the "@gmail.com" to the password, I hope. If you are using special characters, (depending on which specific ones) you may be able to edit the /data/etc/camera-X.conf file and place it directly in there.

starbasessd avatar Feb 05 '22 16:02 starbasessd

Yes I don’t tack @gmail.com. The problem is I don’t use special characters in my password. I gonna try to place my password in the file.

Vilquid avatar Feb 05 '22 16:02 Vilquid

Also, please try dev20201026.

starbasessd avatar Feb 05 '22 16:02 starbasessd

I tried to modify the /data/etc/camera-X.conf file but there is no file named camera-X.conf on the micro sd card. I also tried the dev20201026 version but Wifi doesn't work.

Vilquid avatar Feb 05 '22 18:02 Vilquid

The same wpa_supplicant.conf file that works on 20200606 works on dev20201026. You need to edit it while it's up and running (SSH or Console) or use a Linux to mount and edit the file.

starbasessd avatar Feb 05 '22 18:02 starbasessd