New install fails to login after license issue

[CuriousG]

I signed up for the free one year and receive a license Feb 26, 2018. I delay installing until today May 2, 2018 so a little over 2 months.

I sign up through Google Cloud services which is very confusing if it has never been setup with the 3CX link. I finally have my cloud computing instance up and running so I login to the Management Console with the supplied credentials that were e-mailed to me and I get through just fine.

I proceed to setup my SIP trunks and start the provisioning process. I misread the part after provisioning on what to enter on my phone and this is where my troubles start.

After rebooting the phone didn't prompt me for the username and password information, I decide I wanted to reprovision the phone. I go back into the dashboard and was presented with several error messages one of which had to do with my license key (maybe they revoked it?).

At this point I decided I wanted to log back in to the Management Console. I didn't change the password nor did it give me an option to change the password. So not even an hour later from my brand new install, I'm locked out with the message:

Login access denied. Too many incorrect login attempts. Try later or contact the Administrator.

There was definitely not enough time for me to even have done a backup so I could search for the password in the XML file that I read about. This is my very first time installing 3CX so maybe I missed something. I'm not sure where to proceed from here. I can surely kill this install and start over but will I run into issues with the license key and possibly be locked out again through the Management Console?

 

[Marari]

You can either wait for the ip ban to drop off, or, if you can, log in to the console from another external IP. Use a VPN or maybe your cell phone.

I suggest whitelisting your own external IP address if you're in setup mode.

 

[Allen_Miller]

Are you using STUN or SBC for configuring your phone(s)?

 

[YiannisH_3CX]

Login access denied. Too many incorrect login attempts. Try later or contact the Administrator.

The error suggests that you IP has been blacklisted for too many incorrect login attempts. This could also be caused by a miss-configured device in your network trying to authenticate to the server and the IP was blacklisted by the server. Try accessing the server from a different public IP and whitelist your public IP to prevent this from happening again.

Regarding the rest of the errors, we will need to know what those are once you are able to login back to the server.

 

[CuriousG]

I was using STUN to provision. When it asked for the update information on my phone, I entered in the wrong info and that's when it probably blacklisted my IP. I have resolved the issue with the IP and whitelisted it per your recommendation. I'll have to wait until this evening to play with it some more.

Thanks for the quick replies everyone.

Couple more questions now, since I did sign up with Google Cloud the Dashboard indicates a dynamic IP in red. Should I change that to static? Also I'm using an unsupported SIP trunk provider, is there a way to get rid of the red exclamation point without having to use one of your approved providers? I'm only testing at this point with a DID that is available and if I like what I see, I'll go with someone on the approved list.

 

[YiannisH_3CX]

Glad to see the IP issue has been fixed.

since I did sign up with Google Cloud the Dashboard indicates a dynamic IP in red. Should I change that to static?

If you have a static IP or you are able to get a static IP then i would recommend doing so. If your IP is dynamic then you should leave it set to Dynamic so the PBX can identify any IP changes using STUN and update the DNS entries for the FQDN. If you switch to static and the IP changes then the DNS will entry for the FQDN will not update. This applies to installation that use a 3CX FQDN.

Also I'm using an unsupported SIP trunk provider, is there a way to get rid of the red exclamation point without having to use one of your approved providers?

Not at the moment. As long as you are using an unsupported provider the exclamation mark will remain. That is just a warning though and does not mean that your provider is not working properly.

 

[CuriousG]

So I've been successful in getting my unsupported SIP provider working after a lot of trial and error and my hardware VoIP phone and 3CX client working. I started to implement OpenCNAM support through the CRM server side and I can't find the plugin. I updated the list and there's only 7 listed on the server side and 14 on the client side. Neither has OpenCNAM listed.