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
Traceback (most recent call last):,
File "tribler/core/components/component.py", line 42, in start,
File "tribler/core/components/libtorrent/libtorrent_component.py", line 31, in run,
File "tribler/core/components/libtorrent/download_manager/download_manager.py", line 150, in initialize,
File "tribler/core/components/libtorrent/download_manager/download_manager.py", line 340, in get_session,
File "tribler/core/components/libtorrent/download_manager/download_manager.py", line 296, in create_session,
File "tribler/core/components/libtorrent/download_manager/download_manager.py", line 354, in set_proxy_settings,
ValueError: invalid literal for int() with base 10: '//rutorrent.frixa.appboxes.co'
defset_proxy_settings(self, ltsession, ptype, server=None, auth=None):
""" Apply the proxy settings to a libtorrent session. This mechanism changed significantly in libtorrent 1.1.0. """settings= {}
settings["proxy_type"] =ptypesettings["proxy_hostnames"] =Truesettings["proxy_peer_connections"] =Trueifserverandserver[0] andserver[1]:
settings["proxy_hostname"] =server[0]
settings["proxy_port"] =int(server[1]) # <-- here
It looks like the user specified an incorrect value for the LibtorrentSettings.proxy_server config option.
The error does not look serious, but instead of a generic ValueError, it is better to raise a specific error that describes the problem to the user so he can fix the configuration settings.
The text was updated successfully, but these errors were encountered:
Here:
It looks like the user specified an incorrect value for the
LibtorrentSettings.proxy_server
config option.The error does not look serious, but instead of a generic
ValueError
, it is better to raise a specific error that describes the problem to the user so he can fix the configuration settings.The text was updated successfully, but these errors were encountered: