mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
3.2.0 crashing with Proxy Server #2696
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#2696
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @FaffyBucket on GitHub (Jun 25, 2015).
I updated qBittorrent 3 days ago to 3.2.0, and noticed today that all the settings have reset. Now, if I put my Proxy Server settings in qbittorrent crashes either immediately after applying the settings, or the next time I try to run qbittorrent. I am using this Socks5 proxy:
https://www.privateinternetaccess.com/pages/client-support/
@banks120 commented on GitHub (Jun 26, 2015):
i believe that i am having the same issue. i also crash when running qbittorrent with the very same socks5 proxy.
@tekko commented on GitHub (Jun 26, 2015):
https://github.com/qbittorrent/qBittorrent/issues/3046
@banks120 commented on GitHub (Jun 26, 2015):
This is exactly right thanks tekko
https://github.com/qbittorrent/qBittorrent/issues/3046
@ngosang commented on GitHub (Jun 28, 2015):
@sledgehammer999
@FaffyBucket commented on GitHub (Jul 1, 2015):
That is the same issue. Thanks tekko. I'll close this as it's already being addressed in the linked thread.