# Install SLES behind a proxy

**URL:** <https://forums.suse.com/t/install-sles-behind-a-proxy/34508>\
**Category:** SLES Install-Boot\
**Created:** [October 31, 2019, 2:14pm UTC](https://forums.suse.com/t/install-sles-behind-a-proxy/34508 "2019-10-31T14:14:13Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![didiw](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@didiw](https://forums.suse.com/u/didiw)\
**Post date:** [October 31, 2019, 2:14pm UTC](https://forums.suse.com/t/install-sles-behind-a-proxy/34508/1 "2019-10-31T14:14:13Z")

</div>

I am going to install SLES 15 SP1 on a system behind a company proxy.  
When I am going to set up the network there is no possibility to configure proxy settings. How can I set up proxy settings?

---

<div class="post-metadata">

**Author:** ![didiw](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@didiw](https://forums.suse.com/u/didiw)\
**Post date:** [November 6, 2019, 1:04pm UTC](https://forums.suse.com/t/install-sles-behind-a-proxy/34508/2 "2019-11-06T13:04:24Z")

</div>

Maybe I need to clarigy my problem:  
I am upgrading a SLES 15 server to SP1. The install works up to the call to [scc.suse.com](http://scc.suse.com), which seems to be mandatory and does not work, because the system is behind a mandatory proxy and I have not seen a way to configure orixy settings (as opposed to opensuse).  
So how do I tell yast installer to use the proxy?

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [November 6, 2019, 2:46pm UTC](https://forums.suse.com/t/install-sles-behind-a-proxy/34508/3 "2019-11-06T14:46:24Z")

</div>

Hi and welcome to the Forum 🙂  
Since it’s an upgrade, you need to ensure your proxy should should accept the SUSE domain (or at least selected  
sites like [updates.suse.com](http://updates.suse.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/"

```

The above needs to be in /root/.curlrc as well.

---

<div class="post-metadata">

**Author:** ![didiw](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@didiw](https://forums.suse.com/u/didiw)\
**Post date:** [November 8, 2019, 12:04pm UTC](https://forums.suse.com/t/install-sles-behind-a-proxy/34508/4 "2019-11-08T12:04:09Z")

</div>

The problem was due to name resolution, both with the proxy name name and [scc.suse.com](http://scc.suse.com).  
Now when I call SUSEConnect, I get the following error message:

> [@](#):
>
> Error: Connection refused by server [https://scc.suse.com](https://scc.suse.com)

Connecting to [scc.suse.com](http://scc.suse.com) using wget works, so no idea what the problem is.

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [November 8, 2019, 1:32pm UTC](https://forums.suse.com/t/install-sles-behind-a-proxy/34508/5 "2019-11-08T13:32:30Z")

</div>

[QUOTE=didiw;58817]The problem was due to name resolution, both with the proxy name name and [scc.suse.com](http://scc.suse.com).  
Now when I call SUSEConnect, I get the following error message:

Connecting to [scc.suse.com](http://scc.suse.com) using wget works, so no idea what the problem is.[/QUOTE]  
Hi  
What about curl and https?

---

<div class="post-metadata">

**Author:** ![didiw](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@didiw](https://forums.suse.com/u/didiw)\
**Post date:** [November 8, 2019, 3:12pm UTC](https://forums.suse.com/t/install-sles-behind-a-proxy/34508/6 "2019-11-08T15:12:45Z")

</div>

I had used https for sure since port 443 was given.

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [November 8, 2019, 3:42pm UTC](https://forums.suse.com/t/install-sles-behind-a-proxy/34508/7 "2019-11-08T15:42:33Z")

</div>

> [@didiw;58819](#):
>
> I had used https for sure since port 443 was given.

Hi  
So without authentication you can get to [scc.suse.com](http://scc.suse.com);

```auto
curl https://scc.suse.com
openssl s_client -connect scc.suse.com:443
```

---

<div class="post-metadata">

**Author:** ![didiw](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@didiw](https://forums.suse.com/u/didiw)\
**Post date:** [November 8, 2019, 4:35pm UTC](https://forums.suse.com/t/install-sles-behind-a-proxy/34508/8 "2019-11-08T16:35:18Z")

</div>

curl works, (is redirected to login poage)  
openssl is not in the installation system

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [November 8, 2019, 4:44pm UTC](https://forums.suse.com/t/install-sles-behind-a-proxy/34508/9 "2019-11-08T16:44:20Z")

</div>

[QUOTE=didiw;58821]curl works, (is redirected to login poage)  
openssl is not in the installation system[/QUOTE]  
Hi  
Hmmm, wonder if that may be the problem. Is it possible to try from another system with openssl?

---

<div class="post-metadata">

**Author:** ![didiw](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@didiw](https://forums.suse.com/u/didiw)\
**Post date:** [November 18, 2019, 12:33pm UTC](https://forums.suse.com/t/install-sles-behind-a-proxy/34508/10 "2019-11-18T12:33:03Z")

</div>

[QUOTE=malcolmlewis;58822]Hi  
Hmmm, wonder if that may be the problem. Is it possible to try from another system with openssl?[/QUOTE]  
It has nothing to do with openssl, as far as I know.

---

<div class="post-metadata">

**Author:** ![didiw](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@didiw](https://forums.suse.com/u/didiw)\
**Post date:** [November 18, 2019, 12:54pm UTC](https://forums.suse.com/t/install-sles-behind-a-proxy/34508/11 "2019-11-18T12:54:02Z")

</div>

I have finally managed to solve the problem. to do so, I had to execute the following steps:

```
- abort the graphical installer, in order to fall back to the old "text-graphical" (not the curses based one, that you get when selecting text-based install using F3 in the
  isolinux selector).
  - Enable ssh and shell by hand in Settings
  - Configure the network, (still with no possibility to configure the proxy (in contrary to opensuse at this place). Be sure to select the correct interface, as they are not
      usually in the correct alphabetical order.
  - The shell is just for nothing, but keep it open until you managed to log as in the next step.
  - Log in via ssh and root and password you had to give. If it does not work, you can correct the password or even the network settings in the shell from the previous
     step
   - Set http_proxy, hitps_proxy and socks_proxy(?) by hand or you can mount your root partition to /mnt, copy over /mnt/etc/sysconf/proxy to /etc/sysconf/proxy and
     run . /mnt/etc/profile.d/profile.sh. This also sets your proxy variables. Don't forget to unmount /mnt.
   - Finally start the installation by running yast,ssh.

```

- Does it really have to be so complicated?
- If so, why is there no SuSE-HowTo how to do it? At least I have not found any.
- Is it so uncommon to install/upgrade SLES from behind a mandatory proxy?
- Why can’t the graphical installer just get the proxy settings from /etc/sysconfg/proxy from the system to be upgraded?

Hope this helps  
Regards, Dieter
