You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked that this feature has not been requested before
I checked that this feature is not in the "Not planned" list
This feature will benefit the majority of users
Problem Description / Use Case
I run seanime on a NAS. On this machine I lock the network down by binding services to vpn ip and use ufw to limit communication(as a secondary measure). In the code I observed
it binds a service to 0.0.0.0:43213, which by grepping the code I find is the TorrentClientPort.
Proposed Solution
My thoughts:
The services are probably unauthenticated so by default they should bind to 127.0.0.1 like the main web server.
I don't know enough about torrent protocols and eyeballing the code in internal/torrentstream/repository.go felt maybe there's some need to bind to 0.0.0.0. However, I'm running qbittorrent in docker as an unpriviliged user and it still works so maybe there is no need to bind to 0.0.0.0 here after all?
Maybe we can allow the user to change the host for the torrent client? An option can be provided in the Torrent client section like Streaming server section's Host field.
Or maybe we can bind the torrent client and streaming server to same host as server.host? It would be weird if the user wants to use use it on a different host as the main server's host, and if they want to change, they can do that in the settings page.
The text was updated successfully, but these errors were encountered:
Checklist
Problem Description / Use Case
I run seanime on a NAS. On this machine I lock the network down by binding services to vpn ip and use ufw to limit communication(as a secondary measure). In the code I observed
Also while running seanime i observed:
it binds a service to
0.0.0.0:43213
, which by grepping the code I find is theTorrentClientPort
.Proposed Solution
My thoughts:
The services are probably unauthenticated so by default they should bind to 127.0.0.1 like the main web server.
I don't know enough about torrent protocols and eyeballing the code in
internal/torrentstream/repository.go
felt maybe there's some need to bind to 0.0.0.0. However, I'm running qbittorrent in docker as an unpriviliged user and it still works so maybe there is no need to bind to 0.0.0.0 here after all?Torrent client
section likeStreaming server
section'sHost
field.server.host
? It would be weird if the user wants to use use it on a different host as the main server's host, and if they want to change, they can do that in the settings page.The text was updated successfully, but these errors were encountered: