[App][Pro] Micro Web Server

Apps
, ,
122

Tried to restart the web server?

123

Sure, several times. Also tried on PC and tabet and mobile.

124

That’s a bit strange. I am not aware of any changes.
I will try looking into that. It is just that I am still down with sickness. So it might take a while still. Sorry.

1 Like
125

No hurry, take your time to recover, thanks for reacting.

126

Hi @Peter_Kawa , can you please try if FTP still works to find out if it’s my local problem or a system/app problem? Thanks in advance.

When I open the App settings, HTTP and FTP Servers are both running, is this standard?

127

Yes, still works fine on my Pro 19’s, Jan.
I use the ‘normal’ ipv4 IP address, like 192.168.2.x:5081, not the homey-62xxxxxxxxxxxx:5081 address like mentioned in the app settings.

And it doesn’t work with ftp client setting “passive mode”, maybe you have it enabled?

You can disable auto launch for the FTP service, Jan:
Only the description above it needs a little update

1000000479
1000000479605×580 56.9 KB

128

Thanks Peter, this means it is my local problem.
Tried all this but still no result, the connection is established but the LIST command does not work.
There are several sound files on it and they can be played, so the LIST command should have to show these files.
In active mode it takes a few seconds before the response message and the error is displayed.
Any other suggestions that I can try?
@robertklep Any idea?

129

Apparently, the Micro Web Server app doesn’t support passive 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

That means that the FTP server needs to be able to make a network connection with your PC (on IP address 192.168.2.11), and it looks like that’s being blocked, probably by a firewall.

The annoying thing about this is that the port number to which the server connects will be different every time (that’s why active mode sucks and FTP servers should support passive mode) so all you can do is somehow whitelist your Homey to allow access to all ports on your PC.

130

Thanks Robert, apparently I added the passive-mode logging, here is a logging in active-mode:

12:48:43	Status:	Connecting to 192.168.2.22:5081...
12:48:43	Status:	Connection established, waiting for welcome message...
12:48:43	Status:	Insecure server, it does not support FTP over TLS.
12:48:44	Status:	Logged in
12:48:44	Status:	Retrieving directory listing...
12:48:44	Command:	PWD
12:48:44	Response:	257 "/"
12:48:44	Command:	TYPE I
12:48:44	Response:	200 Switch to "binary" transfer mode.
12:48:44	Command:	PORT 192,168,2,11,20,240
12:48:44	Response:	200 The requested action has been successfully completed
12:48:44	Command:	LIST
12:48:49	Response:	425 No connection established
12:48:49	Error:	Failed to retrieve directory listing
13:00:43	Status:	Disconnected from server

Does this give a better view on the problem? (disconnected manual @13:00:43)

131

Still the same issue: the server wants to connect to your PC, and it doesn’t work (“425 No connection established”)

132

Thanks @robertklep and @Peter_Kawa Found the problem,
the Windows Defender Firewall was blocking it.

2 Likes