Forum › Forums › Freeview HD › Aura UHD › FTP / DNLA Server not working
- This topic has 52 replies, 7 voices, and was last updated 3 years, 7 months ago by
Anonymous.
-
AuthorPosts
-
April 8, 2022 at 3:40 pm #22476
Anonymous
InactiveHi All. Just got myself an Aura, but really struggling with the FTP / DNLA aspect of it.
I have turned the server on in the settings and can watch TV and recordings (And download them) over my (Wired) network using a browser pointing to 192.168.0.61:8080 (The Aura IP).
However, the Aura doesn’t show up as a DNLA server on any of my devices, and I can’t FTP into it using Fileziller to 192.168.0.61 using port 2323, user name aura and password as the unchanged 0000 pin. I just get the ‘Connection Refused’ message.
I know there has been a bit of discussion about this, but can anyone offer me any hits about how to get this working?
April 12, 2022 at 6:50 am #109345Anonymous
InactiveHi Mark, I am in the same situation as you. I am not an expert.
I persevered with FileZilla, repeatedly typing in the full ftp address into the “Host” box.
I was initially getting the error messages similar to yours. Then entering precisely the same ftp address I got the message:
Status: Connection established, waiting for welcome message…
Status: Insecure server, it does not support FTP over TLS.
A popup box appeared, I had to accept that I was using an insecure server then:
Status: Logged in
With a directory listing of the Aura.
Hope this helps, good luck.
April 12, 2022 at 7:43 am #109346Anonymous
InactiveA quick update, I’m back to not being able to make the connection!!!
I hope someone can come up with the solution for this problem.
April 14, 2022 at 12:39 pm #109347Anonymous
InactiveDon’t know about DLNA other than to say that it’s a dreadful monster on any device but I’ve been trying to suss the ftp issue and might be able to help. I don’t think it’s actually “the connection” as such. It seems that the server can’t handle large streams of data – perhaps a buffer that gets filled and doesn’t empty quickly enough. I tried to transfer a folder full of audio albums and got the “connection lost” message followed by ftp being unavailable for long periods of time. I then tried transferring smaller numbers of files and had no such issue. Gradually increasing the number of files in the queue eventually created the “connection lost” error but critically, the server became available again almost immediately afterwards. This suggests to me that it’s the size or number of files being added to the queue that’s the issue – and that the more that buffer or stream is overloaded, the longer it takes to be cleared out so it can start again. (I’s also tried various ways to create the outage – running the screen-saver, switching to live TV or running various apps – none of those appears to cause any issue for ftp).
I don’t pretend this is a “scientific explanation” but I can say that I’m now able to tranfer as many files as I like without losing the ftp connection – albeit in a rather labour-intensive fashion. Assuming this is about a data buffer, I don’t know if it’s something that Humax can address but if ftp itself was THAT bad, it wouldn’t even exist. My guess is that they need to add or adjust some sort of cache. Meanwhile, limit the number of files you transfer in one hit and at worst, you’ll only lose access to the server for a couple of seconds.
Edit – am looking at FileZilla and see that it has an option to apply a “speed limit” to transfers. Will have a play with that later to see if throttling helps though in general, using FileZilla does seem to remove the problem anyway.
April 14, 2022 at 1:30 pm #109348Anonymous
InactiveSadly I don’t get that far. I can’t actually connect at all.
I have tried the browser method as detailed on the Humax share files screen and also using Filezilla, but all I get is the dreaded “Connection Refused’ message.
However, as detail above I can at least watch and download SD files using the browser and port 8080.
April 14, 2022 at 1:52 pm #109349Martin Liddle
ParticipantMarkPainter – 21 mins ago »
Sadly I don’t get that far. I can’t actually connect at all.
I have tried the browser method as detailed on the Humax share files screen and also using Filezilla, but all I get is the dreaded “Connection Refused’ message.
Could you tell us what your Filezilla settings are please?
April 14, 2022 at 7:56 pm #109350Anonymous
InactiveThese are my settings
[attachment=95181,2150] [attachment=95181,2151] [attachment=95181,2152]
April 14, 2022 at 8:30 pm #109351Anonymous
InactiveHave you tried simply typing ftp://192.168.1.61:2323 in your browser or any Windows explorer window – remove all the potential complexities of setting encryption etc. And in FileZilla, just enter the Host as the IP address and the port as 2323 in the main window (where it says “quick connect”). That’s all you need. You only need the name and password if specifically asked for it.
April 15, 2022 at 7:08 am #109352Anonymous
InactiveI appreciate all your ongoing suggestions.
Sadly no difference however I try to connect.
The port display 8080 works 100% fine but nothing on port 2323 seems to do anything.
[attachment=95184,2153] [attachment=95184,2154]
April 15, 2022 at 8:19 am #109353Anonymous
InactiveHave you tried rebooting the Aura?
April 15, 2022 at 8:56 am #109354Anonymous
InactiveI have tried unplugging it and power recycling, as well as doing a hard reset and disk format.
But made no difference.
I emailed Humax support at the start of the week and and apparently my email has been passed on to the technicians colleague, but not heard back on that yet.
April 15, 2022 at 10:23 am #109355Martin Liddle
ParticipantMarkPainter – 14 hours ago »
These are my settings
The only difference between your settings and my settings for Filezilla is that for encryption I have “Only use plain FTP (insecure)”. For me it works first time, every time.
April 15, 2022 at 1:47 pm #109356Anonymous
InactiveWell. I have done some more experimenting. I have reset my entire network, and changed it from it’s default 192.168.0.1 range to 192.168.1.1 in case that would help.
I then when into the Humax, turned off the DNLA server, turned off the file share server, selected “Allow anonymous connections” and then turned the file share server back on.
And it worked… First time with no issues.
I was able to browse and download and see what everyone else can see on their Aura.
I genuinely thought I had cracked it. Played around browsing and uploading and downloading and all seemed fine.
Then put the Humax into standby mode, went out for an hour, and then came back and tried it again.
Guess what? Back to being “ECONNREFUSED – Connection refused by server”.
“Error: Could not connect to server”
I think this has beaten me. I can’t think of anything else I can try.
Very disappointing, especially when this is an expensive domestic device which should just work when you plug it in.
I assumed that being a Humax it would be the best, but have I become very disheartened with this and probably won’t bother Humax with my money again.
April 15, 2022 at 2:01 pm #109357Anonymous
InactiveNot sure if this will help, but I had the same problem trying to connect using Filezilla. In my case it turned out to be a wi-fi extender that did something strange with the ip address. I took all my devices off wi-fi and used Powerlines to connect to everything that needed an internet connection. It’s worked perfectly ever since, and is much more stable when streaming (no more buffering).
April 15, 2022 at 4:08 pm #109358Anonymous
InactiveHi Geoff
Thanks for you input, sadly for me I am already using a wired network with a powerline adapter from my PC to the router.
It doesn’t work on Wifi from my laptop either.
The frustrating thing is that I can watch the recordings perfectly every time using the port 8080 access.
Was genuinely deflated after getting it working once for it not to work again after putting the Humax into standby and then waking it again.
I have now tried setting it on a fixed IP, but it made no difference.
What a waste of a bank holiday Friday this has been!
-
AuthorPosts
- You must be logged in to reply to this topic.