Package Details: noip 2.1.9-7

Git Clone URL: https://aur.archlinux.org/noip.git (read-only)
Package Base: noip
Description: Dynamic DNS Client Updater for no-ip.com services
Upstream URL: http://www.no-ip.com/downloads.php?page=linux
Licenses: GPL
Submitter: xyproto
Maintainer: runnytu
Last Packager: runnytu
Votes: 41
Popularity: 0.292430
First Submitted: 2014-08-01 09:28
Last Updated: 2016-01-02 14:35

Latest Comments

alexei commented on 2017-06-19 22:26

You need to add Wants=network-online.target and After=network-online.target 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

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] http://askubuntu.com/a/459213/509340
[2] https://wiki.archlinux.org/index.php/Dynamic_DNS

eddie1985 commented on 2016-09-23 09:48

I have the same problem on my Raspberry Pi 3:

noip2[183]: Read from dynupdate.no-ip.com failed (Connection reset by peer)
noip2[183]: Can't get our visible IP address from ip1.dynupdate.no-ip.com

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

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

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

goetzc commented on 2015-12-31 15:20

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

I have some issues on my Raspberry Pi:

noip2[183]: Read from dynupdate.no-ip.com failed (Connection reset by peer)
noip2[183]: Can't get our visible IP address from ip1.dynupdate.no-ip.com

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?

jedr93 commented on 2015-09-04 17:01

/tmp/yaourt-tmp-(user)/aur-noip/./PKGBUILD: Line 31: cc: command not found
ERROR: There was a bug in build ().
Aborting ...

bl0ndynek commented on 2015-02-25 18:17

@TheProgramm3r
You need binutils to be installed because this PKGBUILD is building on Raspberry PI.

TheProgramm3r commented on 2015-02-24 11:07

Currently, the `makepkg -s` fails with "==> Error: Cannot find the strip binary required for object file stripping." On armv6h (Raspberry Pi). I will test on a x86_64 PC today if possible.

All comments