Trying to set the time on roku automatically and it’s failing; are the time servers used by roku down? This would be urgent for apps that are time-based.
“The time could not be set from the network and will not be displayed. Please check your network connection.
Note that some channels will not work correctly until the time has been set.”
I checked my network connection and it’s fine. Anyone know what’s going on?
Update: whatever the issue was appears resolved today, getting the correct time now, whereas yesterday it was a good 10+ days in the past.
spoke to soon, still seeing an issue when running roku through a web proxy and rebooting, the time is many days in the past. This wasn’t happening last week, something changed
What does this even mean, “Trying to set the time on roku automatically and it’s failing”? I thought Roku always fetches its own time. No idea where you are seeing that error msg and by whom either. Maybe posting a screenshot would have helped?
Sorry for being unclear, that was under Settings → System → Time → Time zone → Set automatically
I tried that after seeing dates from roDateTime as several days in the past. seems it’s only happening when running through a web proxy.
date = CreateObject("roDateTime")
print "The date is now "; date.AsDateString("long-date") + " "; date.GetHours(); ":"; date.GetMinutes(); ":"; date.GetSeconds()
I run that after disconnect from the proxy and reboot roku
output: The date is now Wednesday December 9, 2015 23:56:12
then going to home screen and run a few minutes later, it gets the correct time
output: The date is now Wednesday January 20, 2016 2:55:40
last week the time was correct through the proxy, so at first I thought it was a more widespread issue
If the Roku is not able to connect to the time server, it will boot with a date in the past (actually the date the software was built).
I think the IP address of the time servers changed on the day you were having trouble. Maybe stale DNS information? Perhaps related to your proxy server?
–Mark
Concerning the time server, I am setting a demo for a Roku that will not have access to the internet. The Roku is for a trade show that will not have internet access. The time does not get set correctly and is set to November 11,2015.
Could you provide the ntp address for the Roku? Or how could we set the datetime as our client relies on the datetime for guide data. We could then setup a ntp server on our local server to give the correct time to the Roku.
Thanks for any help on this matter.
That’s not really possible. The system is deliberately designed so that only the actual Roku time server can set the time.
–Mark
“edskitter” wrote:
how could we set the datetime as our client relies on the datetime for guide data.
I was thinking we could hit an API that would give the current time on app launch and then retain the offset from the roku’s time as a global var to be used whenever the time is needed. Hopefully won’t need to do that but maybe it would work for your situation.
(Update for Time server issue)
Up here in Canada with Bell … their dns is still pointing to ur old timeservers ips.. this has created a disaster here for thousands… Youtube doesnt work .. you get a black screen… most apps that rely on datetime object for authentication just exit or spit out an error. (Note: Netflix does work)
Time shows as December 9 2015 .. for everyone.. the only FIX is to change DNS in the BELL router to googles or any other DNS that has the updated entries.. such as 8.8.8.8 or 8.8.4.4..
I contacted Roku only to get a response from your call center overseas that this is normal… I dont think its normal there is no time on home screen.. Its been 3 days there is no TIME.. Im a programmer and I know what to do but most others have a hard time changing the dns…
As for Bell Canada I dont think they care .. They were notified.. This situation is probably good for them.. but whats strange is why propagation is taking this long.. it doesnt make sense..
Is there any way to get you guys to contact Bell Canada to Fix this?
Im sorry to jump in on ur post joetesta.. but u mentioned time servers and this is a big issue here since Bell Canada serves hundreds of thousands of clients and many people have rokus here…
We have just reactivated the old IP addresses so locales that are still caching the old address should be working again. We will make sure that we see no traffic to the old addresses before we deactivate them again.
–Mark
You guys are great… I just confirmed it.. and it works.. thats professionalism..
“b_live883” wrote:
(Update for Time server issue)
Im sorry to jump in on ur post joetesta.. but u mentioned time servers and this is a big issue here since Bell Canada serves hundreds of thousands of clients and many people have rokus here…
Don’t be sorry, glad I started the thread now that we know this actually was a problem for more than just me!
cheers,
Joe
hi — today is new years day 2022 — my venerable Roku Soundbridge M1001 was showing:
11:46 Sunday, February 20, 2022
when i walked in this morning — snafu — i was able to go to the device’s internal webpage at:
http://soundbridge.local/SoundBridgeConfig.html
where the: Time Zone & Network Time were set to:
Time Server: time.rokulabs.com
which are no longer responding correctly —> thus yielding wrong time on the M1001
SOLUTION that WORKED: setting the network time server to:
thank you apple & thank you roku for making updatable user-configurable products — i dont have to throw it out, because i love it as a clock, and it still streams music purrfectly. 
john penner,
toronto island
