Package Details: noip 2.1.9-7

Git Clone URL: (read-only, click to copy)
Package Base: noip
Description: Dynamic DNS Client Updater for services
Upstream URL:
Licenses: GPL
Submitter: xyproto
Maintainer: runnytu
Last Packager: runnytu
Votes: 50
Popularity: 0.003579
First Submitted: 2014-08-01 09:28 (UTC)
Last Updated: 2021-08-21 10:47 (UTC)

Latest Comments

1 2 Next › Last »

runnytu commented on 2021-08-21 10:50 (UTC)

@rrafal1337, done with the same version to avoid other users to upgrade.

rrafal1337 commented on 2021-08-19 19:47 (UTC)

Works fine on aarch64 architecture. Just need to be added to PKGBUILD file.

alexei commented on 2017-06-19 22:26 (UTC)

You need to add and to [Unit], and enable systemd-networkd-wait-online service. Otherwise, the service starts as soon as systemd-networkd starts and fails to get the IP, before the network is actually configured. Not sure why exactly, but ddclient doesn't have this problem, so just use ddclient instead.

goetzc commented on 2016-09-23 16:03 (UTC) (edited on 2016-09-23 16:36 (UTC) by goetzc)

This noip official client was removed from Debian and Ubuntu as it seems to have security issues (for example sends the password unencrypted over the internet).[1] @eddie1985 you might try ddclient and optionally another DDNS providers, like Dynu or DNS Dynamic. See the link for more info.[2] [1] [2]

eddie1985 commented on 2016-09-23 09:48 (UTC)

I have the same problem on my Raspberry Pi 3: noip2[183]: Read from failed (Connection reset by peer) noip2[183]: Can't get our visible IP address from I check the noip2.service, it seems right: Requires=systemd-resolved.service After=systemd-resolved.service Solutions? Thanks

matiwinnetou commented on 2016-01-02 22:43 (UTC)

Works like a charm after a restart on my raspberry pi2, thanks for an update, this was really annoying.

runnytu commented on 2016-01-02 14:40 (UTC)

@des-b & @goetzc, Updated with the changes in service file.

goetzc commented on 2015-12-31 15:20 (UTC)

I'm also seeing the same issue as des-b. Those changes to the systemd service file seem to be needed.

des-b commented on 2015-10-27 17:00 (UTC)

I have some issues on my Raspberry Pi: noip2[183]: Read from failed (Connection reset by peer) noip2[183]: Can't get our visible IP address from This happens after a reboot and from there at every attempt to update my ip address. If I restart the service with `systemctl restart noip2` it works nicely. However it also works from reboot by overriding some settings in the noip service: Requires=systemd-resolved.service After=systemd-resolved.service Maybe this should be added to the noip.service file. Or choose some other target which includes systemd-resolved?