Google & Facebook Accounts Login Enabled
We often see situations where customers forget their log-in credentials and have to use the password reset over and over again.
To help address this issue, we have enabled the Facebook & Google Sign-In integration for faster sign-up and automatic sign-in.
Having said that, there is very important to point out.
The billing console also grants you (and anyone with your credentials) access to your servers, payment methods, billing/email/ticket history, etc.
If your Google account or Facebook account is compromised and you have not enabled two-factor authentication on your Web Hosting Magic account(s), the intruder will gain access to your data.
Before using this log-in feature, please do visit your security settings page and enable 2FA.
That way, if anyone should ever gain access to your Google or Facebook account(s) and attempt to login to your Web Hosting Magic, they will be stopped stone-cold since they won't be able to complete the authentication process.
How To Login With Google or Facebook
There are two ways to associate Google, Facebook, or Twitter with your account and use it for subsequent logins.
Option 1:
- Visit https://dashboard.webhostingmagic.com/login
- Select either Google or Facebook to log in.
You will see a notice such as:
Link Initiated!
Please ensure that you have completed the initial account registration before attempting to associate either of these services with your existing Web Hosting Magic account. You just need to do this once.
Once this has been done, you can log in with either Google or Facebook the next time you visit.
You can also log out and log in with them.
Option 2:
- Log in with your existing account with email and password
- Visit https://dashboard.webhostingmagic.com/user/security and then link your Google or Facebook accounts.
Next time you visit, you can then either of these to log in.
If you receive an error message when attempting to sign in with these, please use your normal sign-in credentials and do let us know via www.webhostingmagic.com/feedback.html about the issue so we can get it sorted out.