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: Support IP address for http-validation if specifying a custom ACME Server #3650

Open
CitizenRacer opened this issue Jun 20, 2024 · 1 comment
Labels

Comments

@CitizenRacer
Copy link

Describe the issue you are experiencing

I'm using a custom, private acme server. There's no reason I shouldn't be able to get a cert for an ip address but the integration doesn't let me specify an ip address in the names list.

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?

5.0.18

Steps to reproduce the issue

  1. Under domains, specify an ip address
  2. Run the addon
  3. Get the error message:
    Requested name 10.0.0.8 is an IP address. The Let's Encrypt certificate authority will not issue certificates for a bare IP address.

System Health information

System Information

version core-2024.6.3
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.12.2
os_name Linux
os_version 6.6.33-haos
arch x86_64
timezone America/Los_Angeles
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 5000
Installed Version 1.34.0
Stage running
Available Repositories 1464
Downloaded Repositories 39
HACS Data ok
Home Assistant Cloud
logged_in true
subscription_expiration March 18, 2025 at 5:00 PM
relayer_connected true
relayer_region us-east-1
remote_enabled true
remote_connected true
alexa_enabled true
google_enabled false
remote_server us-east-1-9.ui.nabu.casa
certificate_status ready
instance_id 83b8b314e81b4d9ea5749a5e19ccd248
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 12.4
update_channel stable
supervisor_version supervisor-2024.06.0
agent_version 1.6.0
docker_version 26.1.4
disk_total 116.7 GB
disk_used 46.9 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
board generic-x86-64
supervisor_api ok
version_api ok
installed_addons UniFi Network Application (3.1.0), Log Viewer (0.17.0), Studio Code Server (5.15.0), Samba share (12.3.1), Z-Wave JS UI (3.8.0), Mosquitto broker (6.4.1), File editor (5.8.0), Cloudflared (5.1.12), ESPHome (2024.6.0), Terminal & SSH (9.14.0), Home Assistant Google Drive Backup (0.112.1), MQTT Explorer (browser-1.0.1), Let's Encrypt (5.0.18), rtl_433 MQTT Auto Discovery (0.8.1), rtl_433 (0.5.1), Matter Server (6.1.2), AppDaemon (0.16.6)
keymaster
zwave_integration zwave_js
network_status on
Dashboards
dashboards 4
resources 18
views 16
mode storage
Recorder
oldest_recorder_run June 18, 2024 at 9:18 PM
current_recorder_run June 19, 2024 at 5:14 PM
estimated_db_size 1289.91 MiB
database_engine sqlite
database_version 3.44.2
Spotify
api_endpoint_reachable ok

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

no

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

no

Additional information

No response

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 Jul 20, 2024
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

1 participant