Proxy Credentials issue

Get Help
1

We are setting up xibo 1.8.11 on docker (Centos host) and are having trouble accessing external content through our corporate proxy server. It requires domain authentication, so credentials in the form
domain\user

For some reason the credentials are not working, no matter how I format the domain\user:password, (url encode or not) - what seems to be happening is the username is being passed as
httpdomain\user to the proxy server.

In fact, the “domain” part seems irrelevant, since whatever user I enter, the proxy logs tell me it is getting “httpuser” passed to it - this does not happen with any other apps accessing the property.

Any ideas?

Thanks

Simon

2

You can load the docker image out of band instead if you can’t get your proxy to work with Docker.

So on a machine without proxy, run the following:

docker pull xibosignage/xibo-xmr:release-0.7
docker pull xibosignage/xibo-cms:release-1.8.11
docker pull mysql:5.6
docker save xibosignage/xibo-xmr:release-0.7 > xmr.tar.gz
docker save xibosignage/xibo-cms:release-1.8.11 > cms.tar.gz
docker save mysql:5.6 > mysql.tar.gz

Copy those three tar.gz files over to the production box, then run

docker load -i xmr.tar.gz
docker load -i cms.tar.gz
docker load -i mysql.tar.gz

Then do your docker-compose up -d or whatever as normal, and it won’t need to download those images.

3

Hi Alex,

Sorry, I explained the error really badly. setting http_proxy worked fine for the download (after encoding the backslash.) The problem we are having is with Xibo itself, on the settings/network page.

Thanks

Simon

4

You need to make sure your proxy supports basic authentication. I’m pretty sure that’s all that is supported

Assuming it does, then the http at the beginning sounds like maybe your proxy URL format is off and that’s knocking on to authentication.

That being said I can well believe that a backslash in the username would be removed. Many proxies I’ve seen actually support other characters to do the same job - hash # for example, so you could try that

5

As I say, I can use standard linux http_proxy to access sites, using:
http_proxy=http://dom%5Cproxyuser:password@192.168.0.1:8080
This works for curl, wget etc, and in the proxy logs I see dom\proxyuser in the log as username
In xibo I am using the following settings
Proxy URL http://192.168.0.1
Proxy Port 8080
Proxy Credentials dom\proxyuser:proxypassword
and this records error 407 in the XIbo log, and a username of httpdom\proxyuser in the proxy log user field. If I use
Proxy Credentials proxyuser:proxypassword
(i.e. no special chanracters) I see httpproxyuser in the proxy log file. Something in the way Xibo is taking the various bits and gluing them together is breaking it - as an act of desparation I cleared the port and credentail fields and put
http://dom\proxyuser:password@192.168.0.1:8080
in the Proxy URL it all worked!!!

Not entirely intuitive, so it would be nice if the code could be fixed so the fields work as expected, but I’m happy now :slight_smile:

Simon