Page 1 of 1

Device Cannot Login with the Same e-maill address again.

Posted: 18 Jun 2020, 09:34
by Episystems
Hello,

We have an issue when a customer tries to login with the same e-mail address again as explained bellow:

The Customer sees the bellow image, inserts his e-mail address, accepts The Condition and press Login
E-mailRegistration.png
Then in case the same e-mail address used again, it displays: "Error! Sorry the registration process has been interrupted because the user is already registred!" as depicted bellow:
ErrorUserAlreadyRegistered.png
Thank you in advance

Re: Device Cannot Login with the Same e-maill address again.

Posted: 18 Jun 2020, 10:16
by HSNMSupport
Hi,
once you register your email address, it is written into DB so there is no needs to register again.
Why are you register twice with the same email address?
Have a nice day.

Re: Device Cannot Login with the Same e-maill address again.

Posted: 18 Jun 2020, 13:04
by Episystems
Hello,

In case a customer has more than one devices,
How will they connect multiple devices with the same e-mail address?

Thank you in advance

Re: Device Cannot Login with the Same e-maill address again.

Posted: 18 Jun 2020, 13:30
by HSNMSupport
1) the product assigned to him must have 2 or more concurrent decides allowed.
2) he must log in not register again.
Have a nice day.

Re: Device Cannot Login with the Same e-maill address again.

Posted: 19 Jun 2020, 09:07
by Episystems
1) the product assigned to him must have 2 or more concurrent decides allowed.
They are already configured for 10 concurrent connection and an unlimited Maximum number of devices
2) he must log in not register again.
There is only the option to Register.
How can we setup the option to Login for someone who has already registered?

Have a nice day.

Re: Device Cannot Login with the Same e-maill address again.

Posted: 19 Jun 2020, 10:30
by HSNMSupport
I think you've wrongly configured your domain products.
Please provide us via email to support the URL to reach your HSNM and open port 22 for ssh access.
Thank you