Jump to content

Recommended Posts

Posted

Hi all,

 

We have been having an issue with the time/date settings on our Ubiquiti Cloud Key where it is set to 2018. We have tried amending the statistics timezone in user interface to 'browser's', 'site's', 'controller's' and 'UTC' but to no avail.

I believed it was an issue with RM blocking access to their NTP server as this works fine at another site where RM isn't the ISP.

I went into services > NTP and changed the NTP server to the one RM have recommended me to use but I'm still getting the incorrect time/date.

I have spoken to Ubiquiti on many occasions and they have been unable to get this working. They didn't believe it to be a firewall setting as I assumed above, but instead had me compacting the database and restoring from a backup etc which I found pretty useless.

 

Has anyone else had this issue and if so could you offer any guidance on how to fix?

 

Many thanks

Posted
I've not encountered that problem, but do you have an NTP server on the local network that it could use instead of the default Ubiquiti one? A domain controller, perhaps?
Posted

Would I need to set up an NTP server on the DC or is it as simple as just popping the address into services > NTP?

 

I've not encountered that problem, but do you have an NTP server on the local network that it could use instead of the default Ubiquiti one? A domain controller, perhaps?
Posted
IIRC a domain controller will have NTP server running if it's the authoritative time server for the Windows domain. I'd just try pointing your Unifi Controller to the DC first of all and see if that does the trick.
Posted

Hmm...tried that but the time or date still hasn't changed

 

try pointing to the DC using it's ip address not host name.. I had a dlink camera that was fixed using this.
Posted
Might be worth checking whether other devices are able to use your DC as an NTP server. Do you have an IP camera or something that you can manually set an incorrect time on, and then give it the DC IP address as an NTP server and see if the time corrects itself? If it does, but your CLoud Key doesn't, that would indicate something wonky with the Cloud Key.
  • 7 months later...
  • 5 months later...
Posted

Our port number is 8443, we are with RM had to request I and outbounds to the iPaddress followed by port number.

I have the cloud key setup on the DC with the unfiltered proxy set

I still can’t get email alerts though but can get everything else

Posted
Could you help me? Same problem

I assume by what you suggest possible the ISP

But I have a USG now in place of their router

I am new to this stuff and Ubiquiti are really not helping

 

- - - Updated - - -

 

Could you help me? Same problem
BT are my ISP
Posted
I assume by what you suggest possible the ISP

But I have a USG now in place of their router

I am new to this stuff and Ubiquiti are really not helping

 

- - - Updated - - -

 

BT are my ISP

 

Just allow NTP through the firewall UDP port 123, you could tie this down to specific external NTP services or internal source addresses but I don't normally bother. How you do that on the USG I do not know as I do not have one but it will be the same sort of process for other firewall filters/policies/rules.

 

You can checkout some YouTube vidoes, just do a search for USG.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...