connecting problems through firewall

[himmijimmy]

nice client,
but is there a way to force connecting on port 80/443?
i am in an firewalled environment , there unfortunately is no way to connect on other ports.

ap_list |  
    -- | --
   0 | "gew1-accesspoint-a-2t2g.ap.spotify.com:4070"
   1 | "gew1-accesspoint-a-5gzt.ap.spotify.com:443"
   2 | "gew1-accesspoint-a-sln5.ap.spotify.com:80"
   3 | "gew1-accesspoint-a-zjsh.ap.spotify.com:4070"
   4 | "gew1-accesspoint-a-k969.ap.spotify.com:443"
   5 | "gew1-accesspoint-a-1djt.ap.spotify.com:80"
   6 | "guc3-accesspoint-a-m2zt.ap.spotify.com:4070"
   7 | "guc3-accesspoint-a-wz6l.ap.spotify.com:443"
   8 | "gae2-accesspoint-a-7zxr.ap.spotify.com:80"

[hrkfdn]

You can now specify an HTTP proxy, maybe this helps in your use-case?

[pbentkowski]

I have a similar problem. I cannot connect via my institution LAN, but when I switch my computer to connect to my smartphone's hotspot WiFi, it works. Funny, the official Spotify client for Linux works fine through LAN.

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 110, kind: TimedOut, message: "Connection timed out" }', src/libcore/result.rs:1188:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

Running both on Linux Mint 19.3 Cinnamon with ncspot installed via Snap. Love the small RAM footprint!

[Khillo81]

I'm facing the exact same problem. Could anyone tell me how this http_proxy thing works? I've tried it but it doesn't seem to help. The only reason I'm using ncspot is to listen to music at work while I'm working at the command line.

[hrkfdn]

Closing due to inactivity. ncspot supports http_proxy env vars set by the system, anything else would have to be done in librespot.