text:
SSL certificate error

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

Yes

Are you sure you're not using someone else's docker image?

Yes

Have you searched for similar issues (both open and closed)?

Yes

Describe the bug
i have a fresh NPM image running and tried to generate SSL certificate for my domain
i tried both http/dns challenges
for http challenge i get this error:
Communication with the API failed, is NPM running correctly?

or this one:
example.example.com: There is no server available at this domain. Please make sure your domain exists and points to the IP where your NPM instance is running and if necessary port 80 is forwarded in your router.

for the second error i made sure my DNS record is configured as DNS only and not proxied on cloudflare and i have both port 80 and 443 forwarded on my WAN router
if i opted for DNS challenge i get this error
Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-3" --agree-tos --email "xxxx@gmail.com" --domains "example.com" --authenticator dns-cloudflare --dns-cloudflare-credentials "/etc/letsencrypt/credentials/credentials-3" --dns-cloudflare-propagation-seconds 240
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Encountered CloudFlareAPIError adding TXT record: 10000 Authentication error
Error communicating with the Cloudflare API: Authentication error
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

    at ChildProcess.exithandler (node:child_process:397:12)
    at ChildProcess.emit (node:events:390:28)
    at maybeClose (node:internal/child_process:1064:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)

although the API key is working fine
curl -X GET "https://api.cloudflare.com/client/v4/user/tokens/verify" \
     -H "Authorization: Bearer xxxx" \
     -H "Content-Type:application/json"
{"result":{"id":"96ec8dc212843213fb16d363732e6b34","status":"active"},"success":true,"errors":[],"messages":[{"code":10000,"message":"This API Token is valid and active","type":null}]}

Nginx Proxy Manager Version
v2.9.14
i tried the latest as well but i had the same issue and i saw a post here recommending downgrading helped but unfortunately it didn't help me ref. https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1862
To Reproduce
Steps to reproduce the behavior:

Go to the tab "SSL Certificates"
Click on "Add SSL Certificate"
Enter the domains "*.example.com, example.com"
Select "Use DNS Challenge", Cloudflare, and set API Key
Set Propagation Seconds (450 Seconds) (Optional)

Expected behavior
wildcard  SSL certificate to be created
Operating System
ubuntu server 21.10

Any update about this issue?

can you do *.example.com or just example.com?
Anyways i have same error with just example.com, but not when domain is unavailable, maybe this happens if domain points to different location. I'm using cloud flare dns without proxy do i need to use dns challenge?

I am facing the same issue. Have enabled port forwarding for both 80 & 443. keep getting the same errors outlined in the original post

Same Problem here. Can`t renew the or create  SSL via Letsencrypt

guessing im not the only one here today xD

same here

Same here

+1

+1

I'm seeing the same "Communication with the API failed, is NPM running correctly?" on NPM 2.9.19 on a Raspberry Pi using Docker. The error occurs when I test connectivity, but ultimately succeeded in requesting the certificate from Let's Encrypt.

I'm also getting Communication with the API failed, is NPM running correctly?" after pulling :latest this morning. I'm glad its not just me, hopefully we get this fixed. Thanks!!!

Well... u can request a certificate but only the check does currently not work. Requesting and renewing does work just fine ;)

+1 hope solve it

same here

Yep. same here?

Anyone had any luck with a older version ?

Same issue here

Same here, please advise

Same here :/

`Uncaught SyntaxError: Unexpected end of JSON input
FROM
./run: line 19:  1287 Trace/breakpoint trap   (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js`
whenever you try to see if the server reachable, docker logs will display this error.
I've tried to pinpoint script that triggers but had no luck so far

npm       | `QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method wil
l be removed in 3.0
npm       | `QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` met
hod will be removed in 3.0
npm       | QueryBuilder#omit is deprecated. This method will be removed in version 3.0
npm       | Model#$omit is deprected and will be removed in 3.0.

Same problem in all my servers. Nothing changed, worked fine till it doesnt.

Same here. PM works fine on my Oracle Cloud hosts, but I'm facing this issue on my home server.

same here, even install lastest version hardware

same here.

same. no joy. I'm new to all this and I've been beating my head thinking I messed up somewhere.

I'm having the same issue.

Yep, same issue.

The only way I was able to get SSL is to Add host and request the SSL through the Host setup process.

The wall of "same here" messages doesn't speed up the process of resolving this issue and it creates an unnecessary spam for those who follow issues via email.
If you want to help, please provide additional information such as logs, your settings, info about your setup or anything else that you think might be helpful.
If you want to show that you also interested in solving this issue, consider just up-voting initial issue message, so that the counter will go up.
But please, stop spamming "same here"

@Sebekerga Agreed.
Here are most recent logs with Error/Failed tags. Happy to provide more if these are not helpful.
[12/9/2022] [8:44:39 AM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation   Failed to renew certificate npm-13 with error: Some challenges have failed. Failed to renew certificate npm-14 with error: Some challenges have failed. Failed to renew certificate npm-15 with error: Some challenges have failed. Failed to renew certificate npm-17 with error: Some challenges have failed. Failed to renew certificate npm-18 with error: Some challenges have failed. Failed to renew certificate npm-20 with error: Some challenges have failed. All renewals failed. The following certificates could not be renewed:   /etc/letsencrypt/live/npm-13/fullchain.pem (failure)   /etc/letsencrypt/live/npm-14/fullchain.pem (failure)   /etc/letsencrypt/live/npm-15/fullchain.pem (failure)   /etc/letsencrypt/live/npm-17/fullchain.pem (failure)   /etc/letsencrypt/live/npm-18/fullchain.pem (failure)   /etc/letsencrypt/live/npm-20/fullchain.pem (failure) 6 renew failure(s), 0 parse failure(s)     at ChildProcess.exithandler (node:child_process:402:12)     at ChildProcess.emit (node:events:513:28)     at maybeClose (node:internal/child_process:1100:16)     at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

After spending the night on it I found what was my issue.
I'm using NPM as a docker in unRAID, and for whatever reason the port settings of the template (where you specify the port forwarding at docker network level) changed.
Instead of forwarding port 180 to the internal port 80 and port 1443 to the internal port 443, the template was forwarding port 180 to port 180 and port 1443 to port 1443.
I changed it back to forwarding to 80 and 443 and now it's working.

@LucaVignati Thanks for sharing, glad you solved your issue.
But this doesn't explain my case.
I am not using NPM, and my NGINX host is a docker image and ports 80 and 443 are pointing at the NGINX Proxy Manager Docker Container.

The wall of "same here" messages doesn't speed up the process of resolving this issue and it creates an unnecessary spam for those who follow issues via email.
If you want to help, please provide additional information such as logs, your settings, info about your setup or anything else that you think might be helpful.
If you want to show that you also are interested in solving this issue, consider just up-voting initial issue message, so that the counter will go up.
But please, stop spamming "same here"

My apologies, I believe the reason people are adding "same here" or some derivative of that is because it makes them part of the conversation. So, when there is any update on the matter, they get notified. Please forgive me if there is a less intrusive way to accomplish these results. If you know of any, go ahead an inform the forum so future users don't follow the same method.
One a side note. My issue resolved by deleting the host and SSL cert in nginx and recreating it. I have done this a bunch of times in the past already and it didn't work. It just "worked" last night. Not sure why.

"Same Here" -> use the button Subscribe at the top on the right sidebar (pc)
I was having the same problems, and just to test it out, i disabled IPv6 through my docker-compose.yml
#docker-compose.yml
version: "3"
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      # These ports are in format <host-port>:<container-port>
      - '80:80' # Public HTTP Port
      - '443:443' # Public HTTPS Port
      - '81:81' # Admin Web Port
      # Add any other Stream port you want to expose
      # - '21:21' # FTP

    # Uncomment the next line if you uncomment anything in the section
    environment:
      # Uncomment this if you want to change the location of
      # the SQLite DB file within the container
      # DB_SQLITE_FILE: "/data/database.sqlite"

      # Uncomment this if IPv6 is not enabled on your host
      DISABLE_IPV6: 'true'

    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

And now it creating proxy host with ssl work.
Will return when my instance of Nextcloud-aio is up and running, then i can test if my https://sub.domain-name.tld works

@patrick250709 Could you please try getting just the certificate under SSL Certificates tab (Without creating the host first)?
The Communication with the API failed, is NPM running correctly? error comes up when you try to add the Cert before creating the host but after pointing your DNS Records at the NGINX Proxy Manager host.

@patrick250709 No joy for me.
It turned out that my yml already had IPv6 disabled.
Test Server Reachability gives me Communication with the API failed, is NPM running correctly? and trying to request the SSL without testing gives me this:
Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-64" --agree-tos --authenticator webroot --email "abc@example.com" --preferred-challenges "dns,http" --domains "test.example.com"
Another instance of Certbot is already running.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-xyz/log or re-run Certbot with -v for more details.

    at ChildProcess.exithandler (node:child_process:402:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

@Srcodesalittle Exact steps that I used to take every time I created Certs. Since the issue started, nothing has changed. I have tried to reduce to Flexible, no joy either.
I might be missing something very obvious, I just need to sleep on it maybe.

@Srcodesalittle Exact steps that I used to take every time I created Certs. Since the issue started, nothing has changed. I have tried to reduce to Flexible, no joy either.
I might be missing something very obvious, I just need to sleep on it maybe.

Sorry to hear that, the only thing I can think is whether the dns resolver on your docker image is working correctly and if you try too many cert requests, letsencrypt will time you out for a while (logs should tell you this). Other than that, not sure what could be happening.

@Srcodesalittle No, not at all mate.
I will give a try to fresh install on a fresh host to reproduce this. I will report back with results, hopefully with positive ones.

@patrick250709 No joy for me.
It turned out that my yml already had IPv6 disabled.
Test Server Reachability gives me Communication with the API failed, is NPM running correctly? and trying to request the SSL without testing gives me this:
Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-64" --agree-tos --authenticator webroot --email "abc@example.com" --preferred-challenges "dns,http" --domains "test.example.com"
Another instance of Certbot is already running.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-xyz/log or re-run Certbot with -v for more details.

    at ChildProcess.exithandler (node:child_process:402:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

I get the same errors. I didn't change anything in my container since installation a year ago and just started popping this error on new certs, or updating old ones, updating the image didn't solve this issue. I also tried rolling back acme as suggested in the main post but didn't work. Any ideas? This is annoying

Renewing an existing SSL cert is not an issue from the SSL tab.
Generating new SSL cert for a domain that is correctly pointed to the NGINX Proxy Manager fails.
Can you try to generate a new SSL cert for a domain that is pointing to your host, but doesn't have the cert yet?

Today some certificates expired for my sites and I'm struggling to get it back.
Here are the logs from the container:
2022-12-13T19:24:50.625796744Z [12/13/2022] [8:24:50 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
2022-12-13T19:24:50.625869881Z [12/13/2022] [8:24:50 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
2022-12-13T19:24:50.629915615Z [12/13/2022] [8:24:50 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
2022-12-13T19:24:50.896222410Z [12/13/2022] [8:24:50 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
2022-12-13T19:24:51.041405201Z [12/13/2022] [8:24:51 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
2022-12-13T19:24:51.180183421Z [12/13/2022] [8:24:51 PM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
2022-12-13T19:24:51.180235168Z Renewal configuration file /etc/letsencrypt/renewal/npm-1.conf is broken.
2022-12-13T19:24:51.180240077Z The error was: expected /etc/letsencrypt/live/npm-1/cert.pem to be a symlink
2022-12-13T19:24:51.180256288Z Skipping.
2022-12-13T19:24:51.180259414Z Renewal configuration file /etc/letsencrypt/renewal/npm-2.conf is broken.
2022-12-13T19:24:51.180262249Z The error was: expected /etc/letsencrypt/live/npm-2/cert.pem to be a symlink
2022-12-13T19:24:51.180265285Z Skipping.
2022-12-13T19:24:51.180268420Z Renewal configuration file /etc/letsencrypt/renewal/npm-3.conf is broken.
2022-12-13T19:24:51.180280744Z The error was: expected /etc/letsencrypt/live/npm-3/cert.pem to be a symlink
2022-12-13T19:24:51.180284200Z Skipping.
2022-12-13T19:24:51.180287045Z Renewal configuration file /etc/letsencrypt/renewal/npm-4.conf is broken.
2022-12-13T19:24:51.180289951Z The error was: expected /etc/letsencrypt/live/npm-4/cert.pem to be a symlink
2022-12-13T19:24:51.180296834Z Skipping.
2022-12-13T19:24:51.180299749Z Renewal configuration file /etc/letsencrypt/renewal/npm-5.conf is broken.
2022-12-13T19:24:51.180302645Z The error was: expected /etc/letsencrypt/live/npm-5/cert.pem to be a symlink
2022-12-13T19:24:51.180309367Z Skipping.
2022-12-13T19:24:51.180312193Z 0 renew failure(s), 5 parse failure(s)
2022-12-13T19:24:51.180315329Z
2022-12-13T19:24:51.180318194Z     at ChildProcess.exithandler (node:child_process:402:12)
2022-12-13T19:24:51.180321099Z     at ChildProcess.emit (node:events:513:28)
2022-12-13T19:24:51.180323835Z     at maybeClose (node:internal/child_process:1100:16)
2022-12-13T19:24:51.180330327Z     at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
2022-12-13T19:24:51.201348545Z [12/13/2022] [8:24:51 PM] [Nginx    ] › ℹ  info      Reloading Nginx
2022-12-13T20:10:48.684400673Z [12/13/2022] [9:10:48 PM] [Express  ] › ⚠  warning   invalid signature
2022-12-13T20:10:52.155386518Z `QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0
2022-12-13T20:10:52.156477415Z `QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0
2022-12-13T20:10:52.161289113Z QueryBuilder#omit is deprecated. This method will be removed in version 3.0
2022-12-13T20:10:52.163846892Z Model#$omit is deprected and will be removed in 3.0.
2022-12-13T20:10:58.871617045Z [12/13/2022] [9:10:58 PM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #4: CENSORED.si
2022-12-13T20:10:58.871650769Z [12/13/2022] [9:10:58 PM] [SSL      ] › ℹ  info      Command: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --cert-name "npm-4" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation
2022-12-13T20:10:59.249930474Z [12/13/2022] [9:10:59 PM] [Express  ] › ⚠  warning   Command failed: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --cert-name "npm-4" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation
2022-12-13T20:10:59.249986269Z Saving debug log to /var/log/letsencrypt/letsencrypt.log
2022-12-13T20:10:59.249991018Z Renewal configuration file /etc/letsencrypt/renewal/npm-4.conf is broken.
2022-12-13T20:10:59.249994053Z The error was: expected /etc/letsencrypt/live/npm-4/cert.pem to be a symlink
2022-12-13T20:10:59.249997089Z Skipping.
2022-12-13T20:10:59.250000115Z 0 renew failure(s), 1 parse failure(s)
2022-12-13T20:10:59.250014361Z Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

As a workaround I did the following:

Go to /nginx/certificates
Delete the expired certificates
Go to /nginx/proxy
Edit the site
Go to the SSL tab
Select "Request a new SSL Certificate"
Select your checkboxes that you want
Click Save

Renewing an existing SSL cert is not an issue from the SSL tab. Generating new SSL cert for a domain that is correctly pointed to the NGINX Proxy Manager fails.
Can you try to generate a new SSL cert for a domain that is pointing to your host, but doesn't have the cert yet?

Hi I just created a new cert for my domain and it works fine. No issues

Renewing an existing SSL cert is not an issue from the SSL tab. Generating new SSL cert for a domain that is correctly pointed to the NGINX Proxy Manager fails.
Can you try to generate a new SSL cert for a domain that is pointing to your host, but doesn't have the cert yet?

Hi I just created a new cert for my domain and it works fine. No issues

It works only for a while when you first pull the images and make a completely new and fresh container of npm without any volumes saved. Then after I add like 4 hosts, each with it's own cert, it breaks and refuses to even make a new certificate. No matter if I try to add it when adding a new proxy host or directly through the SSL cert tab.

Renewing an existing SSL cert is not an issue from the SSL tab. Generating new SSL cert for a domain that is correctly pointed to the NGINX Proxy Manager fails.
Can you try to generate a new SSL cert for a domain that is pointing to your host, but doesn't have the cert yet?

Hi I just created a new cert for my domain and it works fine. No issues

It works only for a while when you first pull the images and make a completely new and fresh container of npm without any volumes saved. Then after I add like 4 hosts, each with it's own cert, it breaks and refuses to even make a new certificate. No matter if I try to add it when adding a new proxy host or directly through the SSL cert tab.

Not to discount your experience, but my NPM is already running close to ten hosts on different domains. As I mentioned in my comment, that is the state where I added a new cert to a new sub domain and it worked fine.

Renewing an existing SSL cert is not an issue from the SSL tab. Generating new SSL cert for a domain that is correctly pointed to the NGINX Proxy Manager fails.
Can you try to generate a new SSL cert for a domain that is pointing to your host, but doesn't have the cert yet?

Hi I just created a new cert for my domain and it works fine. No issues

It works only for a while when you first pull the images and make a completely new and fresh container of npm without any volumes saved. Then after I add like 4 hosts, each with it's own cert, it breaks and refuses to even make a new certificate. No matter if I try to add it when adding a new proxy host or directly through the SSL cert tab.

Not to discount your experience, but my NPM is already running close to ten hosts on different domains. As I mentioned in my comment, that is the state where I added a new cert to a new sub domain and it worked fine.

That is even more confusing to me then. What version of npm are you using? I'm on v2.9.19 - which should be the latest from docker hub. It did it the first time I set up my server (that was like 2.9.18) and then repulled the images and rebuilt the container and it broke again.

Renewing an existing SSL cert is not an issue from the SSL tab. Generating new SSL cert for a domain that is correctly pointed to the NGINX Proxy Manager fails.
Can you try to generate a new SSL cert for a domain that is pointing to your host, but doesn't have the cert yet?

Hi I just created a new cert for my domain and it works fine. No issues

It works only for a while when you first pull the images and make a completely new and fresh container of npm without any volumes saved. Then after I add like 4 hosts, each with it's own cert, it breaks and refuses to even make a new certificate. No matter if I try to add it when adding a new proxy host or directly through the SSL cert tab.

Not to discount your experience, but my NPM is already running close to ten hosts on different domains. As I mentioned in my comment, that is the state where I added a new cert to a new sub domain and it worked fine.

That is even more confusing to me then. What version of npm are you using? I'm on v2.9.19 - which should be the latest from docker hub. It did it the first time I set up my server (that was like 2.9.18) and then repulled the images and rebuilt the container and it broke again.

I'm on 2.9.18 just checked

hey guys, i just started my own domain. I tried the button it did not work (test if it works) like the thread indicates. but I am able to create ssl cert fine. I dont know about renew as of yet. so just letting you know that the creation part is working for me.

This morning all my sites are greeting visitors with a red background and "Google Safe Browsing recently detected phishing", it must be related to recent certificate shenanigans... Ohh joy.

Hello, in my case I solved the problem.
First I also got this "internal error" or "Communication with the API failed, is NPM running correctly?".
Then I removed the certificat and tried to recertify it and got the same, but got the message in the red box "Another instance of Certbot is already running".
My solution I found: https://community.letsencrypt.org/t/solved-another-instance-of-certbot-is-already-running/44690
After doing that I registered the certificat by the "edit proxy host" menu!

@kitoming Yes, but that still doesn't solve the problem with getting new certificated under 'SSL Cert' tab. A fresh cert without host pointing at a service.
By way of update, I have installed a new droplet on DO, with a fresh IP, with fresh Docker, with fresh install of NGINX Proxy Manager, and tried to 'Test reachability', still gives me the same error. Not sure if it is even worth typing here, as no contributors or maintainers of this project have replied.

Hi all,
In my case the error got resolved by itself. I have tried many of the things above. Initially disabling force SSL and trying failed but it worked the next day. From last couple of days all the methods are working as expected. I personally think LetsEncrypt have updated something recently.

Hi all, In my case the error got resolved by itself. I have tried many of the things above. Initially disabling force SSL and trying to generate the certificate failed. However it worked the next day. From last couple of days all the methods are working as expected. I personally think LetsEncrypt have updated something recently.

I can not reproduce that. Still none of the certificate generation methods works for me, even above cloudflare workaround has no effect.

Hi all, In my case the error got resolved by itself. I have tried many of the things above. Initially disabling force SSL and trying to generate the certificate failed. However it worked the next day. From last couple of days all the methods are working as expected. I personally think LetsEncrypt have updated something recently.

I can not reproduce that. Still none of the certificate generation methods works for me, even above cloudflare workaround has no effect.

Try these
-> Create Proxy, close
-> edit proxy, request SSL without force
Forgot to mention, I had to do the DNS Challenge way couple of times before getting the SSL to work without DNS challenge

My NPM was working fine for months, now I just realized that it does not auto-renew certificates anymore (which it did until a certain point in time, maybe the last update?).
The odd thing is, issuing new certificates works. Also when I manually click on "renew now", it renews without any issues. But when I click on "test server reachability" I get "Communication with the API failed, is NPM running correctly?". So basically I am just missing the automatism to not have to renew my certificates manually every few months.
Is NPM not even trying to renew or where would I see its failed attempts? In the audit log I just see user actions from my side.

@bigbeka
I am following your chat ,I am also facing same issues that you were mentiond, Did you solved that issue?

Test Server Reachability gives me Communication with the API failed, is NPM running correctly? and trying to request the SSL without testing gives me this:
Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-64" --agree-tos --authenticator webroot --email "abc@example.com" --preferred-challenges "dns,http" --domains "test.example.com"
Another instance of Certbot is already running.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-xyz/log or re-run Certbot with -v for more details.

    at ChildProcess.exithandler (node:child_process:402:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

step 1: The above issue is solved by opening the instance or server 80 port to public(check for your server in Digital ocean or others )
step 2:Then try to request new ssl certificate

@nagalakshmi896 Step 1 does not make sense as anyone using NGINX Proxy Manager need to expose port 80 to public.

@nagalakshmi896 Step 1 does not make sense as anyone using NGINX Proxy Manager need to expose port 80 to public.

@bigbeka
please try by open the inbound rules 80 and 443

I am having the same issue as everything above. I initially thought it may have been a change I made to my firewall policies so I reverted them. The issue persisted.
The only way I was able to get it working again was the following:
Delete SSL Certificate for the host.
Delete & Recreate the host and then request a new certificate

@jc21 is there any new information. No workaround works for me.

Some friendly person on Reddit pointed me to the settings for the host, seemed to do the trick for me.

Try using the SSL request through the host setup, rather than trying to set it up before configuring a new host. Not sure why but my NPM (different setup, stand alone docker host) won’t allow me to request the cert from the SSL section, I have to use the SSL section in the new host setup in order for it to work.
https://imgur.com/a/OW1Jp2o

I don't think this solves the problem.
The main point of getting SSL before setting up the host is to check if the Domain pointing at the public IP has actually propagated or not, hence the need for SSL tab, and the need for "Test" button.
If the domain is not pointing to the correct IP, and you request SSL from Let's Encrypt, you might get penalised for this and get temporary ban. 🤷♂

Some friendly person on Reddit pointed me to the settings for the host, seemed to do the trick for me.

Try using the SSL request through the host setup, rather than trying to set it up before configuring a new host. Not sure why but my NPM (different setup, stand alone docker host) won’t allow me to request the cert from the SSL section, I have to use the SSL section in the new host setup in order for it to work.
https://imgur.com/a/OW1Jp2o

Crazy thing for me is that I can confirm that I see all the error messages given above, but after "some time" the expiration date of my SSL certs changed and they have been renewed even though an error was shown. Sadly, I do not see any other error messages in addition to those that have been reported here.

I had this issue myself, and while reading through this thread last week suddenly everything just started working again.
I didn't think much of it and continued to use it, but now the issue is back. I've read through all the suggestions here and haven't had any results.
I've been following the logs of my container with 'docker logs --folllow [container ID]' while implementing these fixes, and I haven't seen anything that strikes me as some major error. In fact, it seems like everything is fine. It's getting the SSL certs, its storing the certs, etc. But when testing server readability I get the same error and this output from the logs:

I see its giving me an uncaught syntaxerror, but I wouldn't even know where to begin fixing that. I hope this helps somehow.

I had this issue too, and when i create new cert, output is:
"Another instance of Certbot is already running"
My solutions:
To find the certbot process, try:
ps -ef | grep certb
The process ID would be the first number after the user, like:
root 5555 5100 …
To kill the process, try:
kill 5555
((replace 5555 with your actual certbot PID#))
Sources:
https://community.letsencrypt.org/t/solved-another-instance-of-certbot-is-already-running/44690/2
Hope to help someone!

I had this issue too, and when i create new cert, output is: "Another instance of Certbot is already running" My solutions: To find the certbot process, try: ps -ef | grep certb The process ID would be the first number after the user, like: root 5555 5100 … To kill the process, try: kill 5555 ((replace 5555 with your actual certbot PID#)) Kill all certbot pid running and retry then i created success new cert.

I saw this potential solution and tried it, but it didn't work for me. I'm getting the certs without issue, and I've never gotten the error you spoke of. I've looked through a bunch of the open issues with people having similar problems and no response from any dev's, so I just migrated to Caddy. I hope there's a fix coming for everyone in the meantime!

Ok, I believe Cloudflare security (double proxies and other bits) block let's encrypt creating and renewing certs. I've tried disabling bits and bobs on cloudflare with no luck. Issue for me started once I switched to Cloudflare (all was working ok on namecheap but of course namecheap doesn't provide same tools and security as cloudflare).
Switching to Cloudflare cert for all my domains and subdomains (8 hosts/subdomains) took less than 5 mins.
Hope this helps you guys:
Log into cloudflare -> SSL/TLS -> Origin Server and create certificate (just one, wildcard certificate will be used for all subdomains)
using notepad
copy and paste certificate into notepad and save as e,g, certificate.crt
copy and paste key into another notepad file and save as key.crt
Log into your NPM:
go to SSL certificates -> add new -> custom
give it a name and then browse and choose cert and key files in the 2 fileds available.
save the cert - should show 15 years expiry date etc.
Go to your domains and subdomains and replace your ssl cert with cloudflare one
All works for me :)

Ok, this steps work for me Docker
re-deploy container
Remote in container console
Run  pip install certbot-dns-cloudflare==$(certbot --version | grep -Eo '0-9+') cloudflare
if you get this error, just update      pip install --upgrade --force-reinstall acme==2.2.0
(https://freeimage.host/i/HEzf6jj)

Same problem here

Have you tried this?
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2011#issuecomment-1422399423

Have you tried this? #2011 (comment)

No, I like Lets Encrypt and I do not have a CloudFlare account nor do I manage my Domains through CloudFlare.  I add about a Host a Year to NPM and everytime I try to do this NPM is broken.  Very anoying.  NPM never got certificate renewal automatically working, every 3 Months I have to go into it and update the certificates by hand.
I guess it is time to switch to another proxy.

I'm getting the "Communication with API failed, are you sure NPM is running correctly" error too, I can't request any new certificate nor renew my existing ones. I didn't change anything in my docker compose or anything, this issue just came up by itself which to me does not make sense. I also can't find any solution on this, except switching to traefik - but I just can't get it working, either, so I hope this will get fixed fast

Hi team, I'm experiencing exactly the same error. In my case I have NPM as an AddOn in HASS.IO, but the error is the same. Let'sencrypt reaches the box but is discarded with a connection refused, so al mappings are ok, but missing a "web server" attending the request.
I've seen that the call to certbot is using --authenticator webroot; so it needs a web server listening on :80 serving the file that lets encrypt is looking for. Which is not the case !!
One solution would be to change to --standalone but I'm not sure if it's possible to configure, somehow, NPM to use --standalone instead.
Thanks
Luis

It seems like this topic/issue has not been resolved, as I came here with the same problem. The author needs to check and see about duplicating and resolving the issue.

I just got 2 notices from Let's Encrypt about certificates expiring soon. I checked NPM to also find I'm getting the "Communication with the API failed, is NPM running correctly?" error when using the "Test Server Reachability" option, and I'm concerned about auto renewal not working. In the past with a different setup I never got cert expiration notices from Let's Encrypt.

So looking at my logs and I am getting the same error about certbot already running.

So I used the guidance in this comment to remove the lock files and this seemed to resolve the certbot is already running issue. I'm still faced with renewal failures. My logs are like this:
[2/25/2023] [4:12:28 AM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
Failed to renew certificate npm-5 with error: Some challenges have failed.
The following renewals failed:
  /etc/letsencrypt/live/npm-5/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
    at ChildProcess.exithandler (node:child_process:402:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
[2/25/2023] [4:14:43 AM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #5: ***.***.***
[2/25/2023] [4:14:43 AM] [SSL      ] › ℹ  info      Command: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --cert-name "npm-5" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation
[2/25/2023] [4:15:07 AM] [Express  ] › ⚠  warning   Command failed: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --cert-name "npm-5" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Failed to renew certificate npm-5 with error: Some challenges have failed.
All renewals failed. The following certificates could not be renewed:
  /etc/letsencrypt/live/npm-5/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
Duplicate relation "access_list" in a relation expression. You should use "a.[b, c]" instead of "[a.b, a.c]". This will cause an error in objection 2.0

So I used the guidance in this comment to remove the lock files and this seemed to resolve the certbot is already running issue. I'm still faced with renewal failures. My logs are like this:
[2/25/2023] [4:12:28 AM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
Failed to renew certificate npm-5 with error: Some challenges have failed.
The following renewals failed:
  /etc/letsencrypt/live/npm-5/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
    at ChildProcess.exithandler (node:child_process:402:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
[2/25/2023] [4:14:43 AM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #5: ***.***.***
[2/25/2023] [4:14:43 AM] [SSL      ] › ℹ  info      Command: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --cert-name "npm-5" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation
[2/25/2023] [4:15:07 AM] [Express  ] › ⚠  warning   Command failed: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --cert-name "npm-5" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Failed to renew certificate npm-5 with error: Some challenges have failed.
All renewals failed. The following certificates could not be renewed:
  /etc/letsencrypt/live/npm-5/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
Duplicate relation "access_list" in a relation expression. You should use "a.[b, c]" instead of "[a.b, a.c]". This will cause an error in objection 2.0

Hi did you manage to resolve this problem i am in same state as yu just with slighter difrent error :(

Just updated to 2.9.20 after seeing @jc21 did a push to Docker Hub. Unfortunately no change in the SSL certificate renewal bug...
0:28:54
[3/16/2023] [12:28:54 AM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
0:28:54
Failed to renew certificate npm-4 with error: Some challenges have failed.
0:28:54
Failed to renew certificate npm-6 with error: Some challenges have failed.
0:28:54
All renewals failed. The following certificates could not be renewed:
0:28:54
  /etc/letsencrypt/live/npm-4/fullchain.pem (failure)
0:28:54
  /etc/letsencrypt/live/npm-6/fullchain.pem (failure)
0:28:54
2 renew failure(s), 0 parse failure(s)
0:28:54
0:28:54
    at ChildProcess.exithandler (node:child_process:402:12)
0:28:54
    at ChildProcess.emit (node:events:513:28)
0:28:54
    at maybeClose (node:internal/child_process:1100:16)
0:28:54
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
0:47:38
`QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0
0:47:38
`QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0
0:47:38
QueryBuilder#omit is deprecated. This method will be removed in version 3.0
0:47:38
Model#$omit is deprected and will be removed in 3.0.

Have you tried this?
#2011 (comment)

hi
yes, i've tried this. It didn't work before, but this time it worked ..
still, I don't have an explanation for the let's encrypt error in npm .. 🤔
but thanks!!

I use NPN on Home Assistant Core all running on a Windows PC. For me disabling the Windows firewall and also pausing ESET allowed to me renew all certs one by one from the SSL certificates list.

My NPM can issue LE certificate normally (domain hosted in CF) but the GUI showing error when doing reachability test. May be a visual bug

That gave me hope for a minute, @tomvanswam - unfortunately when I double-checked the AAAA record correctly points to the same server as the A one in my case 😞

Thanks @tomvanswam - I'm on a VPS so no issues re firewalls, etc. If I delete and recreate them fresh it tends to work, it's the auto-renewal that isn't working. I'll look at the logs again later but have posted in a few other ones re this issue, really hoping there'll be a fix soon.

I did do a first resignation indeed, not a renewal, maybe my luck runs out in 60 days 🙄

I can confirm: I can generate new certificates but cannot renew certificates.
Removing certificates leaves the cert files in place and when running certbot renew in the console it still finds them and tries to renew them.
certbot renew --cert-name npm-42 --force-renewal gives the following error:
Renewal configuration file /etc/letsencrypt/renewal/npm-42.conf is broken. The error was: expected /etc/letsencrypt/live/npm-42/cert.pem to be a symlink Skipping.
What works is to remove the certificate manually in the SSL Certificates tab and generating a new one.

Thanks for confirming, @KoenVanduffel - interesting finding re cert files being left in place after removal from the UI, that was my suspicion too. Quite a hassle to do if lots of subdomains!

I deleted the SSL certificate, yet I can't request a complete new ssl certificate..
It's now even getting more weird. I just tried a refresh on my other domain, this wasn't working at first.
Now it has refreshed it. I now requested a new ssl for the 2nd (sub) domain, it's not working again.

I deleted the SSL certificate, yet I can't request a complete new ssl certificate..
It's now even getting more weird. I just tried a refresh on my other domain, this wasn't working at first. Now it has refreshed it. I now requested a new ssl for the 2nd (sub) domain, it's not working again.

it might be worth trying the steps I put in #2881 and see if they work for you at all for renewing.  For the removals did you do it via UI or command line? As @KoenVanduffel mentions the UI version doesn't seem to properly remove. In that situation I copied a known 'good' certificate from another site on that domain then refreshed it using the steps mentioned in that linked issue.

I've done this now:
Part 2 - turn off Force SSL and then renew
Then it created a new ssl certificate... I'm using this through a HA plugin, not sure on how I would need to do the shell commands, but for now it seemed to be ok again for a couple months.

Turning 'Force SSL' off was the quick fix for me.

Been almost a year and nothing on this issue. To be such a popular application that does see updates, it would be nice to see this fixed.

Theres many forks to this repo, I would recommend tracking one of them and seeing if someone has picked up maintaining the app.

Turning 'Force SSL' off was the quick fix for me.

Fixed it for me, too. Could it be that the wrong (http) challenge is being checked to start a DNS challenge?

Turning 'Force SSL' off was the quick fix for me.

Fixed it for me, too. Could it be that the wrong (http) challenge is being checked to start a DNS challenge?

I have found when SSL renewal fails or a challenge fails, restart the container and try again. Been the simplest workaround for me so far.

"Same"
My setup:
OpenSuse 15.4
Docker 23.0.6
jc21/nginx-proxy-manager 2.10.4 / 2.10.3
When I try to refresh the certificate:

Meanwhile the logs of nginx:
[8/4/2023] [7:30:07 AM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #1: dummy.domain.name.org
[8/4/2023] [7:30:07 AM] [SSL      ] › ℹ  info      Command: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-1" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation
[8/4/2023] [7:30:23 AM] [Express  ] › ⚠  warning   Command failed: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-1" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation
Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
Failed to renew certificate npm-1 with error: Some challenges have failed.
All renewals failed. The following certificates could not be renewed:
  /etc/letsencrypt/live/npm-1/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.

When I try the "Test the server reachability":

[8/4/2023] [7:31:34 AM] [SSL      ] › ℹ  info      Testing http challenge for dummy.domain.name.org
Uncaught SyntaxError: Unexpected end of JSON input

FROM
bash: line 1:   325 Trace/breakpoint trap   (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
``

With Version 2.10.3 on "refresh" and on "Test the server reachability" the error was:
![Screenshot from 2023-08-04 07-42-04](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/51380897/707f980b-adc8-41ad-bead-5320ad4ea798)

Otherwise no changes.

Fixed it for me, too. Could it be that the wrong (http) challenge is being checked to start a DNS challenge?

I have found when SSL renewal fails or a challenge fails, restart the container and try again. Been the simplest workaround for me so far.

Unfortunately not. I tried this before. I'm in a LXD container, where I can ssh into. It's not a port or connection issue. Manual "dry run" also worked.

If anyone wants to give this a try:
My setup is NPM docker running on the same virtual machine as all of my other docker stuff. I use AdGueard Home, with a DNS rewrite of *.mydomain.com - > Local IP of NPM. I figured there was probably some sort of problem of NPM trying to reach stuff but just getting redirected and never leaving my LAN...
So I set up wireguard in the virtual machine that runs all of my docker stuff. I have a subscription to AirVPN and used their config generator. With the VPN connected, I'm able to add/renew certificates.
My guess is that the VPN forces traffic to leave my LAN, which helps things renew properly. Either that, or it just randomly started working while I was messing around with it.

My guess is that the VPN forces traffic to leave my LAN, which helps things renew properly. Either that, or it just randomly started working while I was messing around with it.

I've had this before too, where it suddenly started to work again...

I would like to weigh in here and suggest making sure that "Block common exploits" is disabled in the proxyhost settings for the particular domain you're trying to renew (re-enable it afterwards)

Just to flag this PR I submitted seems to do the trick - https://github.com/NginxProxyManager/nginx-proxy-manager/pull/3121 - I've done renewals on a few servers since and they seem to go through OK. You can test it via the auto-built Docker image in the PR.

I had exactly the same problem as described above.
I checked my router settings and it seems that port 80/443 was not forwarded.
I opened the ports and it fixed that issue

I am using ubuntunu+portainer+npm+uptime kuma. I want to get a certificate for uptime kuma. When I click: "Test Server Reachability" I get an error: "Communication with the API failed, is NPM running correctly?". Any help?
80 and 443 ports are available

@baxenko where are you clicking 'Test Server Reachability'? I've got the Portainer/NPM/Uptime Kuma setup too and all are working fine (using my PR above for NPM to ensure SSL certs issued/renewed OK)

@baxenko I'm pretty certain, at least for me, that it's network related. Probably NAT Loopback. I think NPM sends out a DNS request for your domain, gets pointed at your home network, and your router never lets anything leave. The solution for me was connecting the machine that runs NPM to a VPN. That forced stuff to leave my home network so the certificate stuff could succeed.

I found this that seems to help a lot: https://www.reddit.com/r/nginxproxymanager/comments/166fbka/certbot_renew_internal_error/
Looks like we need a different certbot version packaged into this docker container

https://old.reddit.com/r/nginxproxymanager/comments/166fbka/certbot_renew_internal_error/k1b9fra/
Yeah this work.

I am using ubuntunu+portainer+npm+uptime kuma. I want to get a certificate for uptime kuma. When I click: "Test Server Reachability" I get an error: "Communication with the API failed, is NPM running correctly?". Any help?
80 and 443 ports are available

@EDIflyer , @etymotic
My problem was due to an installed Portainer which prevented npm from updating uptime kuma. A friend of mine wrote instructions on how to properly install it and configure Portainer to detect the container. It worked for me. Thank you all for your help.
✅ Instructions: https://gist.github.com/Vladkarok/12ed9c11282d1659ecf369028c3202e6

Hello everyone
I had the same issue, and it turns out it has something to do with my firewall setting.
I have a pfsense firewall, and when I checked my settings, I found that I allowed only TCP/UDP connection to the web, which I think wasn't enough for nginx to verify the API token.

https://old.reddit.com/r/nginxproxymanager/comments/166fbka/certbot_renew_internal_error/k1b9fra/ Yeah this work.

Thanks, it has fixed my issue. Thanks for sharing the fix.
The following commands ran in the container fixed the issue.
cd /opt/certbot /opt/certbot/bin/pip install certbot==2.6.0 /opt/certbot/bin/pip install -U certbot-dns-godaddy . /opt/certbot/bin/activate && pip install --upgrade pyopenssl

In my case, creating a new certificate did not work for me. The problem was not having created the subdomain in cloudfare and pointing it to my server. Once the subdomain was created in cloud fare I was able to create my new certificate without problems.
En mi caso no me funcionaba crear un nuevo certificado. El problema era no haber creado el subdominio en cloudfare y apuntarlo a mi servidor. Una vez creado el subdominio en cloud fare pude crear mi nuevo certificado sin problemas.

The only way I was able to get SSL is to Add host and request the SSL through the Host setup process.

Thank you so much @bigbeka !  Your comment worked for me. 👍

Okay, after a few hours of frustration, re-installs, and changing router configs, I kept getting the internal error or the communication with the API NPM running correctly?
I have another subdomain outside of NPM with its own certificate, so I decided to do a force renewal and it worked right away. I was about to add a wildcard to that certificate and import it to NPM, but I decided to try it one more time. I created a new certificate from scratch with a fresh API key from Cloudflare.
That's when I noticed something. When using the DNS Challenge option, the credentials file content had the example below:
(not my actual token btw)
Cloudflare API token
dns_cloudflare_api_token = 0123456789ABCDEF0123456789ABCDEF01234567
I replaced the token with my Cloudflare token, and it failed. I then tried it again, this time using single quotes around my token, like this:
dns_cloudflare_api_token = '0123456789ABCDEF0123456789ABCDEF01234567'
IT WORKED!  I checked the credentials file to verify, and it had:
dns_cloudflare_api_token = \0123456789ABCDEF0123456789ABCDEF01234567\
The weird thing was that my credentials file for my previous certificates that I could not renew did not have any quotes or slashes around the token, but they had worked up until now. Anyway, I thought I would share if anyone else was having the same problem.

I had this issue after doing a backup of my folder data and letsencrypt. the problem was that I was not aware of the symlinks on the live folder, so after copying back my backup folders I was not able renew the certificates. to fix this problem I had to update the symlinks for every certificate.
I decided to create a script to fix it, this script can be executed inside the docker container (haven't tested it from the host), it will search for the most recent certificate in the archive folder and create a symlink in the live folder pointing to it.
afterwards you should be able to execute certbot renew
https://gist.github.com/yesid-bocanegra/dfa0cbf0f99a6834340613f43b6610e0

First time caller, long time listener.
I noticed that the jc21/nginx-full has been deprecated in favor of using nginxproxymanager/nginx-full, although, I'm not sure when it was marked deprecated. Even more damning is the fact that the develop and master branches of this repo's README's both use example docker-compose files that still use the jc21/nginx-proxy-manager:latest image.
Strangely enough, it looks like @jc21's account pushed a new image just 12 hours ago, despite this repo not having seen a commit since last month. Even stranger, is that the new image, nginxproxymanager/nginx-full, hasn't seen an update in 9 months!
I have a faint suspicion that most of the issues folks have had in this thread are due to using the deprecated image, IF it truly is deprecated.
I did try spinning up a container with the following docker-compose, but the container exits with code 0 immediately, so I think the ENTRYPOINT may be wrong somewhere.

docker-compose.yaml
```
version: '3.8'
networks:
  default:
    external: true
    name: outbound
services:
app:
image: 'nginxproxymanager/nginx-full:latest'
restart: unless-stopped
ports:
# These ports are in format :
- '80:80' # Public HTTP Port
- '443:443' # Public HTTPS Port
- '81:81' # Admin Web Port
# Add any other Stream port you want to expose
# - '21:21' # FTP
# Uncomment the next line if you uncomment anything in the section
volumes:
  - ./data/data:/data
  - ./data/letsencrypt:/etc/letsencrypt

networks:
default:
external: true
</details>

@nsaccente interesting. I haven't had a chance to play with it, but try nginxproxymanager/nginx-proxy-manager:latest

@etymotic , I attached my docker-compose contents as a <details> element; already using nginxproxymanager/nginx-proxy-manager:latest but no cigar.

Update, it appears that my ISP has changed my IP, which has been the cause of all my troubles. Updating my domain provider's dns with my new IP. I guess I can't put off setting up dyndns any longer :shrug:
The error provided by NPM is... vague at best... misguiding at worst.
Despite this small victory, the following are still true:

nginxproxymanager/nginx-proxy-manager:latest still exits immediately.
jc21/nginx-proxy-manager:latest is the image I got working (however, I'll be pinning to 2.9.18, and manually updating image versions)
The DEPRECATED sentiment on the jc21 image is ... wrong? It's supposed successor crashes on startup and isn't being regularly built

For those having trouble with NPM's SSL certification feature, please make certain that the IP of your server is still valid!

Look. This might seem silly, but I was also having this problem.
Turns out my problem is that I enabled basic WAF protection in my Cloudflare to block anything not coming from Spain and to block Bots.
Well, obviously that blocked Let's Encrypt bot not residing on Spain. Duh. I disabled the filters and it's now working nicely.
I thought I'd leave my 5 cents here if anyone else has been having problems with this.

Well, obviously that blocked Let's Encrypt bot not residing on Spain. Duh. I disabled the filters and it's now working nicely.
I had a very similar issue, along with my isp blocking port 80 and not telling me. No wonder i coudnt renew my cert.

Thought id also leave my 5 cents.

https://old.reddit.com/r/nginxproxymanager/comments/166fbka/certbot_renew_internal_error/k1b9fra/ Yeah this work.

Thanks, it has fixed my issue. Thanks for sharing the fix.
The following commands ran in the container fixed the issue. cd /opt/certbot /opt/certbot/bin/pip install certbot==2.6.0 /opt/certbot/bin/pip install -U certbot-dns-godaddy . /opt/certbot/bin/activate && pip install --upgrade pyopenssl

Its not worked for me 🥲

https://old.reddit.com/r/nginxproxymanager/comments/166fbka/certbot_renew_internal_error/k1b9fra/ Yeah this work.

Thanks, it has fixed my issue. Thanks for sharing the fix.
The following commands ran in the container fixed the issue. cd /opt/certbot /opt/certbot/bin/pip install certbot==2.6.0 /opt/certbot/bin/pip install -U certbot-dns-godaddy . /opt/certbot/bin/activate && pip install --upgrade pyopenssl

Its not worked for me 🥲

Did you by any chance disable "Block Common Exploits" before renewing the cert? (Also wait an hour or so first if you've been spamming the renew button a lot)

The issue for me was always with renewals rather that the initial domain add - #3121 fixes it for me though.

I just successfully (manually) refreshed my certs:

Interesting, all with local per site certs as opposed to DNS ones? Certainly when I tried latest recently it still didn't work and I had to rebase my PR onto latest to her it working (the ACME 'well-known' challenge wasn't getting through otherwise.

authors: AlanMW AlaskaJedi AzSaSiN BL3CKM00N BartAgterbosch Barzoo7 CameronMacG CristianEduardMihai DelScipio Deses DomBrownInOz EDIflyer Evilernie2001 GamerClassN7 HostLabs-LLC JtMotoX KoenVanduffel LucaVignati LuisPalacios Lzyct MarkoS046 OfficialMuffin Radiofreqq RemarkablyCool RobusTetus RobustMarker Sebekerga Srcodesalittle SriharshaShesham Tschakko1993 Voxis Wdrussell1 Yannic-reust abduroshyd ahmedelemamn awad0 balones6531 baxenko bigbeka bmmmm davix3f etymotic evlo g4xx gabbas1 gitrummy gylove1994 holgerflick irhiggs johndoe0815 julianjuan77 kiennt048 kitoming lazyzyf lenschith liveinaus lmatzer lolekuk misaka00251 msawyer91 nagalakshmi896 nrbDev nsaccente patrick250709 prom00 punkyard pwfraley rodneyt rohankm rumplin stackexpress-bhogireddynagalakshmi styxadmin tarkh timnolte timnunes tomvanswam tuanhd8789 vm75 vuanhson wickedyoda yasarza yesid-bocanegra


text:
NPM tries to handle requests interally for /.well-known/acme-challenge/* and responds with 404

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

Yes

Are you sure you're not using someone else's docker image?

Yes

Have you searched for similar issues (both open and closed)?

Yes

Describe the bug

I am running a Mailcow server behind NPM and need to get Letsencrypt certificates for it. Every time a request is made to mailserver.mydomain.com/.well-known/acme-challenge/[acme-challenge-here], NPM responds with a 404 error.
I have tried curl -H "Host: mailserver.mydomain.com" http://[serverIP]:8080/.well-known/acme-challenge/test and it works fine, but when I try curl mailserver.mydomain.com/.well-known/acme-challenge/test, I get the response of:

<title>404 Not Found</title>

404 Not Found

openresty

I can also see this in the NPM logs:
==> ./proxy-host-12_error.log <==
2022/05/31 16:28:25 [error] 479#479: *4286 open() "/data/letsencrypt-acme-challenge/.well-known/acme-challenge/test" failed (2: No such file or directory), client: xx.xxx.xx.xx, server: autoconfig.mydomain.com, request: "GET /.well-known/acme-challenge/test HTTP/1.1", host: "mailserver.mydomain.com"

==> ./proxy-host-12_access.log <==
[31/May/2022:16:28:25 +0000] - - 404 - GET http mailserver.mydomain.com "/.well-known/acme-challenge/test" [Client xx.xx.xx.xx] [Length 150] [Gzip -] [Sent-to xx.xx.xx.xx] "curl/7.64.1" "-"

This seems to suggest that maybe NPM is looking for this file locally instead of actually passing the request to my server?
Nginx Proxy Manager Version

v.9.18
Operating System

Ubuntu Server 20.04

What you describe is exactly the job of NPM. Its the proxy that creates, renews, uses and holds the certs for the services behind it. To do that it captures the calls to the /.well-known/acme-challenge/.
What may be useful for you to know is the /data/letsencrypt directory on the host holds the certs and keys, so it can be shared between NPM and other containers that need those certs. Leaving NPM to update the certs and other containers to simply use them. For instance, I use the NPM created wildcard cert for email services by pointing exim and dovecot at the NPM certs.
If you need permission changes, other container restarts etc letsencrypt has the ability to run scripts, see the renewal-hooks directory.

Hi, thanks so much for your advice - I was just thinking about something like that now! It seems like someone else seems to have had my exact same problem in #779, so sorry for not looking throroughly enough! I'll try adding a renewal hook later and close this for now

Hi,
is it just possible to send .well-know part to mailcow?

There will probably be a way, but I decided not to go down that route because I still want NPM to handle the ACME requests for the other certificates. In the end, it wasn't that hard to just make a posthook script that copies the new certificate from NPM to mailcow when it gets renewed (see #779).

source: gharchive/issue

repo: NginxProxyManager/nginx-proxy-manager

license: MIT

license_type: permissive

license_source: github-api


text:
Added Icon

Fully added Icon (only tested on macOS)

This change will also let this project completely configured for electron-forge, no more electron-builder.

source: gharchive/pull-request


text:
impactLevels does not exist in type 'JextAxeConfigureOptions'

Thanks for this package, it looks great.
I am trying to set up axe-jest using the Setting the level of user impact example in the readme, but typescript errors saying this is not an option?

Object literal may only specify known properties, and 'impactLevels' does not exist in type 'JestAxeConfigureOptions'

I am using jest v27, with @types/jest-axe v3.5, @testing-library/react v12 and React v17.0.2

I did a little bit of digging and figured out that for impactLevels to work, it needs to be defined in the axe-core package's type definition for RunOptions.
Alternatively, we can amend it in the index.d.ts file of the @types/jest-axe package like so:
export interface JestAxeConfigureOptions extends RunOptions {
    globalOptions?: Spec | undefined;
    impactLevels?: ImpactValue[]; // <-- added change
}

Maybe @NickColley can give me some guidance to see if that's an acceptable option. If so, I can submit a PR so that we can get this issue taken care of.

I think the types are defined in a separate repository? So if you can find that I think they'd be okay with you contributing there. I'm not a big type script person so that's why it's not used directly in this project. I might consider doing those comments that turn into typescript compatible hints?

@NickColley @chrisrhymes I opened a PR with the @types/jest-axe project: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/62022

@NickColley @chrisrhymes impactLevels support has finally been added to @types/jest-axe. That should resolve this issue. We are all good to go! 👍🏼

Cheers!

authors: NickColley chrisrhymes shunchu

repo: NickColley/jest-axe


text:
ArgumentOutOfRangeException after using "remove duplicates" tool

I applied a filter for removing duplicate frames with 95% similarity. Then when I played the recording, the Windows .NET alert appeared and showed this:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at ScreenToGif.Windows.Editor.FrameListView_SelectionChanged(Object sender, SelectionChangedEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.Controls.ListBox.OnSelectionChanged(SelectionChangedEventArgs e)
at System.Windows.Controls.Primitives.Selector.SelectionChanger.End()
at System.Windows.Controls.Primitives.Selector.SelectionChanger.SelectJustThisItem(ItemInfo info, Boolean assumeInItemsCollection)
at System.Windows.Controls.Primitives.Selector.OnSelectedIndexChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
at System.Windows.DependencyObject.SetValueCommon(DependencyProperty dp, Object value, PropertyMetadata metadata, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType, Boolean isInternal)
at System.Windows.DependencyObject.SetValue(DependencyProperty dp, Object value)
at ScreenToGif.Windows.Editor.TimerPreview_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3101.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
ScreenToGif
Assembly Version: 2.13.3.0
Win32 Version: 2.13.3.0
CodeBase: file:///C:/Program%20Files%20(x86)/ScreenToGif/ScreenToGif.exe
PresentationFramework
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3101.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.dll
WindowsBase
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3101.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3101.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
System
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
PresentationCore
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3101.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/PresentationCore/v4.0_4.0.0.0__31bf3856ad364e35/PresentationCore.dll
System.Xaml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3101.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xaml/v4.0_4.0.0.0__b77a5c561934e089/System.Xaml.dll
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
PresentationFramework.Aero2
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework.Aero2/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.Aero2.dll
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
PresentationFramework-SystemXmlLinq
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework-SystemXmlLinq/v4.0_4.0.0.0__b77a5c561934e089/PresentationFramework-SystemXmlLinq.dll
PresentationFramework-SystemXml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework-SystemXml/v4.0_4.0.0.0__b77a5c561934e089/PresentationFramework-SystemXml.dll
UIAutomationTypes
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3101.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/UIAutomationTypes/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationTypes.dll
System.Runtime.Serialization
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
SMDiagnostics
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/SMDiagnostics/v4.0_4.0.0.0__b77a5c561934e089/SMDiagnostics.dll
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System.ServiceModel.Internals
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Internals/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Internals.dll
UIAutomationProvider
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3101.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/UIAutomationProvider/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationProvider.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

I suppose it's also worth noting that I removed some frames using "delete all previous" from the start of the video before performing the step described above.

Hi, I was not able to reproduce this bug.
I created a recording with 24 frames, then I selected the third frame and clicked to "delete previous".
After that, I clicked to remove frames with at least 99.5 % similarity (due to my recording having less pixel changes).

I also tried to select the latest frame before applying "Remove duplicates" to check if the app was able to move the selection to a smaller index (22 to 14). It also didn't crash.

I was able to create a gif afterwards and the program worked great otherwise. I tried just now to reapply the filter to my recent projects and the error did not occur again. I suppose I could have kept the original, sorry about that.

It was strange that the Exception was not caught by my custom dialog window. It went straight to the .Net dialog.
I'll keep trying to find this crash, but if I fail to do so, I'm going to add a simple check under FrameListView_SelectionChanged (to avoid the crash, at least).

I create a pull request may have relationship with this problem.

authors: NickeManarin dgbrokaw laiqun

repo: NickeManarin/ScreenToGif

license: MS-PL


text:
Add Dark Mode

Objective
Add dark mode in the following contexts

App
Storybook

To do so, I will need to investigate about possible alternatives which will need the lowest code maintenance, as well as a clean implementation.

Is blocked by: none

Tasks:

Research

[x] Look for dark Bulma styles
[x] Look for style settings at OS or browser level
[x] Look for ThemeProvider articles in React (only from StyledComponents)
[x] Look for theme switcher (light/dark) in Storybook

Development

[ ] Implement it on Storybook

[x] Add theme swticher to its configuration
[ ] Check themes are well implemented on all atom level components
[ ] Check themes are well implemented on all molecule level components
[ ] Check themes are well implemented on all organism level components
[ ] Check themes are well implemented on all template level components

[ ] [WIP] Implement it on the App

[x] Change Bulma styling injection from calling the stylesheet to implementing the npm package
[ ] Create an idea to toggle the mode for each user (by localStorage or by configurations maintained in a db)
[ ] Implement mentioned idea above
[ ] Add needed UT

First article I have founded related to Browser-level implementation

Bulma has been installed from its npm package and reused with node-sass to create style files for storybook and the public app
Scripts have been included in the PR

Have in mind that update react-scripts from 4.0.X to 5 could arise some build errors related to JSON object deconstruction.
The way to solve that is to make the same deconstruction but as a JS constant (the JSON reference must be imported as a const)

The best tutorial to implement Dark mode in storybook (based on my approach using prefers-color-scheme) is this long but carefully explained article

repo: NicolasOmar/my-pets


text:
如何修改滑快颜色

多谢

dotStyle，用 scss 的话还可以直接改颜色变量
文档：https://nightcatsama.github.io/vue-slider-component/#/zh-CN/style

repo: NightCatSama/vue-slider-component

license: mit

license_source: bigquery


text:
Whitelist turns on again after a reload/restart

Hello,
if I set the whitelist to off and then reload or restart the Server the whitelist is on again.
I am not sure if this is a bug or the intention of the plugin. I connected the MySQL Database successfully.
Is it somehow possible to save the state of the whitelist?
Thank you
best regards

Hi. Unfortunately, when you change the state of the whitelist via command, it is not saved on reboot. If you want the state to be saved, I recommend to switch in the config with a parameter. I will fix this issue in the next version of the plugin.

Hi. Unfortunately, when you change the state of the whitelist via command, it is not saved on reboot. If you want the state to be saved, I recommend to switch in the config with a parameter. I will fix this issue in the next version of the plugin.

Thank you for the answer. How exactly do you mean "I recommend to switch in the config with a parameter."?
Thank you
Best regards

I'm referring to this parameter. (See screenshot).

I apologise for the long reply.

I'm referring to this parameter. (See screenshot).

I apologise for the long reply.

oh sorry didn't see that option... no problem and thank you for the reply
Have a nice week
Best regdards


text:
Add CI workflow to build this crate on Linux

Add CI workflow to build zkllvm-rslang-types using rslang on Linux.
Steps:

Install latest release of rslang (described in readme)
Build zkllvm-rslang-types crate

cargo +zkllvm build --release --target assigner-unknown-unknown

(optional) Build examples

cargo +zkllvm build --examples --target assigner-unknown-unknown

Right now we are considering removing this repository. So this issue is no longer actual.

repo: NilFoundation/zkllvm-rslang-types


text:
'RemovePropertyPrivate/Public' removes the word but doesn't remove spaces

The following code:
Property Private String psStringProp "teststring"
Property Public String psStringProp "teststring"

turns into:
Property         String psStringProp "teststring"
Property        String psStringProp "teststring"

The keywords are removed, but an ugly empty space is left behind; this should be reduced to 1 space in my opinion. Not sure if this is intentional or a bug, but in my opinion this is a bug.

Fixed!

authors: Caeylinity NilsSve

repo: NilsSve/DfRefactor


text:
admin-app: Add variant to status

This patch adds a new byte to the status reported by the admin-app: the hardware variant (lpc55, nrf52).
Fixes: https://github.com/Nitrokey/nitrokey-3-firmware/issues/206
Open question:

Should we have a separate variant for the usbip runner?

lgtm

Should we have a separate variant for the usbip runner?

Would say: yes

Added a  usbip variant.

authors: daringer robin-nitrokey


text:
尔雅

尔雅内容是空的

感谢您的关注，我们刚刚更新了《尔雅》正文部分

xue xue!

authors: Greenhorntc xiu-ze

repo: NiuTrans/Classical-Modern


text:
Option default value is somehow munged when indexed

From the API:

The value is actually false. This makes me concerned that the indexing could be munging other kind of values into different representations of their actual definition.

Related, #69, possibly the same solution. #69 is likely a specific case of this more generic issue.
It seems that treating all default and example values as strings is fraught with perils.

repo: NixOS/nixos-search