[GH-ISSUE #20] Proxy Support #17

Closed
opened 2026-02-28 14:29:59 +03:00 by kerem · 9 comments
Owner

Originally created by @sethdusek on GitHub (Jan 14, 2021).
Original GitHub issue: https://github.com/jpochyla/psst/issues/20

Hello, I have tried using psst but I am unable to connect to Spotify. I believe this is because Spotify now has even stricter region requirements. I tried using proxychains4, but it doesn't seem to work properly with this application. The main Spotify client has an option to select a SOCKS5/SOCKS4/HTTP proxy. Are there any plans to add this to psst as well?

Originally created by @sethdusek on GitHub (Jan 14, 2021). Original GitHub issue: https://github.com/jpochyla/psst/issues/20 Hello, I have tried using psst but I am unable to connect to Spotify. I believe this is because Spotify now has even stricter region requirements. I tried using proxychains4, but it doesn't seem to work properly with this application. The main Spotify client has an option to select a SOCKS5/SOCKS4/HTTP proxy. Are there any plans to add this to psst as well?
kerem 2026-02-28 14:29:59 +03:00
Author
Owner

@jpochyla commented on GitHub (Jan 14, 2021):

We could do this, yeah! As we're also using a TCP session to talk to Spotify, SOCKS would be needed, right?

<!-- gh-comment-id:760380831 --> @jpochyla commented on GitHub (Jan 14, 2021): We could do this, yeah! As we're also using a TCP session to talk to Spotify, SOCKS would be needed, right?
Author
Owner

@sethdusek commented on GitHub (Jan 20, 2021):

Yea I think so. I personally use my VPS + ssh SOCKS5 to get around the region restrictions

<!-- gh-comment-id:763350341 --> @sethdusek commented on GitHub (Jan 20, 2021): Yea I think so. I personally use my VPS + ssh SOCKS5 to get around the region restrictions
Author
Owner

@jpochyla commented on GitHub (Jan 22, 2021):

I've looked into this a bit and while HTTP proxy would be possible to use as well, SOCKS5 would be easiest to implement. I'll get to it through the next week.

<!-- gh-comment-id:765283661 --> @jpochyla commented on GitHub (Jan 22, 2021): I've looked into this a bit and while HTTP proxy would be possible to use as well, SOCKS5 would be easiest to implement. I'll get to it through the next week.
Author
Owner

@jpochyla commented on GitHub (Feb 1, 2021):

I have a SOCKS5 support implemented for the TCP session and the CDN connections, but the Spotify WebAPI would need a small PR for aspotify, so it will take a couple more days, but it's close.

<!-- gh-comment-id:770934947 --> @jpochyla commented on GitHub (Feb 1, 2021): I have a SOCKS5 support implemented for the TCP session and the CDN connections, but the Spotify WebAPI would need a small PR for `aspotify`, so it will take a couple more days, but it's close.
Author
Owner

@jpochyla commented on GitHub (Mar 10, 2021):

Hah, sorry, that took longer then expected :) I've completely removed aspotify and we do our own thing now. If you're still interested and feel adventurous, try latest master. I haven't tested it yet, but setting SOCKS_PROXY env var to smth. like socks5://john:smith@socks.google.com should work. In the future, we could add it to the Preferences dialog.

<!-- gh-comment-id:795355919 --> @jpochyla commented on GitHub (Mar 10, 2021): Hah, sorry, that took longer then expected :) I've completely removed `aspotify` and we do our own thing now. If you're still interested and feel adventurous, try latest master. I haven't tested it yet, but setting `SOCKS_PROXY` env var to smth. like `socks5://john:smith@socks.google.com` should work. In the future, we could add it to the Preferences dialog.
Author
Owner

@jpochyla commented on GitHub (Mar 13, 2021):

Closing, feel free to open in case of any issues!

<!-- gh-comment-id:798614532 --> @jpochyla commented on GitHub (Mar 13, 2021): Closing, feel free to open in case of any issues!
Author
Owner

@aslafy-z commented on GitHub (Aug 18, 2021):

This issue should be reopened since support for HTTP proxy is not present. I had a look to ureq, it seems that it won't be implemented from now on, see https://github.com/algesten/ureq/issues/62. What were the reasons behind the choice of ureq? It looks like https://github.com/seanmonstar/reqwest for example has many more features (including http_proxy support) and is better supported.

<!-- gh-comment-id:901034031 --> @aslafy-z commented on GitHub (Aug 18, 2021): This issue should be reopened since support for HTTP proxy is not present. I had a look to ureq, it seems that it won't be implemented from now on, see https://github.com/algesten/ureq/issues/62. What were the reasons behind the choice of ureq? It looks like https://github.com/seanmonstar/reqwest for example has many more features (including http_proxy support) and is better supported.
Author
Owner

@jpochyla commented on GitHub (Aug 18, 2021):

reqwest is an async client, we need only sync interface. And if I'm not mistaken, ureq does support HTTP proxies. The reason only SOCKS is supported in Psst is that we're connecting to a TCP session, and tunelling that through HTTP CONNECT is slightly more work. PRs welcome!

<!-- gh-comment-id:901035668 --> @jpochyla commented on GitHub (Aug 18, 2021): `reqwest` is an async client, we need only sync interface. And if I'm not mistaken, `ureq` does support HTTP proxies. The reason only SOCKS is supported in Psst is that we're connecting to a TCP session, and tunelling that through HTTP CONNECT is slightly more work. PRs welcome!
Author
Owner

@Metacinnabar commented on GitHub (May 19, 2022):

HTTP proxy support would be great!

<!-- gh-comment-id:1132303512 --> @Metacinnabar commented on GitHub (May 19, 2022): HTTP proxy support would be great!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/psst#17
No description provided.