# suse\_register via proxy

**URL:** <https://forums.suse.com/t/suse-register-via-proxy/28359>\
**Category:** SLES Configure-Administer\
**Created:** [June 29, 2016, 6:51pm UTC](https://forums.suse.com/t/suse-register-via-proxy/28359 "2016-06-29T18:51:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dafrk](https://avatars.discourse-cdn.com/v4/letter/d/958977/32.png) [@dafrk](https://forums.suse.com/u/dafrk)\
**Post date:** [June 29, 2016, 6:51pm UTC](https://forums.suse.com/t/suse-register-via-proxy/28359/1 "2016-06-29T18:51:10Z")

</div>

dear experts,

I am desperately trying to register SLES 11 SP4 for SAP applications using suse\_register. since i can under no circumstances connect the server directly to the web, I have to use a proxy in whose configuration i have absolutely no influence. I just told them to grant me access to \*[novell.com](http://novell.com) without authorization.

I did the following:  
OS\>yast2 proxy  
insert proxy settings and test - works.  
insert proxy settings into .curlrc

Then I tested the proxy with mozilla firefox. When I am trying to open [secure-www.novell.com](http://secure-www.novell.com), it prompts me that the certificate is not trustworthy - i accept the exception and get te certificate. since then everything works fine.

But when I am trying to  
OS\>curl -x : [secure-www.novell.com](http://secure-www.novell.com)  
it gives me the typical CA-certificate error. With the option -k it works. same with wget

So when I am trying to register via  
OS\>suse\_register -a regcode-sles= -a email= -L /root/.suse\_register.log

it runs into a TCP timeout. but since i can access the register web page via firefox, network settings should not be the problem.

I am 90% sure it has something to do with suse\_register or curl not accepting the certificate.

Glad for any help.

Best regards

---

<div class="post-metadata">

**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\
**Post date:** [June 29, 2016, 7:58pm UTC](https://forums.suse.com/t/suse-register-via-proxy/28359/2 "2016-06-29T19:58:07Z")

</div>

On 29/06/16 16:54, dafrk wrote:  
[color=blue]

> I am desperately trying to register SLES 11 SP4 for SAP applications  
> using suse\_register. since i can under no circumstances connect the  
> server directly to the web, I have to use a proxy in whose configuration  
> i have absolutely no influence. I just told them to grant me access to  
> \*[novell.com](http://novell.com) without authorization.
> 
> I did the following:  
> OS\>yast2 proxy  
> insert proxy settings and test - works.  
> insert proxy settings into .curlrc
> 
> Then I tested the proxy with mozilla firefox. When I am trying to open  
> [secure-www.novell.com](http://secure-www.novell.com), it prompts me that the certificate is not  
> trustworthy - i accept the exception and get te certificate. since then  
> everything works fine.
> 
> But when I am trying to  
> OS\>curl -x : [secure-www.novell.com](http://secure-www.novell.com)  
> it gives me the typical CA-certificate error. With the option -k it  
> works. same with wget
> 
> So when I am trying to register via  
> OS\>suse\_register -a regcode-sles= -a email= -L  
> /root/.suse\_register.log
> 
> it runs into a TCP timeout. but since i can access the register web page  
> via firefox, network settings should not be the problem.
> 
> I am 90% sure it has something to do with suse\_register or curl not  
> accepting the certificate.[/color]

What does “export | grep proxy” output?

I’m guessing it won’t include https\_proxy so if you “export  
https\_proxy=$http\_proxy” the suse\_register command should then work.

Note I don’t believe suse\_register uses the .curlrc file.

## HTH.

Simon  
SUSE Knowledge Partner

* * *

## If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below. Thanks.

---

<div class="post-metadata">

**Author:** ![dafrk](https://avatars.discourse-cdn.com/v4/letter/d/958977/32.png) [@dafrk](https://forums.suse.com/u/dafrk)\
**Post date:** [June 30, 2016, 12:49pm UTC](https://forums.suse.com/t/suse-register-via-proxy/28359/3 "2016-06-30T12:49:42Z")

</div>

thank you, this solved the problem. I don’t get why yast2 proxy does not offer setting the HTTPS Proxy and only sets http.