That's what it says on the Aura settings screen.
I have also tried port 21 and 22 in WinSCP, but got exactly the same error.
I've also tried running ftp from the command prompt, then opening 192.168.1.248 (without a port number). I get "Connection refused"
When I try to connect to the FTP server on my Aura I get "No connection could be made because the target machine actively refused it".
I've tried two methods:
WinSCP
Web browser, using ftp://aura:0000@192.168.1.248:2323
I have File Share enabled on the Aura (and have used the URL it displays...
How long after a factory reset do you typically start getting random reboots again? (or do you not suffer from this problem?).
Also, is there any way of backing up and restoring the recording schedule following a factory reset?
Well, my luck lasted 5 days. It rebooted again this evening for the first time since I did the Freeview reset.
Humax Support responded to my email - they just told me to do a factory reset. TBH I'm not sure if it's worth the trouble, as I suspect that it may only buy be another couple of weeks...
Hmmm....I just exported my Freeview settings, did a Freeview reset, left the Aura on BBC1 for 20 minutes, then re-imported my settings. My recording schedule was not restored.
Have I misunderstood something?
EDIT: I started to re-add my scheduled recordings, starting with the 1 o'clock news on...
I haven't noticed any soft power-downs, but will keep an eye out for it. My resets are full cold restarts, with the Humax logo being displayed.
The last time a recording was interrupted (on Friday night) it failed to record the remainder of the programme after the restart. There was a 2nd...
Has anyone experienced this? I thought it might be an app glitch (we watch alot of stuff using Kodi), but the Aura will often reboot when we're simply watching live TV.
Has anyone else had this problem? It's pretty annoying as quite a few scheduled recordings have failed because of this.
Hmmm...that's sounds interesting, and would certainly explain the problem. If it's true then I guess there is no obvious solution if I continue with Proxmox :0(
I've just tried turning the HDHomeRun off then on again. It slightly improved things - I can now get tune channels from 2 of the 6 available multiplexes. If I try to add any of the other 4 the DVROntime service crashes.
Bit of a strange problem...I've just migrated my virtual environments from ESXi to Proxmox. I've created a Windows 10 VM and installed DVROntime, just as I did on ESXi (where DVROntime was running fine). While it installed without any issues, whenever I try to tune channels the DVROntime service...
Thanks. Yes it does look like the crashes are being caused by signal quality issues with the HDHomeRun. I'll look into the cabling and see if I can improve things.
After resetting (i.e. power cycling) the HDHomeRun the DVROntime retuning process initially failed to find any channels at all. I then reset the HDHomeRun again and tried again. The DVROntime service crashed a few more times, but eventually the scan completed. There were no channels in the...
Thanks - yes, those were the six channels that I tried tuning. It was just 22 and 28 that caused the problem. It looks like Sky Arts is missing as a consequence, which is a shame as I use it alot.
I've attached the event log. I think I tried tuning for the first time between 21:20 and 21:45
OK so it seems that channels 22 and 28 seem to cause the crash when tuning. If I omit these then I can progress to updating the EPG. So everything appears to be back up and running.
Many thanks for your help!
Doh! Sorry I hadn't spotted that the section already existed. OK I managed to correct the config and start the service. One step forward....
Now when I try to tune the channels the DVROntime service repeatedly crashes after tuning four of the six channels. The message generated in the Event Log...
OK so I was able to start the service manually - must've been a genuine timeout....
So I stopped it again, replaced the three v1.0.6 files with the equivalent files from v1.0.7, made the changes to the config file, then tried to restart the service. This time I get: "Windows could not start the...
That's what it says on the Aura settings screen.
I have also tried port 21 and 22 in WinSCP, but got exactly the same error.
I've also tried running ftp from the command prompt, then opening 192.168.1.248 (without a port number). I get "Connection refused"
When I try to connect to the FTP server on my Aura I get "No connection could be made because the target machine actively refused it".
I've tried two methods:
WinSCP
Web browser, using ftp://aura:0000@192.168.1.248:2323
I have File Share enabled on the Aura (and have used the URL it displays...
How long after a factory reset do you typically start getting random reboots again? (or do you not suffer from this problem?).
Also, is there any way of backing up and restoring the recording schedule following a factory reset?
Well, my luck lasted 5 days. It rebooted again this evening for the first time since I did the Freeview reset.
Humax Support responded to my email - they just told me to do a factory reset. TBH I'm not sure if it's worth the trouble, as I suspect that it may only buy be another couple of weeks...
Hmmm....I just exported my Freeview settings, did a Freeview reset, left the Aura on BBC1 for 20 minutes, then re-imported my settings. My recording schedule was not restored.
Have I misunderstood something?
EDIT: I started to re-add my scheduled recordings, starting with the 1 o'clock news on...
I haven't noticed any soft power-downs, but will keep an eye out for it. My resets are full cold restarts, with the Humax logo being displayed.
The last time a recording was interrupted (on Friday night) it failed to record the remainder of the programme after the restart. There was a 2nd...
Has anyone experienced this? I thought it might be an app glitch (we watch alot of stuff using Kodi), but the Aura will often reboot when we're simply watching live TV.
Has anyone else had this problem? It's pretty annoying as quite a few scheduled recordings have failed because of this.
Hmmm...that's sounds interesting, and would certainly explain the problem. If it's true then I guess there is no obvious solution if I continue with Proxmox :0(
I've just tried turning the HDHomeRun off then on again. It slightly improved things - I can now get tune channels from 2 of the 6 available multiplexes. If I try to add any of the other 4 the DVROntime service crashes.
Bit of a strange problem...I've just migrated my virtual environments from ESXi to Proxmox. I've created a Windows 10 VM and installed DVROntime, just as I did on ESXi (where DVROntime was running fine). While it installed without any issues, whenever I try to tune channels the DVROntime service...
Thanks. Yes it does look like the crashes are being caused by signal quality issues with the HDHomeRun. I'll look into the cabling and see if I can improve things.
After resetting (i.e. power cycling) the HDHomeRun the DVROntime retuning process initially failed to find any channels at all. I then reset the HDHomeRun again and tried again. The DVROntime service crashed a few more times, but eventually the scan completed. There were no channels in the...
Thanks - yes, those were the six channels that I tried tuning. It was just 22 and 28 that caused the problem. It looks like Sky Arts is missing as a consequence, which is a shame as I use it alot.
I've attached the event log. I think I tried tuning for the first time between 21:20 and 21:45
OK so it seems that channels 22 and 28 seem to cause the crash when tuning. If I omit these then I can progress to updating the EPG. So everything appears to be back up and running.
Many thanks for your help!
Doh! Sorry I hadn't spotted that the section already existed. OK I managed to correct the config and start the service. One step forward....
Now when I try to tune the channels the DVROntime service repeatedly crashes after tuning four of the six channels. The message generated in the Event Log...
OK so I was able to start the service manually - must've been a genuine timeout....
So I stopped it again, replaced the three v1.0.6 files with the equivalent files from v1.0.7, made the changes to the config file, then tried to restart the service. This time I get: "Windows could not start the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.