Proxy issue

Christian

New member
Hi Dmitry,

  I setup a squid proxy server to isolate Windows machine running RB and prevent Windows Services to connect to Internet (no default gateway setup). The proxy has no login/password.
  Unfortunatly I cannot use RB broadcasting with proxy setup. I tried those setting but none worked:
    192.168.1.128:3128
    http://192.168.1.128:3128
    proxy:3128

The proxy works for Firefox and Dropbox for instance!

Could you please confirm it should work?

Also does the proxy works for HTTP GET request under Reports settings ?
To be more precise I am using the HTTP GET feature to update the last played tracks on my website and I use a private IP (ie 192.168.1.70) but I can use the public IP of the website easily. I also use the HTTP GET to update onto TuneIn so I need the proxy to go to Internet. As a workarround I can do the TuneInupdate from my website server I just need to know ;)

Thanks. Christian
 
You should specify proxy using the HOSTNAME:PORT format, e.g. 192.168.1.128:3128

I see that you already did so, but it still didn't work? Please try restarting RadioBOSS and see if it fixes the problem.

The proxy is only used for stream playback and broadcasting, the HTTP GET requests are sent without using a proxy server.
 
I did some new attepts this evening, but no I cannot get the streaming working through the proxy setting like: 192.168.1.128:3128
The network configuration is without setting any gateway.
On the same machine I can browse Internet with Firefox and dropbox in in sync with the same proxy setting.

For the HTTP GET I can manage a workarround.

Regards
Christian
 
Thank you for the information, we'll check how proxy server works in RadioBOSS.
 
An update on the proxy issue. In order for this feature to work with streaming, the proxy has to support TCP tunneling (the HTTP "CONNECT" method). Otherwise you'll receive an error message. As you set up your own Squid proxy, you can add support for this: http://wiki.squid-cache.org/Features/HTTPS - please also note that you should enable this feature for all ports (or, at least, the ports you use for broadcasting, by default only SSL ports are open for tunneling).
 
Hi Dmitry,

  I just noticed your message. Thanks very much for investigating. Yes it fixes the problem. I can now connect through proxy.
  Maybe you should document it somewhere so other users knows that http CONNECT must be enabled on streaming port 8000, 80 or whatever they are using.
 
Christian said:
  Maybe you should document it somewhere so other users knows that http CONNECT must be enabled on streaming port 8000, 80 or whatever they are using.
Yes, good idea - thank you!
 
Back
Top