SUSE Support

Here When You Need Us

Update Process Using Curl Does Not Access the Configured Proxy Server

This document (7006745) is provided subject to the disclaimer at the end of this document.


SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
SUSE Linux Enterprise Server 11
SUSE Linux Enterprise Server 10


NOTE regarding (SLE10 and SLE11 only):                                                                                                                                                                                        
The Novell Customer Center (NCC) and are not available anymore.
SLE10 and SLE11 Systems still registered to the Novell Customer Center (NCC) can be migrated
to the SUSE Customer Center (SCC) as outlined at:

The server cannot connect to the update server due to proxy errors
The server attempts to connect directly to the update server, instead of using the configured proxy server
The server is configured to access a proxy server, but fails to connect
The supportconfig updates.txt file may show the following:

#==[ Command ]======================================#
# /usr/bin/curl --verbose --capath /etc/ssl/certs/ --digest --remote-time --fail -u 8f8474ba172c4959bad2835bdc0ae9b0:fe81fa3c28fa4d909e8d74135d1f63ab -O "" 2>curl.log
* About to connect() to port 443
*   Trying connected
* Connected to ( port 443
* successfully set certificate verify locations:

#==[ Command ]======================================#
# env | grep -i proxy

#==[ Configuration File ]===========================#
# /etc/sysconfig/proxy


Even though a proxy is configured correctly in the /etc/sysconfig/proxy file, curl uses the http_proxy and https_proxy environment variables to know how to properly use a proxy server. If these variables are not set in curl's session environment, curl will not use the proxy server and updates will not occur as expected.

1. Try to log out and log back in. The environment variables will be set and the updates should work. To check the environment, run:

env | grep -i proxy

2. If logging out does not work, try rebooting the server; then retest.
3. If rebooting does not work, you are clearing or unsetting the http_proxy or https_proxy variables in the environment. Search your environment files for entries like the following, and remove them so the variables can be set properly by the /etc/sysconfig/proxy file.

unset http_proxy
unset https_proxy

Some environment files to search include, but are not limited to:


This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7006745
  • Creation Date: 27-Aug-2010
  • Modified Date:21-Dec-2021
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.