Support for Proxy server

[reiabreu]

Screenly OSE should support proxy servers and proxy exceptions

[vpetersson]

Feel free to add it and do a pull request. The source code is available.

Personally, I haven't used proxy servers in ages (with the exception of SSH tunnels).

[reiabreu]

Lots of companies still use proxy servers. Screenly may be used as a digital signage system for companies, therefore it would be very interesting to support proxy servers. AFAIK, uzbl does not support proxy exceptions and ignores the environment variables http_proxy and no_proxy, which other browsers recognize and use. Perhaps we can replace uzbl with another browser.

[atmosx]

Why not use OpenVPN? "Companies" have enough money to setup an openvpn server, don't they?

[DSigmund]

i tried to add this line into misc/uzbl.rc: set proxy_url = http://[user]:[pwd@[ip]:[port]

Did not work...

[samueldotj]

For me the following worked. set proxy_url = http://hostname:port

@DSigmund May be authentication was the problem in your case.

[DSigmund]

@samueldotj: Hm, the authentication data was correct for my proxy, I checked this

I guess uzbl does really only support a URL here without User/PWD...

On Tue, Jun 24, 2014 at 9:15 PM, Samuel Jacob notifications@github.com wrote:

For me the following worked. set proxy_url = http://hostname:port

@DSigmund https://github.com/DSigmund May be authentication was the problem in your case.

— Reply to this email directly or view it on GitHub https://github.com/wireload/screenly-ose/issues/158#issuecomment-47017627 .

[vpetersson]

@samueldotj / @samueldotj - I've pushed a branch that (theoretically) adds support for proxy support (https://github.com/wireload/screenly-ose/tree/158). Forgot to properly tag it. Could you guys please test it? If so it should be easy to merge into master.

[samueldotj]

Thanks for fixing this. I don't have a RPi currently - will check it in a week or so.

[vpetersson]

@samueldotj sounds good. You check out the changes to screenly.conf and the branch and let me know.

[fridomac]

Sorry to dig up this old issue, but we need to use a proxy for the RPi´s... Tried the proxy support, but when I switch to the "158" branch, I only get a black screen. Web GUI responds normally, but I can not add Webpages ("Server can not retrieve Asset"). Is there any log I can look into? Bye, frido.

[vpetersson]

That branch is pretty much out of date. What we need to do is to pull in and merge the latest changes, and then issue a pull request. Unfortunately I don't have enough time to do that right now.

[fridomac]

No problem, I will try and set the proxy for uzbl manually, see how far I´ll come (i presume I have to set it in ./config somewhere, or in misc/uzbl.rc?

[vpetersson]

@over64 Let's just porting this should be enough.

[varazir]

Is there any official support for a proxy yet?

[vpetersson]

@varazir No, that's the point of this issue is to add that. :)

[jamheadjames64]

Question since this has been removed from sprint2, how do i get the latest updates that add the misc folder to the image?

Sorry I'm just not that great with github, thanks.

[vpetersson]

Depends on your setup, but since you're commenting on this, I presume you require a proxy, you might try this and then follow the regular installation instructions.

[jamheadjames64]

Have done, the Pi works to apt-get update but within Screenly it doesn't. When I try to put in a asset for website is cant with "Server Error: Could not retrieve file. Check the asset URL" for http://www.bbc.co.uk/news

[vpetersson]

Yeah this is because the proxy support in the system is implemented, but not in the actual Screenly stack.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[tyronewyatt]

I use redsocks on my screenly ose and point it to our internal proxy server. Here is a basic guide to get you started https://jmkhael.io/escape-proxy-hell-with-redsocks/

[vpetersson]

Interesting. Good find @tyronewyatt! Thanks for sharing.