Can't renew certificate using Home Assist Nginx "Internal Error"

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: [edited]

I ran this command: from the Nginx Proxy Manager => "Renew Now"

It produced this output: Internal Erroy

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

Hi @dhtguru, and welcome to the LE community forum :slight_smile:

*** can't find Non-existent domain

Did you spell the name right?


Does have DNS Records DNS Lookup - Check DNS Records

1 Like

NPM doesn't have a good reputation around here.

Are you an administrator of the system?
[do you have root access?]


Just a newbie to the home assistant platform. I access it through the HA interface not through docker.
Please excuse my ignorance.

Did you follow a guide of some sort?


As an aside, have a look at Tailscale - it's kind of like a VPN mesh thing that you can install on Home Assistant and on your phone etc, that way you can get remote access to your Home Assistant without a public domain and without making it accessible to anyone else.

With regards to your particular setup, I guess you have a server running nginx proxy manager and that in turn is proxying to your Home Assistant (raspberry pi?), so I'm assuming it's nginx that's terminating TLS and home assistant basically isn't involved.

I'd also assume from the empty responses the server is sending that you are filtering traffic based on IP etc, in which case Let's Encrypts http validation will not be able to access your service in order to complete domain validation.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.