Are ports 80 and 443 totally disabled for the webui?

[lithopsian]

I know in some versions of uTorrent it is possible to connect from webui using port 80 or port 443. This does not seem to be possible with the Linux builds. Is there a setting to allow this or is it just flat out banned?

[mcdonald]

I know in some versions of uTorrent it is possible to connect from webui using port 80 or port 443. This does not seem to be possible with the Linux builds. Is there a setting to allow this or is it just flat out banned?

On Unix-like operating systems, processes attempting to use ports below 1024 are required to have root privileges.

[lithopsian]

Thanks for the reply. So is that a yes or a no? Even owned and started as root, it doesn't seem to be possible to use low ports.

When changed from the tools dialog in webui it doesn't return any errors but doesn't change the port. When run by sending commands directly from the command line, it returns "invalid request" and an HTTP status of 400.

Is there something other than utserver that needs to have root privileges to do this?

[i <3 distrobution]

Maybe change bt.no_connect_to_services_list in your advanced settings?

[lithopsian]

I've tried setting no_connect_to_services to false and no_connect_to_services_list is "25, 110, 6666, 6667".

[mcdonald]

Thanks for the reply. So is that a yes or a no?

It was a conditional: if the server isn't running as root, it won't be able to use those low ports.

Even owned and started as root, it doesn't seem to be possible to use low ports.

I was just working on validation of the web UI IP restriction list, creating some unit tests for settings validation, and noticed that the port validation code restricts port numbers to be between 1025 and 65000, inclusive. This may be OK for the bind port, but it doesn't seem reasonable for the web UI ports (more testing would need to be done to see if the current user has privileges to use a low numbered port if specified).

However, the port validation function is only applied to values submitted via the web interface (in this case, for setting webui.port). If you specify a value for the configuration file setting ut_webui_port, the server should accept that value.

When changed from the tools dialog in webui it doesn't return any errors but doesn't change the port.

The web UI doesn't let you know if your settings changes are accepted by the server.

When run by sending commands directly from the command line, it returns "invalid request" and an HTTP status of 400.

The server does report validation failures on proposed values for settings, so if you talk to it directly via a command-line HTTP utility, you should see that.

[lithopsian]

Good stuff. I can do that. Tomorrow

1025 - 65000? Not 1024 - 65000? Easy to check I guess. I'll do that tomorrow too.