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 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, 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
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.
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 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, 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
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.