Not sure which app you are using there, but this is not the Micro Web Server app represented by this forum thread.
AFAIK, text tokens (like âAntwoordâ) cannot handle binary data, itâs always assumed to be a string (so either UTF-8 or UTF-16). This is probably unfixable since itâs a limitation of the flow system.
1 Like
Could this be solved with Homeyscript (how?), or is this not possible at all?
I donât directly see how, youâll need an app that supports uploads through HTTP, which is the only higher level protocol that HomeyScript supports. But the Micro Web Server and the HTTP/FTP Server app only seem to support FTP uploads.
The FTP-Client app can use your Micro Web server app as FTP server, and Amersfoort chose to use it. But he could have chosen a NAS or online FTP service as well.
But indeed, the issue he reports is unrelated to any FTP server
Plus: We are already âhandlingâ the issue on the FTP client topic, since this has nothing really todo with either the FTP client or Micro Web Server 
Hi! My ftp goes offline after a few days so my flows fail. How can I turn on ftp automatically?
I tried restarting the app but it doesnât work, it doesnât auto-start
Did you actually enable autostart for the FTP? Because the default is no autostart. That is a checkbox in the app settings.
yes. ell the page is a little glitched, not sure why 
I have just installed the app and try to connect using FileZilla on Mac with no success. It cannot locate it and Iâm sure that I have used the correct server address and that the ftp server is running. Are there any common things I could look for to resolve it?
Did you specifily the right port, 5081 as default?
Yes, I did.
Are both Homey and Mac part of the same subnet?
Did you use Homeyâs IP address or itâs name, homey-123456789:5081 as presented in the Web server app?
Iâd use the IP.
Are you sure FTP service is running?
(I donât question your skills, but everyone forgets the obvious sometimes).
Do you have a portscanner to check Homeyâs open ports? Network Utility maybe? Or Nmap
Yes. Itâs easy to overlook obvious things, which is why I checked and re-checked before posting :-).
I tried both the name and ip-address. Both the Homey and Mac are on the same subnet. I have ensured that the ftp service is running. Next step will be to run a portscanner utility to check if there is something funky with the ports.
For context, what I am trying to achieve is to use the web widget in the dashboard (beta) to show updated weather forecast from the Norwegian yr.no service. The web widget doesnât have the possibility to refresh at certain intervals (I have reported this as a request). So what I have done to overcome this is to write a simple html code with a refresh meta tag around an iframe with the yr.no widget.
As I donât have another webserver, I thought I could use the Micro Web Server.
Thanks. It runs fine on both Pro 19âs here, I use it to run my flavour of homeydash.com locally.
What if you change the FTP port to the default one for FTP in general, 21?
Restart the webserver app?
Try an other FTP client?
Can you show the exact error?
Not necessary. I resolved the issue. I hadnât noticed that the HP23 was exposing two IP addresses (wifi and LAN). I had been using the wifi address all along. Once I tried the LAN address, I was able to connect. Jay!
2 Likes
Oh wow hehe. I didnât even think of that possibility yet.
Yeah indeed the wifi is connected, and not actively used when ethernet is connected.
For a long time I didnât use the FTP on the MicroWebServer, but now it doesnât work anymore for me, what is going wrong?
Retrieving files via HTTP works fine.
When I open the App settings, HTTP and FTP Servers are both running, is this standard?
Homey 2016, using FileZilla : (with WinSCP also no directory listing)
14:56:31 Status: Connecting to 192.168.2.22:5081...
14:56:32 Status: Connection established, waiting for welcome message...
14:56:32 Status: Insecure server, it does not support FTP over TLS.
14:56:32 Status: Logged in
14:56:32 Status: Retrieving directory listing...
14:56:32 Command: PWD
14:56:32 Response: 257 "/"
14:56:32 Command: TYPE I
14:56:32 Response: 200 Switch to "binary" transfer mode.
14:56:32 Command: PASV
14:56:32 Response: 502 Command not supported
14:56:32 Command: PORT 192,168,2,11,197,4
14:56:32 Response: 200 The requested action has been successfully completed
14:56:32 Command: LIST
14:56:37 Response: 425 No connection established
14:56:37 Error: Failed to retrieve directory listing
