# SUSEConnect error: IPAddr::InvalidAddressError: invalid address

**URL:** https://forums.suse.com/t/suseconnect-error-ipaddr-invalid-address/29695
**Category:** SLES Updates
**Created:** [April 21, 2017, 12:00pm UTC](https://forums.suse.com/t/suseconnect-error-ipaddr-invalid-address/29695 "2017-04-21T12:00:49Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![System1](https://avatars.discourse-cdn.com/v4/letter/s/51bf81/32.png) [@System1](https://forums.suse.com/u/System1)
#### Post date: [April 21, 2017, 12:00pm UTC](https://forums.suse.com/t/suseconnect-error-ipaddr-invalid-address/29695/1 "2017-04-21T12:00:49Z")

</div>

Hi,

todays SUSE-SLE-SERVER-12-SP2-2017-624 may break SUSEConnect if your  
environment uses the ‘no\_proxy’ variable.

The cause seems to be that a pre-final PTF made it into the update.  
There is one part missing to the solution of bsc#1014863, namely  
[https://github.com/ruby/ruby/commit/556e3da4216c926e71dea9ce4ea4a08dcfdc1275](https://github.com/ruby/ruby/commit/556e3da4216c926e71dea9ce4ea4a08dcfdc1275)

You can easily apply it by hand to /usr/lib64/ruby/2.1.0/uri/generic.rb  
if you already applied the patch or wait for a fixed version of the patch.

Franz

---

<div class="post-metadata">

### Author: ![HvdHeuvel](https://avatars.discourse-cdn.com/v4/letter/h/3da27b/32.png) [@HvdHeuvel](https://forums.suse.com/u/HvdHeuvel)
#### Post date: [April 24, 2017, 10:54pm UTC](https://forums.suse.com/t/suseconnect-error-ipaddr-invalid-address/29695/2 "2017-04-24T22:54:06Z")

</div>

Hi Franz,

As per details in the bug, I think you both reported this issue, and confirmed the solution… ?  
Anyway, I have added your comment here to the bug again as well.

Thanks  
Hans

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)
#### Post date: [April 28, 2017, 3:28pm UTC](https://forums.suse.com/t/suseconnect-error-ipaddr-invalid-address/29695/3 "2017-04-28T15:28:01Z")

</div>

Hi Hans,

yes, I was (one of?) the reporter of this bug. That’s why I tested the  
channel patch immediately. But to my surprise I saw the same error like  
in the first iteration of the PTF and reported it here.  
Unfortunately I was totally side-tracked after that and didn’t open a  
new SR. But the SLES gods heard me anyway and released  
SUSE-SLE-SERVER-12-SP2-2017-643 earlier this week ;-).

Franz.

---

<div class="post-metadata">

### Author: ![HvdHeuvel](https://avatars.discourse-cdn.com/v4/letter/h/3da27b/32.png) [@HvdHeuvel](https://forums.suse.com/u/HvdHeuvel)
#### Post date: [May 1, 2017, 9:43am UTC](https://forums.suse.com/t/suseconnect-error-ipaddr-invalid-address/29695/4 "2017-05-01T09:43:18Z")

</div>

[QUOTE=Franz Sirl;37646]Hi Hans,

yes, I was (one of?) the reporter of this bug. That’s why I tested the  
channel patch immediately. But to my surprise I saw the same error like  
in the first iteration of the PTF and reported it here.  
Unfortunately I was totally side-tracked after that and didn’t open a  
new SR. But the SLES gods heard me anyway and released  
SUSE-SLE-SERVER-12-SP2-2017-643 earlier this week ;-).

Franz.[/QUOTE]

Hey Franz,

Thanks for the confirmation.  
I did check the bug and was told the fix was on it’s way but I had not had time to update here.

Good to see it is sorted now .

Best regards  
Hans