Appliance Proxy settings

From Swivel Knowledgebase
Jump to: navigation, search


Configuring an application to use proxy authentication
Configuration Notes

Introduction

Some communications may require a proxy connection to the internet.


Proxy CMI Configuration

From the CMI select Advanced Options/Networking/HTTP Proxy then select Enter HTTP Proxy.

Enter the following information:

Server: The Proxy server IP or hostname

Port: The Proxy server port

Username: The username for authentication to the Proxy Port

Password: the password for authentication to the proxy port.

For the settings to take effect restart Tomcat.


Proxy Command Line Configuration

For devices that do not have the CMI appliance Proxy configuration, it must be configured through the command line. To configure a proxy for communication from the Swivel appliance edit the following file

It is assumed that the appliance is already configured, and has a valid IP address on your network.

 /etc/profile

Add the following lines:

 export http_proxy=http://username:password@<wwwcacheaddress>:port
 export ftp_proxy=http://username:password@wwwcacheaddress:port
 export gopher_proxy=http://username:password@wwwcacheaddress:port

Example:

 export http_proxy=http://user1234:pass1234@<www.swivelcache.com>:8080


Testing

 echo $http_proxy

For settings to take effect reboot the server.

If any error messages are reported please contact Swivel Secure support (support@swivelsecure.com) for assistance.


Known Issues

Appliance build 2.0.9a may not pass the authentication credentials to the proxy server


Troubleshooting

Error Messages

LOG_HTTP_TRANSPORT_ERROR, Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required"

Authentication is required, enter authentication details. Verify authentication details are correct. Remember to restart Tomcat. It may require allowing access without authentication from the Swivel IP address.


LOG_HTTP_TRANSPORT_ERROR, No route to host

Swivel may not be using the Proxy server, ensure correct details and Tomcat has been restarted. Ensure that the DNS name is recognised.