qbittorrent / qBittorrent

qBittorrent BitTorrent client
https://www.qbittorrent.org
Other
28.27k stars 3.98k forks source link

The use of hostname in version 4.6.0 results in Unsupported socket operation #19781

Closed smomop closed 5 months ago

smomop commented 1 year ago

qBittorrent & operating system versions

qBittorrent: 4.6.0 Operating system: liunx docker Qt: 6.6.0 libtorrent-rasterbar: 2.0.9.0

What is the problem?

After I deployed qBittorrent version 4.6.0 on docker, I changed the IP address on the WebUI page to the hostname of my host, such as nasdev, and then failed to start. In version 4.5.5 of qBittorrent, everything was normal.

This is version 4.6.0 of qBittorrent.

Snipaste_2023-10-25_23-51-04 Snipaste_2023-10-25_23-51-42 Snipaste_2023-10-25_23-51-53

This is version 4.5.5 of qBittorrent.

Snipaste_2023-10-25_23-49-08

Steps to reproduce

  1. Configure webui---- > ip addr to hostname(example:nasdev)
  2. WebUI will be started shortly after internal preparations. Please wait... qbittorrent | "Web UI: Unable to bind to IP: nasdev, port: 8080. Reason: Unsupported socket operation"

Additional context

qbittorrent | WebUI will be started shortly after internal preparations. Please wait... qbittorrent | "Web UI: Unable to bind to IP: ts-464c, port: 8084. Reason: Unsupported socket operation" qbittorrent | WebUI will be started shortly after internal preparations. Please wait... qbittorrent | "Web UI: Unable to bind to IP: ts-464c, port: 8084. Reason: Unsupported socket operation" qbittorrent | WebUI will be started shortly after internal preparations. Please wait... qbittorrent | "Web UI: Unable to bind to IP: ts-464c, port: 8084. Reason: Unsupported socket operation" qbittorrent | WebUI will be started shortly after internal preparations. Please wait... qbittorrent | "Web UI: Unable to bind to IP: ts-464c, port: 8084. Reason: Unsupported socket operation"

Log(s) & preferences file(s)

qbittorrent | [migrations] started qbittorrent | [migrations] no migrations found qbittorrent | ─────────────────────────────────────── qbittorrent | qbittorrent | ██╗ ███████╗██╗ ██████╗ qbittorrent | ██║ ██╔════╝██║██╔═══██╗ qbittorrent | ██║ ███████╗██║██║ ██║ qbittorrent | ██║ ╚════██║██║██║ ██║ qbittorrent | ███████╗███████║██║╚██████╔╝ qbittorrent | ╚══════╝╚══════╝╚═╝ ╚═════╝ qbittorrent | qbittorrent | Brought to you by linuxserver.io qbittorrent | ─────────────────────────────────────── qbittorrent | qbittorrent | To support LSIO projects visit: qbittorrent | https://www.linuxserver.io/donate/ qbittorrent | qbittorrent | ─────────────────────────────────────── qbittorrent | GID/UID qbittorrent | ─────────────────────────────────────── qbittorrent | qbittorrent | User UID: 1000 qbittorrent | User GID: 100 qbittorrent | ─────────────────────────────────────── qbittorrent | qbittorrent | [custom-init] No custom files found, skipping... qbittorrent | WebUI will be started shortly after internal preparations. Please wait... qbittorrent | Connection to localhost (127.0.0.1) 8084 port [tcp/*] succeeded! qbittorrent | [ls.io-init] done. qbittorrent | "Web UI: Unable to bind to IP: ts-464c, port: 8084. Reason: Unsupported socket operation" qbittorrent | WebUI will be started shortly after internal preparations. Please wait... qbittorrent | "Web UI: Unable to bind to IP: ts-464c, port: 8084. Reason: Unsupported socket operation" qbittorrent | WebUI will be started shortly after internal preparations. Please wait... qbittorrent | "Web UI: Unable to bind to IP: ts-464c, port: 8084. Reason: Unsupported socket operation"

Chocobo1 commented 1 year ago

After I deployed qBittorrent version 4.6.0 on docker, I changed the IP address on the WebUI page to the hostname of my host, such as nasdev, and then failed to start.

What are you trying to achieve? qbt webui by default listens to all the interfaces and normally you won't need touch it.

I changed the IP address on the WebUI page to the hostname of my host

Your hostname is not an IP. That field only take IP addresses.

smomop commented 1 year ago

在 docker 上部署 qBittorrent 版本 4.6.0 后,我把 WebUI 页面上的 IP 地址改成了我主机的主机名,比如 nasdev,然后启动失败。

你想达到什么目的?默认情况下,QBT WebUI 会监听所有接口,通常您不需要触摸它。

我将 WebUI 页面上的 IP 地址更改为主机的主机名

您的主机名不是 IP。该字段仅接受 IP 地址

Since I use IPV6, I do not want to be exposed to all networks, so I need to modify it to my host hostname to avoid exposure to the public network。There was no this problem in the early 4.5.5 version, but it became no longer available after upgrading to 4.6.0.

Chocobo1 commented 1 year ago

Since I use IPV6, I do not want to be exposed to all networks, so I need to modify it to my host hostname to avoid exposure to the public network.

You could try giving it ::1 to listen on local ipv6. Or you could try adding firewall rules to block outside connections.

There was no this problem in the early 4.5.5 version, but it became no longer available after upgrading to 4.6.0.

It is clear that this field is called IP address and it would never attempt to resolve host names nor URLs so your usage (using hostname) isn't valid anyway.

FizzyMUC commented 1 year ago

I'm having a similar issue. I just reverted back to v4.4.0 where it is working. In the IP address field for the Web User Interface my config says "localhost". Could this potentially be the issue? Might it work if I simply leave the field blank?

smomop commented 1 year ago

I'm having a similar issue. I just reverted back to v4.4.0 where it is working. In the IP address field for the Web User Interface my config says "localhost". Could this potentially be the issue? Might it work if I simply leave the field blank?

You must be configured as * to work

smomop commented 1 year ago

Since I use IPV6, I do not want to be exposed to all networks, so I need to modify it to my host hostname to avoid exposure to the public network.

You could try giving it ::1 to listen on local ipv6. Or you could try adding firewall rules to block outside connections.

There was no this problem in the early 4.5.5 version, but it became no longer available after upgrading to 4.6.0.

It is clear that this field is called IP address and it would never attempt to resolve host names nor URLs so your usage (using hostname) isn't valid anyway.

Thank you for your answer, but it would be better for me to return 4.5.5 for the current issue

FizzyMUC commented 1 year ago

Definitely works once "localhost" or anything else is deleted from the field.