Outages by using ddns.freedombox.org

Support
1

I use Debian GNU/Linux 13 (trixie) and FreedomBox Version 25.9.3 on a Raspberry Pi 4 Model B.

Freedombox should be accessible via ddns.freedombox.org. This worked for a single day after installation. However, since the second day, the Freedombox interface has been inaccessible from outside by using ddns.freedombox.org. The system is only accessible within its own network.
I deleted the entire system and reinstalled it. But the same error appeared again.
These problems don’t occur with No-IP.
Are there any problems with your server of ddns.freedombox.org?

2

Update: I had added a third domain using GnuDIP. At first it worked perfectly. But now the same thing happened as with ddns.freedombox.org: Freedombox is no longer accessible from outside via this domain either. Currently only No-IP works. So the problem can’t be with the server of ddns.freedombox.org.
I deleted the Let’s Encrypt certificates and re-applied them. But the websites aren’t accessible. The website with GnuDIP says it’s not secure. There might be problems with the certificates.

letsencrypt
letsencrypt1040×537 22.5 KB

3

I tried to repair the app. But it failed:

App repair completed with errors: Command ‘[‘certbot’, ‘certonly’, ‘–non-interactive’, ‘–text’, ‘–agree-tos’, ‘–register-unsafely-without-email’, ‘–domain’, ‘xxx.ddnsgeek.com’, ‘–authenticator’, ‘webroot’, ‘–webroot-path’, ‘/var/www/html’, ‘–renew-by-default’]’ returned non-zero exit status 1. Command ‘[‘certbot’, ‘certonly’, ‘–non-interactive’, ‘–text’, ‘–agree-tos’, ‘–register-unsafely-without-email’, ‘–domain’, ‘xxx.fbx.one’, ‘–authenticator’, ‘webroot’, ‘–webroot-path’, ‘/var/www/html’, ‘–renew-by-default’]’ returned non-zero exit status 1.

Exception: Command ‘[‘certbot’, ‘certonly’, ‘–non-interactive’, ‘–text’, ‘–agree-tos’, ‘–register-unsafely-without-email’, ‘–domain’, ‘xxx.ddnsgeek.com’, ‘–authenticator’, ‘webroot’, ‘–webroot-path’, ‘/var/www/html’, ‘–renew-by-default’]’ returned non-zero exit status 1.
Command ‘[‘certbot’, ‘certonly’, ‘–non-interactive’, ‘–text’, ‘–agree-tos’, ‘–register-unsafely-without-email’, ‘–domain’, ‘xxx.fbx.one’, ‘–authenticator’, ‘webroot’, ‘–webroot-path’, ‘/var/www/html’, ‘–renew-by-default’]’ returned non-zero exit status 1.

“xxx” is a placeholder

4

Error running action: letsencrypt..obtain(“name.fbx.one”): CalledProcessError(1, [“certbot”, “certonly”, “–non-interactive”, “–text”, “–agree-tos”, “–register-unsafely-without-email”, “–domain”, “name.fbx.one”, “–authenticator”, “webroot”, “–webroot-path”, “/var/www/html”, “–renew-by-default”])
Action traceback:
╞ File “/usr/lib/python3/dist-packages/plinth/actions.py”, line 579, in _privileged_call
╞ return_values = func(*arguments[‘args’], **arguments[‘kwargs’])
╞ File “/usr/lib/python3/dist-packages/plinth/modules/letsencrypt/privileged.py”, line 135, in obtain
╞ subprocess.run(command, check=True)
╞ ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
╞ File “/usr/lib/python3.13/subprocess.py”, line 577, in run
╞ raise CalledProcessError(retcode, process.args,
╞ output=stdout, stderr=stderr)

Error running action: letsencrypt..obtain(“name.ddnsgeek.com”): CalledProcessError(1, [“certbot”, “certonly”, “–non-interactive”, “–text”, “–agree-tos”, “–register-unsafely-without-email”, “–domain”, “name.ddnsgeek.com”, “–authenticator”, “webroot”, “–webroot-path”, “/var/www/html”, “–renew-by-default”])
Action traceback:
╞ File “/usr/lib/python3/dist-packages/plinth/actions.py”, line 579, in _privileged_call
╞ return_values = func(*arguments[‘args’], **arguments[‘kwargs’])
╞ File “/usr/lib/python3/dist-packages/plinth/modules/letsencrypt/privileged.py”, line 135, in obtain
╞ subprocess.run(command, check=True)
╞ ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
╞ File “/usr/lib/python3.13/subprocess.py”, line 577, in run
╞ raise CalledProcessError(retcode, process.args,
╞ output=stdout, stderr=stderr)

“name” is a placeholder.

5

So perhaps it’s a problem with GnuDIP which might be solved with FreedomBox 25.11:
“Other changes:
dynamicdns: Handle showing errors from GnuDIP”

6

I just updated to FreedomBox 25.11. Although I re-obtained the Let’s Encrypt certificates for my two GnuDIP domains, the problem persists: Only the No-IP domain works, but the GnuDIP domains don’t.