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 add-on and Google JavaScript deprecation #2930

Closed
timothybuchanan opened this issue Mar 22, 2023 · 1 comment
Closed

Let's Encrypt add-on and Google JavaScript deprecation #2930

timothybuchanan opened this issue Mar 22, 2023 · 1 comment
Labels

Comments

@timothybuchanan
Copy link

Describe the issue you are experiencing

I installed the Let's Encrypt add-on, following the docs to get the required certbot file, which I copied to the share folder as google.json. As startup, I got a 403 error that referenced this page: https://dns.googleapis.com/dns/v1/projects/verdant-petal-381321/managedZones?dnsName=ko0y.org.&alt=json. When I visited that link, I found a 401 error that referenced this page: https://developers.google.com/identity/sign-in/web/devconsole-project. When I went there, I found that javascript is being deprecated as authorization.

This is the full text of the 401 error.

{
  "error": {
    "code": 401,
    "message": "Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.",
    "errors": [
      {
        "message": "Login Required.",
        "domain": "global",
        "reason": "required",
        "location": "Authorization",
        "locationType": "header"
      }
    ],
    "status": "UNAUTHENTICATED",
    "details": [
      {
        "@type": "type.googleapis.com/google.rpc.ErrorInfo",
        "reason": "CREDENTIALS_MISSING",
        "domain": "googleapis.com",
        "metadata": {
          "method": "cloud.dns.api.v1.ManagedZonesService.List",
          "service": "dns.googleapis.com"
        }
      }
    ]
  }
}

Am I reading this correctly, that the add-on will have to be rewritten to not use javascript, or is there some other problem here?

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.8

Steps to reproduce the issue

  1. Install the add-on
  2. Choose DNS challenge and save keys file.
  3. start add-on
    ...

System Health information

System Information

version core-2023.3.5
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.10.10
os_name Linux
os_version 5.15.90
arch x86_64
timezone America/Denver
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 4921
Installed Version 1.31.0
Stage running
Available Repositories 1251
Downloaded Repositories 11
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 9.5
update_channel stable
supervisor_version supervisor-2023.03.1
agent_version 1.4.1
docker_version 20.10.22
disk_total 30.8 GB
disk_used 13.5 GB
healthy true
supported true
board ova
supervisor_api ok
version_api ok
installed_addons SSH & Web Terminal (13.0.3), Home Assistant Google Drive Backup (0.110.1), AdGuard Home (4.8.3), ESPHome (2023.3.1), File editor (5.5.0), Mosquitto broker (6.1.3), X10 MQTT Gateway (0.2.0), Z-Wave JS (0.1.76), WeatherFlow to MQTT (3.1.6), SQLite Web (3.7.0), Let's Encrypt (4.12.8)
Dashboards
dashboards 2
resources 4
views 2
mode storage
Recorder
oldest_recorder_run March 14, 2023 at 14:46
current_recorder_run March 22, 2023 at 10:40
estimated_db_size 770.11 MiB
database_engine sqlite
database_version 3.38.5

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?

No response

Additional information

No response

@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 Apr 21, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 28, 2023
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