[{"_1":2,"_156":-5,"_157":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_135":136},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_85":-5,"_86":87,"_126":-5,"_127":11,"_128":17,"_129":11,"_130":-5,"_131":11,"_132":-5,"_133":134},"canonicalUrl","https://hub.docker.com/r/rhasselbaum/scrappy-ddns/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","rhasselbaum","reponame","scrappy-ddns","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":65,"_66":67,"_68":11,"_69":29,"_70":71,"_76":17,"_77":78,"_82":29,"_83":84},"categories",[],"content_types",[40],"image","date_registered","2015-02-22T19:32:19.990622Z","description","Dynamic DNS-like service that pushes alerts to your mobile devices when your IP address changes.","is_private","last_updated","2018-03-01T12:07:26.139502Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",1250,"repository_type","star_count",2,"status",1,"status_description","active","source","collaborator_count",0,"full_description","# docker-scrappy-ddns\nRuns [Scrappy DDNS](https://github.com/rhasselbaum/scrappy-ddns) in a Docker container with SSL/TLS support out of the box. Scrappy DDNS is a Dynamic DNS-like service that sends push notifications to your mobile devices whenever your public IP address changes. From the [project description](https://github.com/rhasselbaum/scrappy-ddns):\n\n> So what good is a DDNS service that doesn't actually update DNS records? Scrappy might be right for you if:\n\n> * Your DNS hosting service doesn't support true Dynamic DNS and your IP address rarely changes.\n> * You prefer to manage DNS records manually.\n> * You just want to know whenever your IP address changes.\n\nThis dockerized version of Scrappy DDNS runs the web service behind an nginx reverse proxy and enforces SSL/TLS encryption on all connections. This is the recommended way to run Scrappy DDNS on the public Internet.\n\n# Getting started\n\nRead the [Scrappy DDNS README](https://github.com/rhasselbaum/scrappy-ddns) to get up to speed on the basic concepts. You need to create a `token.list` file as described there and obtain an [application key](https://pushover.net/apps/clone/Scrappy_DDNS) on [Pushover](https://pushover.net/). You will also need an X.509 certificate signed by a Certificate Authority (CA) that your dynamic DNS clients trust. A self-signed certificate works fine but your clients must still validate it to prevent eavesdroppers from intercepting your tokens.\n\nWith these items in hand, create a configuration directory on the host to hold your `token.list` file, certificate, and private key arranged like this:\n\n```\n\n +--cert.pem\n +--cert.key\n +--token.list\n```\n\nThe directory can be placed anywhere (e.g. `/etc/scrappyddns`), but the filenames within it must match the ones above. `cert.pem` and `cert.key` are the certificate file and matching private key in PEM-format (base64). These will be used for incoming SSL/TLS connections. The `token.list` file maps alphanumeric tokens in HTTPS requests to servers/networks you want to monitor.\n\nSince the private key and token list files contain sensitive data, you may want to restrict read access to them on the host. The `token.list` file must be readable by UID/GID 33 (the `www-data` or `http` user in many distros). In most cases, the following commands will lock down the files appropriately:\n\n```\nsudo chmod 600 cert.key\nsudo chmod 600 token.list\nsudo chown 33:33 token.list\n```\n\nNow you can start a new Scrappy DDNS container like this:\n\n```\ndocker run -d -p 443:443 -v :/etc/scrappyddns:ro \\\n -e SCRAPPY_PUSH_USER_KEY= \\\n -e SCRAPPY_PUSH_APP_KEY= \\\n --name scrappy-ddns rhasselbaum/scrappy-ddns\n```\n\nWhere:\n* `` is the full path to the configuration directory on the host.\n* `` is your Pushover user key.\n* `` is the Pushover [application key](https://pushover.net/apps/clone/Scrappy_DDNS) for your copy of Scrappy DDNS.\n\nThis starts the service listening for HTTPS connections over port 443 on the host. You can change the exposed port in typical Docker fashion. Whatever port you choose should map to 443 in the container.\n\n# Advanced options\nThe basic configuration shown above will probably suffice for most people. But some more advanced options are also available.\n\n## Configuration variables\nAny variable in the main [scrappyddns.conf](https://github.com/rhasselbaum/scrappy-ddns/blob/master/scrappyddns.conf) configuration file can be overridden with an environment variable by prepending `SCRAPPY_` to its name. For example, to turn up the log level to `DEBUG`, modify the `docker run` command like this:\n\n```\ndocker run -d -p 443:443 -v :/etc/scrappyddns:ro \\\n -e SCRAPPY_PUSH_USER_KEY= \\\n -e SCRAPPY_PUSH_APP_KEY= \\\n -e SCRAPPY_LOG_LEVEL=DEBUG \\\n --name scrappy-ddns rhasselbaum/scrappy-ddns\n```\n\nIf you don't like passing environment variables to `docker run`, you can instead place a [copy](https://raw.githubusercontent.com/rhasselbaum/scrappy-ddns/master/scrappyddns.conf) of `scrappyddns.conf` into your `` and customize it. You only need to include variables that you want to override from the image-supplied defaults. With an external configuration file, the `docker run` command can be made much simpler:\n\n```\ndocker run -d -p 443:443 -v :/etc/scrappyddns:ro \\\n --name scrappy-ddns rhasselbaum/scrappy-ddns\n```\nIf the same variable appears in `scrappyddns.conf` and an environment variable, the latter takes precedence.\n\n## IP address cache\nThe persistent cache that stores the mappings of tokens to IP addresses resides in a Docker volume and can be shared among containers or mounted to a directory on the host like so:\n\n```\ndocker run -d -p 443:443 -v :/var/cache/scrappyddns [...] \\\n --name scrappy-ddns rhasselbaum/scrappy-ddns\n```\nWhere `` is the full path to the directory on the host. This directory must be readable and writable by UID/GID 33 (the `www-data` or `http` user in many distros).\n\n# Troubleshooting\n\nLog output is available through the `docker logs` facility. Misconfigurations or Pushover service interruptions will yield warnings or errors in the log. Currently, there's no retry mechanism for failed calls to the Pushover service.\n\nYou can get more detail about every request Scrappy DDNS receives by setting the `LOG_LEVEL` variable to `DEBUG`. The nginx error log is also included, which cam alert you to problems with the SSL/TLS certificate.","has_starred","hub_user","immutable_tags_settings",{"_72":11,"_73":74},"enabled","rules",[75],".*","is_automated","permissions",{"_79":17,"_80":11,"_81":11},"read","write","admin","user","storage_size",3337550935,"orgData","recentTags",[88],{"_89":40,"_90":91,"_92":93,"_94":95,"_96":97,"_98":99,"_46":115,"_116":91,"_117":29,"_118":52,"_53":119,"_120":121,"_122":106,"_123":115,"_124":62,"_125":17},"content_type","creator",35277,"digest","sha256:054e3641b9b8e2922067f2f8ff85a696447efa0233fce4e025c8e02fedaceccc","full_size",111275877,"id",126541,"images",[100],{"_101":102,"_92":93,"_103":104,"_105":106,"_107":108,"_109":110,"_111":104,"_112":-5,"_113":95,"_59":62,"_114":-5},"architecture","amd64","features","","last_pulled","2026-09-23T06:29:41.75993796Z","last_pushed","2018-03-01T12:07:26Z","os","linux","os_features","os_version","size","variant","2018-03-01T12:07:25.648076Z","last_updater","last_updater_username","media_type","latest","repository",145387,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":137,"_144":145,"_133":154,"_155":11},{"_36":138,"_38":139,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":140,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":65,"_66":67,"_68":11,"_69":29,"_70":141,"_76":17,"_77":143,"_82":29,"_83":84},[],[40],[52],{"_72":11,"_73":142},[75],{"_79":17,"_80":11,"_81":11},"tags",{"_146":60,"_147":-5,"_148":-5,"_149":150},"count","next","previous","results",[151],{"_89":40,"_90":91,"_92":93,"_94":95,"_96":97,"_98":152,"_46":115,"_116":91,"_117":29,"_118":52,"_53":119,"_120":121,"_122":106,"_123":115,"_124":62,"_125":17},[153],{"_101":102,"_92":93,"_103":104,"_105":106,"_107":108,"_109":110,"_111":104,"_112":-5,"_113":95,"_59":62,"_114":-5},[],"canDeleteTags","actionData","errors"]

rhasselbaum/scrappy-ddns

Tags for rhasselbaum/scrappy-ddns