Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Let's Encrypt complains about "legacy name certbot-dns-transip:dns-transip" #2724

Closed
rigrig opened this issue Oct 25, 2022 · 2 comments
Closed
Labels

Comments

@rigrig
Copy link

rigrig commented Oct 25, 2022

Describe the issue you are experiencing

Using the Let's Encrypt plugin, this shows up in the log:
Plugin legacy name certbot-dns-transip:dns-transip may be removed in a future version. Please use dns-transip instead.

The DNS configuration field already contains this though:

provider: dns-transip

Renewing the certificate does work fine.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

Let's Encrypt

What is the version of the add-on?

4.12.7

Steps to reproduce the issue

  1. Configure the plugin for TransIP DNS challenge
  2. Start the plugin (renewing the certificate works fine)
  3. Look at the log file

Actual behavior:
Log contains the warning Plugin legacy name certbot-dns-transip:dns-transip may be removed in a future version. Please use dns-transip instead.

Expected behavior:
No warning

System Health information

System Information

version core-2022.10.5
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.10.5
os_name Linux
os_version 5.15.72
arch aarch64
timezone Europe/Amsterdam
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 4898
Installed Version 1.28.3
Stage running
Available Repositories 1132
Downloaded Repositories 16
Home Assistant Supervisor
host_os Home Assistant OS 9.2
update_channel stable
supervisor_version supervisor-2022.10.0
agent_version 1.4.1
docker_version 20.10.17
disk_total 13.6 GB
disk_used 8.5 GB
healthy true
supported true
board odroid-n2
supervisor_api ok
version_api ok
installed_addons Terminal & SSH (9.6.1), Network UPS Tools (0.11.0), motionEye (0.18.0), Studio Code Server (5.4.0), Let's Encrypt (4.12.7), ESPHome (2022.10.0), MariaDB (2.5.1), Syncthing (1.15.1), Nextcloud Backup (0.17.6)
Dashboards
dashboards 8
resources 9
views 13
mode storage
Recorder
oldest_recorder_run October 15, 2022 at 11:42
current_recorder_run October 25, 2022 at 05:10
estimated_db_size 272.20 MiB
database_engine mysql
database_version 10.6.8

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/file-structure.sh
writing RSA key
cont-init: info: /etc/cont-init.d/file-structure.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun lets-encrypt (no readiness notification)
s6-rc: info: service legacy-services successfully started
[21:56:52] INFO: Selected DNS Provider: dns-transip
[21:56:53] INFO: Use propagation seconds: 60
[21:56:53] INFO: Increasing DNS propagation limit for TransIP to at least 240 seconds.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugin legacy name certbot-dns-transip:dns-transip may be removed in a future version. Please use dns-transip instead.
Renewing an existing certificate for ****.*****.***
Waiting 240 seconds for DNS changes to propagate
Successfully received certificate.
Certificate is saved at: /data/letsencrypt/live/****.*****.***-0001/fullchain.pem
Key is saved at:         /data/letsencrypt/live/****.*****.***-0001/privkey.pem
This certificate expires on 2023-01-23.
These files will be updated when the certificate renews.
NEXT STEPS:
- The certificate will need to be renewed before it expires. Certbot can automatically renew the certificate in the background, but you may need to take steps to enable that functionality. See https://certbot.org/renewal-setup for instructions.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
If you like Certbot, please consider supporting our work by:
 * Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
 * Donating to EFF:                    https://eff.org/donate-le
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Additional information

DNS configuration field:

provider: dns-transip
transip_username: ******
transip_api_key: |
  -----BEGIN PRIVATE KEY-----
   ***
  -----END PRIVATE KEY-----

I guess this is a duplicate of #2418, but that was auto-closed by the bot.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Nov 24, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 1, 2022
@nl0pvm
Copy link

nl0pvm commented Jan 11, 2023

This issue is still relevant and actual

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants