Cannot activate license via a proxy server

SUSE Linux Enterprise Server SLES Networking
1

Hi ,

I am trying to activate my license via a proxy server and it keeps giving me cannot connect error. What is the command to register via a proxy server to connect to novell.com.

Here is the command I tried:
suse_register -d 3 -a regcode-sles=xxxxxx -a email=xyz@zzzzzz.com -L suse_register-d3.log

vim /etc/sysconfig/proxy
PROXY_ENABLED=“yes”

HTTP_PROXY=“http://15.19.22.20:443:389:636”

HTTPS_PROXY=“https://15.19.22.20:443:389:636”

FTP_PROXY=“http://15.19.22.20:443:389:636”

GOPHER_PROXY=""

NO_PROXY=“localhost, 127.0.0.1”

2

Hi
If your using a proxy, there are a few things to configure;

Your proxy should should accept Novell domain (or at least selected
sites used like nu.novell.com and secure.novell.com) without
authentication.

You need to populate proxy setting in YAST and to add two lines
with your proxy information to /etc/profile, for example:

export http_proxy=“http://10.10.1.1:8081/”
export https_proxy=“https://10.10.1.1:8081/”

As well as the /root/.curlrc

Then I would login to the NCC web page and delete the system and
re-register it.

suse_register -a regcode-sles=YourActivationCode -a email=YourEmailAddress -a moniker=YourHostname -L .suse_register.log

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-21-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

3

On Mon, 20 Oct 2014 21:24:02 +0000, ynswati wrote:
[color=blue]

Hi ,

I am trying to activate my license via a proxy server and it keeps
giving me cannot connect error. What is the command to register via a
proxy server to connect to novell.com.

Here is the command I tried:
suse_register -d 3 -a regcode-sles=xxxxxx -a email=xyz@zzzzzz.com -L
suse_register-d3.log

vim /etc/sysconfig/proxy PROXY_ENABLED=“yes”

HTTP_PROXY=“http://15.19.22.20:443:389:636”

HTTPS_PROXY=“https://15.19.22.20:443:389:636”

FTP_PROXY=“http://15.19.22.20:443:389:636”

GOPHER_PROXY=“”

NO_PROXY=“localhost, 127.0.0.1”[/color]

Your proxy addresses make no sense, as they do not specify a single port,
but an HTTPS port, an LDAP port, and an LDAPS port.

Jim

Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
Novell/SUSE/NetIQ Knowledge Partner

4

I did change but still cannot connect.
cat proxy

PROXY_ENABLED=“yes”
HTTP_PROXY=“http://x.x.x.x”
HTTPS_PROXY=“http://x.x.x.x”
FTP_PROXY=“http://x.x.x.x”

GOPHER_PROXY=""

while trying to register:
URL: https://secure-www.novell.com/center/regsvc/
listParams: command=listparams
register: command=register
lang: en-US
initialDomain: .novell.com
SEND DATA to URI: https://secure-www.novell.com/center/regsvc/?command=listproducts&lang=en-US&version=1.0:

About to connect() to proxy 173.x.x.x port 443 (#0)
Trying 173.x.x.x…
connected
Connected to 173.x.x.x. (173.x.x.x) port 443 (#0)
Establish HTTP proxy tunnel to secure-www.novell.com:443
Proxy CONNECT aborted
Closing connection #0
ERROR: Failure when receiving data from the peer: (56)
(2)
ERROR: Failure when receiving data from the peer: (56)
(2)

5

On Mon, 27 Oct 2014 23:04:01 +0000, ynswati wrote:
[color=blue]

I did change but still cannot connect.
cat proxy

PROXY_ENABLED=“yes” HTTP_PROXY=“http://x.x.x.x”
HTTPS_PROXY=“http://x.x.x.x” FTP_PROXY=“http://x.x.x.x”[/color]

You need to include a port, generally.

But in your initial post, your URLs included two ports, which is not
valid.

Is the proxy an authenticated proxy?

Jim

–
Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
Novell/SUSE/NetIQ Knowledge Partner

6

Hi ynswati,

[QUOTE=ynswati;24368]
About to connect() to proxy 173.x.x.x port 443 (#0)
Trying 173.x.x.x…
connected
Connected to 173.x.x.x. (173.x.x.x) port 443 (#0)
Establish HTTP proxy tunnel to secure-www.novell.com:443
Proxy CONNECT aborted
Closing connection #0[/QUOTE]

what type of proxy is that, and how did it’s admin set up the access to the proxy for HTTPS?

Usually, for non-transperent proxies, some dedicated proxy port is configured and needs to be used by the clients (and hence configured in your proxy URL) - i.e. Squid typically uses 3128, so you’d have to specify “HTTPS_PROXY=http://your.proxy.machine.name.com:3128”. But there are many different port numbering approaches, so see your proxy admin for details.

It might also be a case where in the proxy, using the “CONNECT” method isn’t allowed or needs client authentication to the proxy. Again, ask your proxy admin for the specifics of your proxy’s setup.

Regards,
Jens