Internal error on SSL certificates

I tried to add new SSL certificates and i go this issue when try to generate it :

it was working perfectly fine 2 days ago i pulled the last container and for some reason i got this message (unhealthy) with docker ps

I founded this is docker inspect looks like something is blocking curl wich should not be the case
[
    {
        "Id": "5396c4e1207e3486ccb714d7cf9f2027f8be83c35fcbc5c0393d7cb3120a4609",
        "Created": "2019-07-26T12:05:10.838857676Z",
        "Path": "/init",
        "Args": [],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 15761,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2019-07-29T07:06:18.91961627Z",
            "FinishedAt": "2019-07-29T07:05:44.533099275Z",
            "Health": {
                "Status": "unhealthy",
                "FailingStreak": 23,
                "Log": [
                    {
                        "Start": "2019-07-29T07:11:08.475218801Z",
                        "End": "2019-07-29T07:11:08.698302026Z",
                        "ExitCode": 1,
                        "Output": "  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to localhost port 9876: Connection refused\n"
                    },
                    {
                        "Start": "2019-07-29T07:11:23.708785289Z",
                        "End": "2019-07-29T07:11:23.931405635Z",
                        "ExitCode": 1,
                        "Output": "  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to localhost port 9876: Connection refused\n"
                    },
                    {
                        "Start": "2019-07-29T07:11:38.941957592Z",
                        "End": "2019-07-29T07:11:39.161505674Z",
                        "ExitCode": 1,
                        "Output": "  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to localhost port 9876: Connection refused\n"
                    },
                    {
                        "Start": "2019-07-29T07:11:54.171975308Z",
                        "End": "2019-07-29T07:11:54.424361521Z",
                        "ExitCode": 1,
                        "Output": "  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to localhost port 9876: Connection refused\n"
                    },

When trying to ping my own ip on port 9876 (docker proxy i get this)

I finnaly went back to another snapshot i think the issue was that i auto run the container but if i am right it already does it ?
https://askubuntu.com/questions/620930/how-do-i-autostart-docker-container-at-system-reboot
I let this issue open in case someone has the same issue and Jc is willing to give a look at it c:

Okay i said nothing it did it again and i founded what is the issue. So basiclly create a new proxy host "Request a new SSL certificate". Then confirm, once you have done it remodify the host and add some more domaine, subdomain and go back in ssl certificates and "Request a new SSL certificate" save it and there it is the internal error.

After that it's impossible to use let's encrypt ever again in an ways

I ran into this issue just today. I proceeded under the assumption that it was a bug.
While reviewing the docker logs I noticed it was looking for "npm-4" and "npm-5", but it couldn't find them. Eventually I came around to deleting the error SSL and remaking the proxy host, requesting the SSL again.
When you view docker logs what do they contain?

I've got the same issue.

There is definitely a bug with Let's Encrypt.

I've managed to make it running by simple copying any other cert on place where script looking for and everything start's working:

I've managed to make it running by simple copying any other cert on place where script looking for and everything start's working:

Can you explain me what you did exactly and it's working now ? (Also i am a noob in docker so if you could provide the command to access the docker shell with it would be really nice from you c: !)

I've used Portainer (Docker GUI), but you can do it running bellowed command on your node server:
To list all docker containers:
$ docker ps
CONTAINER ID  IMAGE    COMMAND  CREATED      STATUS      PORTS  NAMES
3xamp13id  my_image          X hours ago  Up X hours         my_container

To enter into container:
$ docker exec -it 3xamp13id bash

Then inside just go into /etc/letsencrypt/live directories and copy any other certificate on place of missing one.

I see intressting thanks ! i hope @jc11 see this so maybe he can foudn a fix for it

Yup, just got the same issue.
Has anyone found a fix yet that doesn't involve messing with the container itself? I'm not at all familiar with Docker, I'm happy that I got it running somehow haha :)
Let's ping @jc21 again to see if it helps ;)

Same here. Running on docker as well.

same, but I have problems with NAT Loopback (bwcause of my router). Could this be an issue?

I've didn't check my logs deeply when it occur, but it can be a case (I'm using it on home configuration and behind of home router as well).

Same issues as above.  Don't know Docker - friend setup for me. Worked forever but had to re-image OS drive (All Virtual stuff through HyperV and none of this was even on OS drive).  After that nothing works. I try to delete all hosts and SSL certs and just get "Internal Error" for everything.  Hoping somebody posts some things to try / command to fix

I think I found the issue. When the URL you gave it isn't reachable it'll act as if everything worked instead of telling you what went wrong. I accidentally gave it an URL that hadn't been configured properly yet.

I started having this same issue yesterday after updating to 2.1.0. Rolling back to 2.0.14 seems to have fixed it.

@lachlan334 it would be nice to know why it failed, the docker logs would have the info. FWIW I'm using 2.1.0 in production and not having these problems.

Guys, I also have unhealthy status of npm-container, but it's works... what will be the recommendations?

@lachlan334 it would be nice to know why it failed, the docker logs would have the info. FWIW I'm using 2.1.0 in production and not having these problems.

The output I'm getting from the health check is % Total    % Received % Xferd   Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left   Speed    0     0    0     0    0     0      0      0 --:--:-- --:--:--  --:--:--     0   0     0    0     0    0     0      0      0 --:--:--  --:--:-- --:--:--     0 curl: (7) Failed to connect to localhost port 9876: Connection refused
Logs are as follows:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.,
[s6-init] ensuring user provided files have correct perms...exited 0.,
[fix-attrs.d] applying ownership & permissions fixes...,
[fix-attrs.d] done.,
[cont-init.d] executing container initialization scripts...,
[cont-init.d] done.,
[services.d] starting services,
[services.d] done.,
[2/21/2020] [2:53:12 AM] [Migrate  ] › ℹ  info      Current database version:<PHONE_NUMBER>5017,
[2/21/2020] [2:53:12 AM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...,
[2/21/2020] [2:53:12 AM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json,
[2/21/2020] [2:53:15 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4,
[2/21/2020] [2:53:15 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6,
[2/21/2020] [2:53:15 AM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized,
[2/21/2020] [2:53:15 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...,
[2/21/2020] [2:53:15 AM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized,
[2/21/2020] [2:53:15 AM] [Global   ] › ℹ  info      Backend PID 206 listening on port 3000 ...,
[2/21/2020] [2:53:16 AM] [Nginx    ] › ℹ  info      Reloading Nginx,
[2/21/2020] [2:53:16 AM] [SSL      ] › ℹ  info      Renew Complete,
`QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0,
`QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0,
QueryBuilder#omit is deprecated. This method will be removed in version 3.0,
Connection Error: Error: read ECONNRESET,
[2/21/2020] [3:53:15 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...,
[2/21/2020] [3:53:16 AM] [Nginx    ] › ℹ  info      Reloading Nginx,
[2/21/2020] [3:53:16 AM] [SSL      ] › ℹ  info      Renew Complete,
Connection Error: Error: read ECONNRESET,
Connection Error: Error: Packets out of order. Got: 1 Expected: 16,
Connection Error: Error: read ECONNRESET,
[2/21/2020] [4:53:15 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...,
[2/21/2020] [4:53:16 AM] [Nginx    ] › ℹ  info      Reloading Nginx,
[2/21/2020] [4:53:16 AM] [SSL      ] › ℹ  info      Renew Complete,
Connection Error: Error: read ECONNRESET,
[2/21/2020] [5:53:15 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...,
[2/21/2020] [5:53:16 AM] [Nginx    ] › ℹ  info      Reloading Nginx,
[2/21/2020] [5:53:16 AM] [SSL      ] › ℹ  info      Renew Complete,
Connection Error: Error: read ECONNRESET,
[2/21/2020] [6:53:15 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...,
[2/21/2020] [6:53:16 AM] [Nginx    ] › ℹ  info      Reloading Nginx,
[2/21/2020] [6:53:16 AM] [SSL      ] › ℹ  info      Renew Complete,
Connection Error: Error: read ECONNRESET,
[2/21/2020] [7:53:15 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...,
[2/21/2020] [7:53:16 AM] [Nginx    ] › ℹ  info      Reloading Nginx,
[2/21/2020] [7:53:16 AM] [SSL      ] › ℹ  info      Renew Complete,
Connection Error: Error: read ECONNRESET,
[2/21/2020] [8:53:15 AM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...,
[2/21/2020] [8:53:15 AM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json,
[2/21/2020] [8:53:15 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...,
[2/21/2020] [8:53:15 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4,
[2/21/2020] [8:53:15 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6,
[2/21/2020] [8:53:16 AM] [Nginx    ] › ℹ  info      Reloading Nginx,
[2/21/2020] [8:53:16 AM] [Nginx    ] › ℹ  info      Reloading Nginx,
[2/21/2020] [8:53:16 AM] [SSL      ] › ℹ  info      Renew Complete,
Connection Error: Error: read ECONNRESET,
[2/21/2020] [9:53:15 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...,
[2/21/2020] [9:53:16 AM] [Nginx    ] › ℹ  info      Reloading Nginx,
[2/21/2020] [9:53:16 AM] [SSL      ] › ℹ  info      Renew Complete,
Connection Error: Error: read ECONNRESET,
[2/21/2020] [10:53:15 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...,
[2/21/2020] [10:53:16 AM] [Nginx    ] › ℹ  info      Reloading Nginx,
[2/21/2020] [10:53:16 AM] [SSL      ] › ℹ  info      Renew Complete,
Connection Error: Error: read ECONNRESET,

@lachlan334 hey buddy I have the same.. but npm is working fine.

If it means anything, I've been getting this error with version 2.0.14 running the docker image jlesage/nginx-proxy-manager

@GregHilston Yep that means a lot. I don't maintain jlesage's images. We're up to 2.1.1 now and port 9876 isn't used internally anymore.
@lachlan334 Looks like you were using that 2.1.1 image, but it doesn't make sense why the Healthcheck is still using a setting from a previous docker image. The correct healthcheck will eventually run a curl command: curl --silent http://<IP_ADDRESS>:81/api/ from within the NPM container.
Perhaps try pulling down the stack entirely and putting it back up, assuming your have directory mounted volumes: docker-compose down && docker-compose up -d

I'm running into a similar problem. Requesting a new SSL certificate generates an Internal Error.
Inspecting the docker container shows it's unhealthy and it's spitting some errors:
[     {         "Id": "9d2d526acb3512e60ca4db020b9ef86b93e859735267d224223ca40f5054b3d4",         "Created": "2020-02-21T02:30:55.239750232Z",         "Path": "/init",         "Args": [],         "State": {             "Status": "running",             "Running": true,             "Paused": false,             "Restarting": false,             "OOMKilled": false,             "Dead": false,             "Pid": 3473,             "ExitCode": 0,             "Error": "",             "StartedAt": "2020-02-21T02:30:58.116917696Z",             "FinishedAt": "0001-01-01T00:00:00Z",             "Health": {                 "Status": "unhealthy",                 "FailingStreak": 20095,                 "Log": [                     {                         "Start": "2020-02-24T16:56:39.096936098+01:00",                         "End": "2020-02-24T16:56:39.294612731+01:00",                         "ExitCode": 1,                         "Output": "  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\ncurl: (7) Failed to connect to localhost port 9876: Connection refused\n"                     },                     {                         "Start": "2020-02-24T16:56:54.409165629+01:00",                         "End": "2020-02-24T16:56:54.726601709+01:00",                         "ExitCode": 1,                         "Output": "  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\ncurl: (7) Failed to connect to localhost port 9876: Connection refused\n"                     },                     {                         "Start": "2020-02-24T16:57:09.810871898+01:00",                         "End": "2020-02-24T16:57:10.019143483+01:00",                         "ExitCode": 1,                         "Output": "  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\ncurl: (7) Failed to connect to localhost port 9876: Connection refused\n"                     },                     {                         "Start": "2020-02-24T16:57:25.125134859+01:00",                         "End": "2020-02-24T16:57:25.335763382+01:00",                         "ExitCode": 1,                         "Output": "  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\ncurl: (7) Failed to connect to localhost port 9876: Connection refused\n"                     },                     {                         "Start": "2020-02-24T16:57:40.435902211+01:00",                         "End": "2020-02-24T16:57:40.643842955+01:00",                         "ExitCode": 1,                         "Output": "  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\ncurl: (7) Failed to connect to localhost port 9876: Connection refused\n"                     }                 ]             }
Here I saw the connection refused on 9876, not knowing what's causing it.
I'm using jc21's image, running version 2.1.1.
I don't mean to hijack, but perhaps this is the same problem as OP's running into.

Here I saw the connection refused on 9876, not knowing what's causing it.
I'm using jc21's image, running version 2.1.1.

Same here ! Using jc21's image, version 2.1.1, on docker bridge.

Not sure if it's a docker bug or expected behaviour but it feels like upgrading a docker image within an already-created container, doesn't update the healthcheck. There were quite a few changes between 2.0.* and 2.1.* of NPM so I recommend bringing down the stack entirely and recreating it.
Using existing data and letsencrypt data mounts will be fine though.

That said, the healthcheck shouldn't affect the ability for a certificate to be renewed.

Thank you for the reply jc21.
I don't know about the other users, but in my case this is a clean container / image of version 2.1.1.
I have recreated it once with re-using the data and let's encrypt folder. But the obtaining of SSL certificates never worked.
I eventually gave up on it and used my synology nas to retreive certificates and manually importing them into Nginx, which worked fine.
But it would be nice to find out why the internal error occurs and why the log is spamming the connection refusal on port 9876.
Is there anything I can submit that could help you give insight on the situation?
Kind regards.

I'm getting the same error and unhealthy status in Docker. I have had the error message pop in the past but at the moment I can still create new certs. I tried deleting the old certs and recreating them but always have the same unhealthy container :(
Outputs from my container below if it helps
Docker:

% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (7) Failed to connect to localhost port 9876: Connection refused

Logs:

Traceback (most recent call last):,
File "/usr/lib/python3.8/site-packages/certbot/_internal/renewal.py", line 64, in _reconstitute,
renewal_candidate = storage.RenewableCert(full_path, config),
File "/usr/lib/python3.8/site-packages/certbot/_internal/storage.py", line 465, in init,
self._check_symlinks(),
File "/usr/lib/python3.8/site-packages/certbot/_internal/storage.py", line 531, in _check_symlinks,
raise errors.CertStorageError(,
certbot.errors.CertStorageError: expected /etc/letsencrypt/live/npm-2/cert.pem to be a symlink,
Renewal configuration file /etc/letsencrypt/renewal/npm-2.conf is broken. Skipping.,
,
... [Repeats up to npm-7] ...
,
at ChildProcess.exithandler (child_process.js:295:12),
at ChildProcess.emit (events.js:210:5),
at maybeClose (internal/child_process.js:1028:16),
at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5),

There is a github-develop docker image that has removed 9876 from the Dockerfile EXPOSE. This was the last trace of this port in the entire codebase and although the 2.1.* images should not be using this port whatsoever, for some reasons that apply to specific people it might make a difference.
So, use the github-develop image tag, make sure the previous container is entirely removed before creating a new one. I'll mention the steps here for anyone who doesn't know:
docker rm -f name_of_nginx_proxy_manager_container
or
docker-compose down
If there is any trace of this port 9876  in your healthchecks after that, then I'll literally flip my desk and rage quit this project.

Removing the container and setting up a new one using the github-develop image solved the internal error when requesting SSL certificates for me.
I can see port 9876 is no longer used by this image as well.
I just managed to get Let's Encrypt certificates for all my proxy hosts directly trough Nginx, what a blessing!
Currently I'm unable to SSH to my device (only allowed from local network and I'm at the office right now), so when I am back home I will check the docker container health status. Will get back to you!

Can confirm!
Used github-develop image and the container becomes healthy again with port 9876 no longer used anymore! I've tried it on 3 different hosts and containers are no longer unhealthy.

There is a github-develop docker image that has removed 9876 from the Dockerfile EXPOSE. This was the last trace of this port in the entire codebase and although the 2.1.* images should not be using this port whatsoever, for some reasons that apply to specific people it might make a difference.
So, use the github-develop image tag, make sure the previous container is entirely removed before creating a new one. I'll mention the steps here for anyone who doesn't know:
docker rm -f name_of_nginx_proxy_manager_container
or
docker-compose down
If there is any trace of this port 9876 in your healthchecks after that, then I'll literally flip my desk and rage quit this project.

I just got home and checked trough SSH what the docker container's health status is. It's looking perfectly fine!
Health": {
"Status": "healthy",
"FailingStreak": 0,
No need to flip the desk and rage quit the project @jc21 ;)

I nuked my container and rebuilt with github_develop and mine is happy and healthy now too. Thanks!

Can also confirm that using the github-develop image fixed the issue.

Yep, after removing the container and using the github-docker image, the certs where updated automatically.

Ok sweet I'll merge and re-release today. Phew :)

So guys, what I need to do? Use the develop of the container? 'Coz I have unhealthy still. Thanks in advance.

@SAOPP unhealthy typically means the container took more than 5 seconds to return an OK status. If you're able to create new SSL certificates, you should be good to go. The unhealthy status isn't a big deal.

Yes I understood it, just interesting, and yes I can create a new certs, but I see guys talked about not possible auto renewal certs or I misunderstood?

Please forgive my being uninformed on Docker, but when will this get pushed out to places like Dockerhub? I'm using an Unraid environment.
Is there a way I can upload and use my own certificate in the meantime, such as a Cloudflare certificate?

@Foxglove-X I believe it was already pushed about 4 days ago.
Check the tags under the Docker Hub page.
https://hub.docker.com/r/jc21/nginx-proxy-manager/tags

Ah I see! Mine was pulled from jlesage/nginx-proxy-manager/ which is 5 months out of date.
That must be some other Docker image that's not as well maintained. I should probably use this one instead. Thank you.

jlesage will have to update his own docker images each time I release mine. I don't have an unraid setup myself so I don't know what changes are required to make it work

Hello,
I just installed the latest version of npm.
docker-compose.yml
version: "3"
services:
  app:
    image: jc21/nginx-proxy-manager:latest
    restart: always
    ports:
      - 80:80
      - 81:81
      - 443:443
    volumes:
      - ./config.json:/app/config/production.json
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
    depends_on:
      - db
    environment:
    # if you want pretty colors in your docker logs:
    - FORCE_COLOR=1
  db:
    image: mariadb:latest
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: "npm"
      MYSQL_DATABASE: "npm"
      MYSQL_USER: "npm"
      MYSQL_PASSWORD: "npm"
    volumes:
      - ./data/mysql:/var/lib/mysql

config.json
{
  "database": {
    "engine": "mysql",
    "host": "db",
    "name": "npm",
    "user": "npm",
    "password": "npm",
    "port": 3306
  }
}

I tried to add new SSL certificates and i go this issue when try to generate it :

I have

Thank for all

@rto54 without the logs from the docker containers themselves, there's not a whole lot anyone can debug. Can you provide them?

@nldoty, You can help me for this.
I am a beginner with the docker :-(
Thank

[4/7/2020] [6:55:06 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [6:55:07 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-2" --agree-tos --email<EMAIL_ADDRESS>--preferred-challenges "dns,http" --webroot --domains "unifi.ophiuchus.fr" ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
Plugins selected: Authenticator webroot, Installer None,
Obtaining a new certificate,
Performing the following challenges:,
http-01 challenge for unifi.ophiuchus.fr,
Using the webroot path /data/letsencrypt-acme-challenge for all unmatched domains.,
Waiting for verification...,
Challenge failed for domain unifi.ophiuchus.fr,
http-01 challenge for unifi.ophiuchus.fr,
Cleaning up challenges,
Some challenges have failed.,
,
[4/7/2020] [7:03:09 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:03:24 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:03:32 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:03:42 PM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #2: unifi.ophiuchus.fr,
[4/7/2020] [7:03:43 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot renew --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-2" --preferred-challenges "dns,http" --disable-hook-validation ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
No certificate found with name npm-2 (expected /etc/letsencrypt/renewal/npm-2.conf).,
,
[4/7/2020] [7:03:46 PM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #1: jeedom.ophiuchus.fr,
[4/7/2020] [7:03:48 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot renew --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-1" --preferred-challenges "dns,http" --disable-hook-validation ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
No certificate found with name npm-1 (expected /etc/letsencrypt/renewal/npm-1.conf).,
,
[4/7/2020] [7:05:41 PM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #1: jeedom.ophiuchus.fr,
[4/7/2020] [7:05:43 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot renew --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-1" --preferred-challenges "dns,http" --disable-hook-validation ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
No certificate found with name npm-1 (expected /etc/letsencrypt/renewal/npm-1.conf).,
,
Connection Error: Error: read ECONNRESET,
[4/7/2020] [7:22:47 PM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #1: jeedom.ophiuchus.fr,
[4/7/2020] [7:22:48 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot renew --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-1" --preferred-challenges "dns,http" --disable-hook-validation ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
No certificate found with name npm-1 (expected /etc/letsencrypt/renewal/npm-1.conf).,
,
[4/7/2020] [7:23:19 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:23:23 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:23:53 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:24:08 PM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #1: jeedom.ophiuchus.fr,
[4/7/2020] [7:24:09 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot renew --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-1" --preferred-challenges "dns,http" --disable-hook-validation ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
No certificate found with name npm-1 (expected /etc/letsencrypt/renewal/npm-1.conf).,
,
[4/7/2020] [7:24:14 PM] [SSL      ] › ℹ  info      Revoking Let'sEncrypt certificates for Cert #1: jeedom.ophiuchus.fr,
[4/7/2020] [7:24:22 PM] [SSL      ] › ℹ  info      Revoking Let'sEncrypt certificates for Cert #2: unifi.ophiuchus.fr,
[4/7/2020] [7:25:17 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:25:51 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:25:51 PM] [SSL      ] › ℹ  info      Requesting Let'sEncrypt certificates for Cert #3: unifi.ophiuchus.fr,
[4/7/2020] [7:25:56 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:25:56 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-3" --agree-tos --email<EMAIL_ADDRESS>--preferred-challenges "dns,http" --webroot --domains "unifi.ophiuchus.fr" ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
Plugins selected: Authenticator webroot, Installer None,
Obtaining a new certificate,
Performing the following challenges:,
http-01 challenge for unifi.ophiuchus.fr,
Using the webroot path /data/letsencrypt-acme-challenge for all unmatched domains.,
Waiting for verification...,
Challenge failed for domain unifi.ophiuchus.fr,
http-01 challenge for unifi.ophiuchus.fr,
Cleaning up challenges,
Some challenges have failed.,
,
[4/7/2020] [7:26:25 PM] [Access   ] › ℹ  info      Building Access file #1 for: ophiuchus,
[4/7/2020] [7:26:25 PM] [Access   ] › ℹ  info      Adding: rodolphe,
[4/7/2020] [7:26:26 PM] [Access   ] › ✔  success   Built Access file #1 for: ophiuchus,
[4/7/2020] [7:33:08 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:33:08 PM] [SSL      ] › ℹ  info      Requesting Let'sEncrypt certificates for Cert #4: jeedom.ophiuchus.fr,
[4/7/2020] [7:33:13 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:33:13 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-4" --agree-tos --email<EMAIL_ADDRESS>--preferred-challenges "dns,http" --webroot --domains "jeedom.ophiuchus.fr" ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
Plugins selected: Authenticator webroot, Installer None,
Obtaining a new certificate,
Performing the following challenges:,
http-01 challenge for jeedom.ophiuchus.fr,
Using the webroot path /data/letsencrypt-acme-challenge for all unmatched domains.,
Waiting for verification...,
Challenge failed for domain jeedom.ophiuchus.fr,
http-01 challenge for jeedom.ophiuchus.fr,
Cleaning up challenges,
Some challenges have failed.,
,
[4/7/2020] [7:33:15 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...,
[4/7/2020] [7:33:17 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:33:17 PM] [SSL      ] › ℹ  info      Renew Complete,
[4/7/2020] [7:33:17 PM] [SSL      ] › ✖  error     Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-3/fullchain.pem -subject -noout,
Can't open /etc/letsencrypt/live/npm-3/fullchain.pem for reading, No such file or directory,
140650706484552:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/letsencrypt/live/npm-3/fullchain.pem','r'),
140650706484552:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:,
unable to load certificate,
),
[4/7/2020] [7:33:17 PM] [SSL      ] › ✖  error     Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-4/fullchain.pem -subject -noout,
Can't open /etc/letsencrypt/live/npm-4/fullchain.pem for reading, No such file or directory,
140360297569608:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/letsencrypt/live/npm-4/fullchain.pem','r'),
140360297569608:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:,
unable to load certificate,
),
[4/7/2020] [7:33:41 PM] [Nginx    ] › ℹ  info      Reloading Nginx,

Logs letsencrypt
[root@docker-70a1dec97cfe:/var/log/letsencrypt]# vi letsencrypt.log
2020-04-07 20:01:27,880:DEBUG:certbot._internal.main:certbot version: 1.0.0
2020-04-07 20:01:27,881:DEBUG:certbot._internal.main:Arguments: ['--non-interactive', '--config', '/etc/letsencrypt.ini', '--cert-name', 'npm-3', '--preferred-challenges', 'dns,http', '--disable-hook
2020-04-07 20:01:27,881:DEBUG:certbot._internal.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#manual,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2020-04-07 20:01:27,919:DEBUG:certbot._internal.log:Root logging level set at 20
2020-04-07 20:01:27,919:INFO:certbot._internal.log:Saving debug log to /var/log/letsencrypt/letsencrypt.log
2020-04-07 20:01:27,920:DEBUG:certbot._internal.log:Exiting abnormally:
Traceback (most recent call last):
  File "/usr/bin/certbot", line 11, in <module>
    load_entry_point('certbot==1.0.0', 'console_scripts', 'certbot')()
  File "/usr/lib/python3.8/site-packages/certbot/main.py", line 14, in main
    return internal_main.main(cli_args)
  File "/usr/lib/python3.8/site-packages/certbot/_internal/main.py", line 1350, in main
    return config.func(config, plugins)
  File "/usr/lib/python3.8/site-packages/certbot/_internal/main.py", line 1259, in renew
    renewal.handle_renewal_request(config)
  File "/usr/lib/python3.8/site-packages/certbot/_internal/renewal.py", line 391, in handle_renewal_request
    conf_files = [storage.renewal_file_for_certname(config, config.certname)]
  File "/usr/lib/python3.8/site-packages/certbot/_internal/storage.py", line 52, in renewal_file_for_certname
    raise errors.CertStorageError("No certificate found with name {0} (expected "
certbot.errors.CertStorageError: No certificate found with name npm-3 (expected /etc/letsencrypt/renewal/npm-3.conf).

I seem to have a very similar issue...
 You should use `allowGraph` instead. `allowEager` method will be removed in 3.0
`QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0
QueryBuilder#omit is deprecated. This method will be removed in version 3.0
[4/16/2020] [3:18:46 PM] [SSL      ] › ✖  error     Error: Command failed: /usr/bin/certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
Challenge failed for domain cloud.domain.net
Challenge failed for domain www.domain.net
Attempting to renew cert (npm-3) from /etc/letsencrypt/renewal/npm-3.conf produced an unexpected error: Some challenges have failed.. Skipping.
All renewal attempts failed. The following certs could not be renewed:
  /etc/letsencrypt/live/npm-3/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)

    at ChildProcess.exithandler (child_process.js:295:12)
    at ChildProcess.emit (events.js:210:5)
    at maybeClose (internal/child_process.js:1028:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)

container-start.sh
docker create \
  --name $name \
  -p 80:80 \
  -p 443:443 \
  -p 81:81 \
  -v /mnt/z.raid1/software.docker/A-dockerStartFiles/nginx-proxy/config.json:/app/config/production.json \
  -v /mnt/z.raid1/software.docker/nginx_proxy/data:/data \
  -v /mnt/z.raid1/software.docker/nginx_proxy/letsencrypt:/etc/letsencrypt \
  -e TZ=Europe/Helsinki \
  -e FORCE_COLOR=1 \
  --restart unless-stopped \
  --log-opt max-size=1m \
    jc21/nginx-proxy-manager:latest

docker image inspect jc21/nginx-proxy-manager:latest
[
    {
        "Id": "sha256:ed18ab76b851f62ab3672b5a35b19f43671a4380c4bb8d95b4209a08c6de36e5",
        "RepoTags": [
            "jc21/nginx-proxy-manager:latest"
        ],
        "RepoDigests": [
            "jc21/nginx-proxy-manager@sha256:940681f8439604c9a5a2b88d2036adbcdd23675908bf915806a3289fa8c6b226"
        ],
        "Parent": "",
        "Comment": "buildkit.dockerfile.v0",
        "Created": "2020-04-15T06:02:31.803807951Z",

logs in container:
(/var/log/letsencrypt/letsencrypt.log)
2020-04-17 08:21:32,578:INFO:certbot._internal.renewal:Cert not yet due for renewal
2020-04-17 08:21:32,580:DEBUG:certbot._internal.plugins.selection:Requested authenticator webroot and installer None
2020-04-17 08:21:32,583:DEBUG:certbot._internal.cli:Var pref_challs=dns,http (set by user).
2020-04-17 08:21:32,583:DEBUG:certbot._internal.cli:Var authenticator=webroot (set by user).
2020-04-17 08:21:32,584:DEBUG:certbot._internal.cli:Var webroot_path=/data/letsencrypt-acme-challenge (set by user).
2020-04-17 08:21:32,584:DEBUG:certbot._internal.cli:Var webroot_map={'webroot_path'} (set by user).
2020-04-17 08:21:32,584:DEBUG:certbot._internal.cli:Var webroot_path=/data/letsencrypt-acme-challenge (set by user).
2020-04-17 08:21:32,609:INFO:certbot._internal.renewal:Cert not yet due for renewal
2020-04-17 08:21:32,612:DEBUG:certbot._internal.plugins.selection:Requested authenticator webroot and installer None
2020-04-17 08:21:32,612:ERROR:certbot._internal.renewal:All renewal attempts failed. The following certs could not be renewed:
2020-04-17 08:21:32,613:ERROR:certbot._internal.renewal:  /etc/letsencrypt/live/npm-3/fullchain.pem (failure)
2020-04-17 08:21:32,613:DEBUG:certbot._internal.log:Exiting abnormally:
Traceback (most recent call last):
  File "/usr/bin/certbot", line 11, in <module>
    load_entry_point('certbot==1.0.0', 'console_scripts', 'certbot')()
  File "/usr/lib/python3.8/site-packages/certbot/main.py", line 14, in main
    return internal_main.main(cli_args)
  File "/usr/lib/python3.8/site-packages/certbot/_internal/main.py", line 1350, in main
    return config.func(config, plugins)
  File "/usr/lib/python3.8/site-packages/certbot/_internal/main.py", line 1259, in renew
    renewal.handle_renewal_request(config)
  File "/usr/lib/python3.8/site-packages/certbot/_internal/renewal.py", line 473, in handle_renewal_request
    raise errors.Error("{0} renew failure(s), {1} parse failure(s)".format(
certbot.errors.Error: 1 renew failure(s), 0 parse failure(s)

Let me know if there are any other information missing from above.

Not sure if anyone else has run into this.  I'm running the proxy container on VM inside corporate network and when I try and create the proxy in Nginx Proxy Manager, I too get the 'Internal Error' and in the log I can see that lets encrypt can't validate my domain.  Under SSL Certificates there is an entry but its immediately expired.  In the DNS Manager we use I have my domain mapped to the host IP of the machine where I'm running the proxy container in the Forward Lookup Zone.  Am I correct in thinking letsencrypt just can't reach my domain to validate that 'I own it'?
2020-05-04 17:10:39,713:DEBUG:urllib3.connectionpool:https://acme-v02.api.letsencrypt.org:443 "POST /acme/authz-v3/4362994539 HTTP/1.1" 200 625
2020-05-04 17:10:39,714:DEBUG:acme.client:Received response:
HTTP 200
Server: nginx
Date: Mon, 04 May 2020 17:11:21 GMT
Content-Type: application/json
Content-Length: 625
Connection: keep-alive
Boulder-Requester: 85028888
Cache-Control: public, max-age=0, no-cache
Link: https://acme-v02.api.letsencrypt.org/directory;rel="index"
Replay-Nonce: 0002Z8epRT7DdbUiCHQ6gsOQuvNlarPnL7KRDGYsEg7qoCM
X-Frame-Options: DENY
Strict-Transport-Security: max-age=604800
{
"identifier": {
"type": "dns",
"value": ""
},
"status": "invalid",
"expires": "2020-05-11T17:11:19Z",
"challenges": [
{
"type": "http-01",
"status": "invalid",
"error": {
"type": "urn:ietf:params:acme:error:dns",
"detail": "DNS problem: NXDOMAIN looking up A for  - check that a DNS record exists for this domain",
"status": 400
},
"url": "https://acme-v02.api.letsencrypt.org/acme/chall-v3/4362994539/zHEy1w",
"token": "PCdm1kOKDDqyzF4LX6-gAt0omNYuV0iwRNBtQ0NLR5Q"
}
]
}

@jmford775 Yes, you are correct. Letsencrypt requires you to verify ownership of a domain before issuing a certificate. It does this by first looking for a valid domain response, then reaching out to the domain to verify the server is sitting there. For this to happen you will need to point the domain to the IP you plan on using and open port 80 on that IP and have it point to your proxy container.
From the sound of your post you plan on using this internally. Note that setting up internal DNS to point to your machine will not be sufficient. There must be a valid public IP address with matching DNS pointed to your container. Likewise, the certificate will be valid ONLY for that external address and will not work internally (unless you utilize the same naming scheme).
For example:
External Public IP: 1.1.1.x
Internal Public IP: 10.0.10.x
Public DNS: public.com
Internal DNS: internal.com
Your container sits on 10.0.10.y and it requests a certificate for container.internal.com. Letsencrypt does not know where your container is, because it is using an internal DNS schema. If you request container.public.com then letsencrypt will be able to see that you pointed container.public.com to your external IP (1.1.1.x) and will reach out to that IP (Port 80 [forwarded on firewall]) to verify that the container is actually sitting there.

@s4b3rt0oth I have the same problem as @jmford775 but mine is to connect from the outside. My port 80 and 443 are open and pointing to NPM server but it still shows internal error. The exact same thing happened to me where once trying to add SSL cert, it shows "Internal Error" and will show the cert expired same date and time when I tried adding.

Same here. Running the github-develop build.
Sent from my iPhone

On May 5, 2020, at 2:38 PM, AnonJervis<EMAIL_ADDRESS>wrote:

@s4b3rt0oth I have the same problem as @jmford775 but mine is to connect from the outside. My port 80 and 443 are open and pointing to NPM server but it still shows internal error. The exact same thing happened to me where once trying to add SSL cert, it shows "Internal Error" and will show the cert expired same date and time when I tried adding.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@s4b3rt0oth Yeah I realized it was going to be a no-go being inside our corporate network and thanks for the reply.  I decided since we are already behind super strict firewalls that I would just run a no-auth registry and joxit ui

I get the same error.
My setup, debian container on proxmox.
Installed as shown on https://nginxproxymanager.com/setup/ exept i used database image: jc21/mariadb-aria:10.4.12
when i try to setup a simple proxy i get the internal error.
logs show:
Docker App:
[7/28/2020] [8:41:31 AM] [Nginx    ] › ℹ  info      Reloading Nginx [7/28/2020] [8:41:31 AM] [SSL      ] › ℹ  info      Requesting Let'sEncrypt certificates for Cert #2: home.sieliakus.nl [7/28/2020] [8:41:38 AM] [Nginx    ] › ℹ  info      Reloading Nginx [7/28/2020] [8:41:38 AM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-2" --agree-tos --email<EMAIL_ADDRESS>--preferred-challenges "dns,http" --webroot --domains "home.sieliakus.nl"  Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator webroot, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for home.sieliakus.nl Using the webroot path /data/letsencrypt-acme-challenge for all unmatched domains. Waiting for verification... Challenge failed for domain home.sieliakus.nl http-01 challenge for home.sieliakus.nl Cleaning up challenges Some challenges have failed.
Error log in data folder:
2020/07/28 07:53:18 [error] 243#243: *1 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: nginxproxymanager, request: "GET /api/ HTTP/1.1", upstream: "http://<IP_ADDRESS>:3000/", host: "<IP_ADDRESS>:81" 2020/07/28 07:53:21 [error] 243#243: *3 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: nginxproxymanager, request: "GET /api/ HTTP/1.1", upstream: "http://<IP_ADDRESS>:3000/", host: "<IP_ADDRESS>:81", referrer: "http://<IP_ADDRESS>:81/nginx/proxy" 2020/07/28 07:53:24 [error] 243#243: *5 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: nginxproxymanager, request: "GET /api/ HTTP/1.1", upstream: "http://<IP_ADDRESS>:3000/", host: "<IP_ADDRESS>:81"
I have openend port 80 an 443 on my router and forwarded tot the NPM.
Anything i missed??

Same thing here. Using the Nginx Proxy Manager Add On for Home Assistant

are you change expose port of npm app difference 80 ?

Just encountered this issue, incredibly frustrating.

Got the same issue... I have 4 proxy-hosts, only one is unable to get a new certificate. Finally ended up in NGINX logs where I found that NGINX is not able to fire up the webserver for verification (cannot bind IP-address to port 80).
After comparing this NPM container with another one, I found that I changed the Docker-network from 172.... to <IP_ADDRESS>. It's possible that I changed this after deploying the first proxy-host. I guess the old IP or subnet is still somewhere in NGINX configfiles - does somebody have an idea where? I'm not really used with NGINX...

Strangely, I had certs reporting as expired, but the browser was reporting up-to-date certificates. One of my certs was disconnected for a while, so of course it's cert didn't renew. Connecting and trying to renew showed me this internal error.
I restarted my docker containers, then changed the 'default site' option in settings to 'custom page'. It was previously set to '404 page'. I was thinking that the 404 was returned before the challenge file, interfering with renewals.
When I looked at the certificate page, all my certs were up-to-date. So I'm not sure if it was the container reboot, or if it was changing the 'default site' option that solved my problem. Give it a try?

Same issue here, i change the Default Site from Congratulations Page to Redirect and i give internal error on cert renew. i think npm redirect the request before the certbot find the /.well-known/-acme-chellenge/
i change it back for congrat page but i have a same erreor...

Strangely, I had certs reporting as expired, but the browser was reporting up-to-date certificates. One of my certs was disconnected for a while, so of course it's cert didn't renew. Connecting and trying to renew showed me this internal error.
I restarted my docker containers, then changed the 'default site' option in settings to 'custom page'. It was previously set to '404 page'. I was thinking that the 404 was returned before the challenge file, interfering with renewals.
When I looked at the certificate page, all my certs were up-to-date. So I'm not sure if it was the container reboot, or if it was changing the 'default site' option that solved my problem. Give it a try?

I had this problem at one point. I use CloudFlare DNS, and I was able to resolve by disabling CloudFlare's proxy.
There was not much helpful error information when the certificate generation failed, but I could confirm I had the issue anytime proxy was enabled, issue resolved once it was disabled.


Add new SharedTree format leveraging optional-field v2

Description
Exposes the option to use the new optional-field format on SharedTree.
This does not change the default format.

Note: I had to bump the timeout for the "all scenarios" combinatorial test because adding this additional codec means tree takes longer to initialize (due to compiling more schemas for the encoded format).
We could recover the time spent to construct a tree by doing the 'lazy codec creation' optimization that's mentioned in compatibility.md. I don't think this is much of a big deal in practice for scenarios we're targeting today (that test constructs many trees), and we can always optimize for it later if we want to.

Note for posterity: this PR should have updated the implementation of MessageCodec and EditManagerCodec to actually write version: 2 into the persisted data as well. That's handled in #20636, but the option shouldn't have been exposed on the public API before that was sorted out.


Check the right set of statuses based on the branch

So now the set of the blocking statuses will be determined based on the branch against which the PR is sent.
Based on the sonversation with @sdodson, master tests current devel (3.6) and last release (3.5). Other branches only test their respective versions. So when testing against master 3.6 and 3.5 blocking statuses shall be checked.
@stevekuznetsov PTAL

@stevekuznetsov PTAL

@stevekuznetsov updated

@stevekuznetsov nit addressed

@jhadvig OK! Let me know when and I can show you how to change the Rosie-bot config

This is causing
########## STARTING STAGE: CHECK OTHER JOB STATUSES ##########
+ [[ -s /var/lib/jenkins/jobs/test_pull_request_openshift_ansible_extended_conformance_install_with_status_check/workspace/activate ]]
+ source /var/lib/jenkins/jobs/test_pull_request_openshift_ansible_extended_conformance_install_with_status_check/workspace/activate
++ export VIRTUAL_ENV=/var/lib/jenkins/origin-ci-tool/aa51983c42af91fd00b2a39c162b0b9017148462
++ VIRTUAL_ENV=/var/lib/jenkins/origin-ci-tool/aa51983c42af91fd00b2a39c162b0b9017148462
++ export PATH=/var/lib/jenkins/origin-ci-tool/aa51983c42af91fd00b2a39c162b0b9017148462/bin:/sbin:/usr/sbin:/bin:/usr/bin
++ PATH=/var/lib/jenkins/origin-ci-tool/aa51983c42af91fd00b2a39c162b0b9017148462/bin:/sbin:/usr/sbin:/bin:/usr/bin
++ unset PYTHON_HOME
++ export OCT_CONFIG_HOME=/var/lib/jenkins/jobs/test_pull_request_openshift_ansible_extended_conformance_install_with_status_check/workspace/.config
++ OCT_CONFIG_HOME=/var/lib/jenkins/jobs/test_pull_request_openshift_ansible_extended_conformance_install_with_status_check/workspace/.config
+ git checkout sjb
fatal: Not a git repository (or any of the parent directories): .git
++ export status=FAILURE
++ status=FAILURE
+ set +o xtrace


chore(docs): Fix real mouse wheel docs

:tada: This PR is included in version 1.8.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add video recording to NixOS VM tests

Sometimes, it's a bit difficult to debug VM tests post-mortem, especially when GUIs are involved. So this adds a new nixos-test QEMU UI module to qemu_test, which writes raw video frame deltas to an intermediate file (the reasons for this are detailed in the commit message of db8e70f8636440f2c685461e20fc981170301981), so that it can be encoded to a video file at a later stage.
Encoding of the video is done using a helper tool called nixos-test-encode-video, which encodes the intermediate format into a more commonly recognized one determined by the filename given (for example nixos-test-encode-video foo.video bar.webm will encode the intermediate foo.video into bar.webm using a WebM container with VP9).
NixOS VM test runners now have another attribute called videos, which will gather all the build products from the normal test runner, encode the videos to WebM and add them to the build products. This could see a bit of improvement in Hydra so that those videos are directly displayed in the browser instead of a download.
I've also added usage of the .video attribute in release.nix, so that this is done by default but doesn't increase test run time when building the tests directly without going through release.nix.
A Hydra jobset of this branch is available at https://headcounter.org/hydra/jobset/aszlig/nixos-tests.
Partial example GIF from the enlightenment test:

Converted back to draft since there are still a few issues to solve:

[ ] Add version field for intermediate format
[ ] Test whether endian conversion is done correctly
[ ] Move encoder and QEMU driver into separate repository
[ ] Improve frame timing/pixel format options in encoder

Failure on x86_64-darwin (full log)
Attempted: qemu_test
Partial log (click to expand)
cannot build derivation '/nix/store/wn4vwaa25msqww4l6slh96v7rnhvc2qr-graphite2-1.3.6.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/7zswqah6rx30dkcm6rvryzkj02hx39wh-snappy-1.1.7.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/nk9fhqi8gpdj4k3sshzhmax5k860y83i-soxr-0.1.3.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/hkihdgf951715cdmk7p33i4jx9aw4rkz-x265-2.7.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/gmd19xlkyqm5y3j5lxa30gk8bizqgn16-harfbuzz-1.7.6.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/4v0qxcxrh2ridnaljpijx5v0nzpxfd1y-libass-0.14.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/j8845bkb9lwycvvdxqm2xyvx70nc8lcw-ffmpeg-3.4.2.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/y44na8h4sq0nynxz52aynsk2sh88z1nz-nixos-test-encode-video.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/q1c9kkry2cx33sw0jh762fvqjdq9n5an-qemu-for-nixos-tests-2.12.0.drv': 2 dependencies couldn't be built
error: build of '/nix/store/q1c9kkry2cx33sw0jh762fvqjdq9n5an-qemu-for-nixos-tests-2.12.0.drv' failed

Related: https://github.com/NixOS/nixpkgs/pull/33299

Failure on aarch64-linux (full log)
Attempted: qemu_test
Partial log (click to expand)
36 makeWrapper /nix/store/pzdxl08js43135hc4c28id1a6fna4sqr-hook/nix-support/setup-hook
99 _callImplicitHook /nix/store/7b2p80jk29w7jz2d907nsbpqgxr1zk98-stdenv-linux/setup
117 _eval /nix/store/7b2p80jk29w7jz2d907nsbpqgxr1zk98-stdenv-linux/setup
44 runHook /nix/store/7b2p80jk29w7jz2d907nsbpqgxr1zk98-stdenv-linux/setup
1088 installPhase /nix/store/7b2p80jk29w7jz2d907nsbpqgxr1zk98-stdenv-linux/setup
1283 genericBuild /nix/store/7b2p80jk29w7jz2d907nsbpqgxr1zk98-stdenv-linux/setup
2 main /nix/store/9krlzvny65gdc8s7kpb6lkx8cd02c25b-default-builder.sh

builder for '/nix/store/9kjkkxzdj3n3imw1k1mpg73axzrip86z-qemu-for-nixos-tests-2.12.0.drv' failed with exit code 1
error: build of '/nix/store/9kjkkxzdj3n3imw1k1mpg73axzrip86z-qemu-for-nixos-tests-2.12.0.drv' failed

@dotlambda: This is basically a follow-up to that PR and what I suggested back then. Having a custom UI module in QEMU also has the advantage that we can watch regions for changes, which is particularly useful for making tests with keyboard/mouse input more reliable. Right now we handle input blindly based for example on the assumption that a particular application has started, but we don't actually know whether an input field has focus or even the application is accepting input (we only check whether there is an X window, which could be empty) at all. With access to frame deltas we can simply watch for a certain region to change, press a key, wait for another change (and if it doesn't change, repeat the keypress), press the next key and so on.

There is a however still an issue with the videos, because not all frames are written to the intermediate file. The amount of frames received from QEMU is correct but it seems that the UI module doesn't seem to get all the frame updates from the console. I'm adding a WIP label until I've resolved that.

Needed to fixup the first commit because this would break QEMU on non-x86_64-linux systems.

@grahamcofborg build qemu_test

Failure on x86_64-darwin (full log)
Attempted: qemu_test
Partial log (click to expand)
CC      libavcodec/aacenctab.o
HOSTCC  libavcodec/aacps_fixed_tablegen.o
/nix/store/i9g6883w05pyj9aa4sl8hn945qyy6j53-bash-4.4-p19/bin/bash: gcc: command not found
make: *** [ffbuild/common.mak:152: libavcodec/aacps_fixed_tablegen.o] Error 127
make: *** Waiting for unfinished jobs....
2 warnings generated.
builder for '/nix/store/xsvcfml2m4imhagn2pcwphr2fhh0zkq2-ffmpeg-3.4.2.drv' failed with exit code 2
cannot build derivation '/nix/store/c1vahagnxmg7kzy28l214j3298x92cx4-nixos-test-encode-video.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/s9p0rl04rgw215hwfvn4sdmz7gjvinky-qemu-for-nixos-tests-2.12.0.drv': 1 dependencies couldn't be built
error: build of '/nix/store/s9p0rl04rgw215hwfvn4sdmz7gjvinky-qemu-for-nixos-tests-2.12.0.drv' failed

Success on x86_64-linux (full log)
Attempted: qemu_test
Partial log (click to expand)
patching script interpreter paths in /nix/store/xcv4a8d27msnn2wialrp26wf8rcr2dnk-qemu-for-nixos-tests-2.12.0
checking for references to /build in /nix/store/xcv4a8d27msnn2wialrp26wf8rcr2dnk-qemu-for-nixos-tests-2.12.0...
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
strip is /nix/store/92d2ifxcni4n3zx9s8wnkcjlvnx5ajlc-binutils-2.30/bin/strip
/nix/store/xcv4a8d27msnn2wialrp26wf8rcr2dnk-qemu-for-nixos-tests-2.12.0

Success on aarch64-linux (full log)
Attempted: qemu_test
Partial log (click to expand)
patching script interpreter paths in /nix/store/wbfdcr44a92wzb0nd0q94nnr7mxim79p-qemu-for-nixos-tests-2.12.0
checking for references to /build in /nix/store/wbfdcr44a92wzb0nd0q94nnr7mxim79p-qemu-for-nixos-tests-2.12.0...
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
strip is /nix/store/8yfik687kfccisxnad42j19lfb7ij9b4-binutils-2.30/bin/strip
/nix/store/wbfdcr44a92wzb0nd0q94nnr7mxim79p-qemu-for-nixos-tests-2.12.0

@GrahamcOfBorg build qemu_test

Success on x86_64-linux (full log)
Attempted: qemu_test
Partial log (click to expand)
patching script interpreter paths in /nix/store/2rkz845i1j1a8p9wzc5ydyvw56c4sl00-qemu-for-nixos-tests-2.12.0
checking for references to /build in /nix/store/2rkz845i1j1a8p9wzc5ydyvw56c4sl00-qemu-for-nixos-tests-2.12.0...
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
strip is /nix/store/92d2ifxcni4n3zx9s8wnkcjlvnx5ajlc-binutils-2.30/bin/strip
/nix/store/2rkz845i1j1a8p9wzc5ydyvw56c4sl00-qemu-for-nixos-tests-2.12.0

Failure on x86_64-darwin (full log)
Attempted: qemu_test
Partial log (click to expand)
CC      libavcodec/aacenc_tns.o
CC      libavcodec/aacenctab.o
HOSTCC  libavcodec/aacps_fixed_tablegen.o
/nix/store/i9g6883w05pyj9aa4sl8hn945qyy6j53-bash-4.4-p19/bin/bash: gcc: command not found
make: *** [ffbuild/common.mak:152: libavcodec/aacps_fixed_tablegen.o] Error 127
make: *** Waiting for unfinished jobs....
builder for '/nix/store/xsvcfml2m4imhagn2pcwphr2fhh0zkq2-ffmpeg-3.4.2.drv' failed with exit code 2
cannot build derivation '/nix/store/y8kp09p11rzs70z7yi09w14ycxcnh3x1-nixos-test-encode-video.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/wldfgfaiydxq8mskh8ac0j7kimpxf2wq-qemu-for-nixos-tests-2.12.0.drv': 1 dependencies couldn't be built
error: build of '/nix/store/wldfgfaiydxq8mskh8ac0j7kimpxf2wq-qemu-for-nixos-tests-2.12.0.drv' failed

Success on aarch64-linux (full log)
Attempted: qemu_test
Partial log (click to expand)
patching script interpreter paths in /nix/store/lmr1pg50ls8h80xfqvlnngpj4jir9b1n-qemu-for-nixos-tests-2.12.0
checking for references to /build in /nix/store/lmr1pg50ls8h80xfqvlnngpj4jir9b1n-qemu-for-nixos-tests-2.12.0...
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
strip is /nix/store/8yfik687kfccisxnad42j19lfb7ij9b4-binutils-2.30/bin/strip
/nix/store/lmr1pg50ls8h80xfqvlnngpj4jir9b1n-qemu-for-nixos-tests-2.12.0

While this is cool, it significantly increases the complexity of our testing infrastructure, in particular adding a custom version of QEMU that might be a PITA to maintain.
How large are the video files generated by this for a NixOS release? Our storage costs are already pretty high...

@edolstra: The intermediate video files are up to 2 MB (they only contain compressed frame deltas, although lossless) and the encoded videos in WebM format are around 2-5 MB. If that's too much we could alternatively just not encode them and only make the intermediate forma available so that videos can be encoded on a per-case basis.

@edolstra: As for the maintenance burden: The UI module is written in a way so that it is minimally invasive and the patch that integrates it into QEMU is also not very complicated.

@edolstra: Can you say anything on reverting 13dcb3523309c318e8dce59fae168ea39f98065c again? Because without that encoding videos won't be very helpful.

@aszlig Well, the motivation for 13dcb35 hasn't changed. Without it we can't restart failed builds, which happens fairly often unfortunately.

Any updates on this pull request, please?

@mmahut: For this we need to have a way to put failed builds to a content-addressable location in Hydra, because otherwise it wouldn't be of much use other than watching videos of builds that succeeded anyway and thus don't need to be debugged.

still important to me

Rebased against current master with the Python test driver.
I'll move the encoder and QEMU video driver to a different repository soon (hopefully next week), but since we now (well, since quite a while already, but this PR is quite old) get to the store path contents of even failed derivation, having videos becomes more feasible.

As much as I appreciate the feature by itself, why can't we just run qemu with vnc enabled, and use something to record from there?

I already went this route in the past (even SPICE), see the first commit message.

As much as I appreciate the feature by itself, why can't we just run qemu with vnc enabled, and use something to record from there?

I already went this route in the past (even SPICE), see the first commit message.

Thanks for the pointer - I now did read the commit message ;-)
Did you try approaching upstream qemu with the problems you're facing? I'm not sure if we do ourselves much of a favor shipping our own custom fork of qemu, and tooling to produce a somewhat ffmpeg-specific intermediate format etc. We certainly can't be the only ones facing this. I'd rather see this somewhere inside or alongside qemu, or spice being fixed to not drop frames (if the underlying architecture allows this).

Rebased against current master.

Please approach upstream to get either this or another reliable way of video recording merged. I don't think this is suitable to ship in nixpkgs only.

I'd like to avoid putting such a module upstream since currently it's too Nix-specific and I also have plans for using this same module to add UI test functionality (eg. selecting/matching regions for change or constraining OCR). Furthermore, upstream already rejected a similar implementation (although that one used ffmpeg, while ours does not).

Addendum: Since QEMU 8.0 there is a new D-Bus display, which as far as I can see calls a D-Bus listener for every frame update. This is a lot more close to what we want, but it seems to always write the full frame image even if only a subset has changed. It's not a show-stopper though since we can easily work around this limitation if we even need to.
I'll experiment with that a bit to see whether it's a viable option or whether it has similar drawbacks such as SPICE/VNC.

@Aleksanaa: What's the reason for the close?

Sorry, was just sorting out things being inactive for a long time.

I think it's fair to close inactive pull request if the author doesn't work on it because it still requires reviewers to revisit the pull request from time to time.

@Aleksanaa

Sorry, was just sorting out things being inactive for a long time.

No need to be sorry. I'm totally fine with this, I was just curious to know why.


Opt-in functionality

I'm finding difficult to restrict the PM edit/drag/remove functionality to specific layers in my map. In other words, difficulty to exclude other layers (in particular, those created by third-party tools) where the PM functionality is not required at all. The pmIgnore mechanism is not really useful in these cases as it would minimally require one to traverse those layers and do something only for purposes of disabling PM functionality for them.
The kind feature request here is to provide an initialization option to indicate the desire for the PM functionality in an opt-in fashion. More concretely, something like the following:

An new option optIn (or some other name for the intended effect) for the addControls method, of course with default value false for backwards compatibility.

When adding a particular layer in my application, be able to indicate pmEnable (with basically the opposite meaning of pmIgnore). Example:
L.marker([51.50915, -0.096112], { pmEnable: true }).addTo(map);

Imho, this would really make your wonderful tool even more appealing!  Thanks!

I like it! Marked as a feature request. Please upvote the above post to help me prioritize feature requests.

@carueda would be awesome if you could take a look at https://github.com/geoman-io/leaflet-geoman/pull/504 where I'm adding the optIn option.
It basically works like this:
If you call the this after importing leaflet-geoman:
L.PM.initialize({ optIn: false });

Only layers that have specifically set pmIgnore: false will be handled by leaflet-geoman:
L.marker([51.50915, -0.096112], { pmIgnore: false }).addTo(map);

Does that make sense?

@codeofsumit Thanks much!  LGTM.  I don't have the cycles now to do proper verification but I trust it's all good. Thanks again.

released ✅


TypeError: No method matches given arguments for Person..ctor:

I am getting below error and not able to understand how to solve it,
i am trying to run below code as mentioned in pip documentation
from vedastro.calculators import SaturnInAries
from vedastro.objects import GeoLocation, Time, Person, Gender
import VedAstro.Library as VedAstro
Create a GeoLocation object for Tokyo, Japan
geolocation = GeoLocation(location="Tokyo", latitude=35.6895, longitude=139.6917).geolocation
Define the birth date, time, and time offset
date = "07/05/2010"
time = "06:42"
time_offset = "+09:00"
Create a Time object for the birth date, time, and time offset
time_ob = Time(date, time, time_offset, geolocation).time_object
Define the person's ID, user ID, notes, name, and gender
id = "1234"
user_id = "123"
notes = ""
name = "John Doe"
gender = Gender.Male
Create a Person object for John Doe with the provided details
john_doe = Person(id=id, user_id=user_id, name=name, gender=gender, birth_time=time_ob, notes=notes).person
do calculation to check if saturn is in aries at a given time
saturn_aries = VedAstro.HoroscopeCalculatorMethods.SaturnInAries(time_ob)
data if the astro event occured
occurrence = saturn_aries.Occuring
get the planets or houses related to this astro event
related_body = saturn_aries.RelatedBody
Print the results
print("Occurrence of Saturn in Aries:", occurrence)
print("Related celestial body:", related_body)
TypeError: No method matches given arguments for Person..ctor: (<class 'str'>, <class 'str'>, <class 'VedAstro.Library.Time'>, <class 'VedAstro.Library.Gender'>, <class 'str'>, <class 'str'>, <class 'NoneType'>)

Sorry for the late reply, i thought the issue was major so saved it for this week.....
now i see this simply the case of outdated code still in README file 😅
@rickspark4 check out the readme file now, it contains a working example
please report back if it works so we can close this issue

Hey @sengiv
New code is working now ,but the code you provided earlier is still throwing  same error,
on the other hand there are certain python files that you provided in repo also not working
Regards:
Rick Spark

if possible please list the demo files that is causing error, they probably contain outdated code.
...also feel free to experiment and update code files and make PR 🙏
the repo basically needs spring cleaning 🧹
the core astro library is guaranteed is fine atm, because the live API server is running on the same code base, and there's no errors.
So all errors you're experiencing is only due to "invalid or outdated syntax" via Python


Run Coin-Hive without puppeteer

Any idea how to run the coin-hive package with nodejs without using Puppeteer or ideas for developing monero miner for nodejs. Thanks

Why? If you want a real miner just take xmrig. Javascript isn't the best language when it comes to high-cpu tasks IMO.

@soyuka Ok, thanks for your response, appreciate it.


Person details screen (EXPOSUREAPP-7574)

This is the person details screen that aggregates the test, vaccination and recovery certificates.
Implemented so far is the highest priority QR code and the cwa-user card.
I've left the old VaccinationListFragment in place as it might still be useful for adding the vaccination cards.

Scan Vaccination certificate 1,2 (Blue colour does not mean immune, it means current)

Could you please check this with UX, I think in the latest mockup there isn't a "grey state", but IMHO there should be one.


Documentation for nltest command is missing

Expected behavior: Page has link to documentation for nltest command.
Observed behavior: Page does not have link to documentation for nltest command.
Fix needed: Add link to documentation for nltest command.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6d382ca0-6538-5e1d-3e83-e31c9ab6a911
Version Independent ID: 11eff296-6158-f89a-4941-8735529183e9
Content: Windows commands
Content Source: WindowsServerDocs/administration/windows-commands/windows-commands.md
Product: windows-server
Technology: windows-commands
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

ⓘ We're no longer updating this content regularly. Check the Microsoft Product Lifecycle for information about how this product, service, technology, or API is supported.
Nltest
Applies To: Windows Server 2003, Windows Server 2008, Windows Server 2003 R2, Windows Server 2008 R2, Windows Server 2012, Windows Server 2003 with SP1, Windows 8

https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc731935(v=ws.11)

This ticket is about https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/windows-commands and not https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc731935(v=ws.11) . You are correct that https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc731935(v=ws.11) is no longer being updated per the Microsoft Product Lifecycle. However, this ticket is not about https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc731935(v=ws.11) and https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc731935(v=ws.11) is not relevant to this ticket.
nltest is a command in Windows Server 2016 and possibly later versions. Documentation for Windows Server 2016 is still supported and is still being updated regularly per the Microsoft Product Lifecycle. Therefore, documentation for nltest should exist at https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/windows-commands but is missing. This needs to be fixed.

#assign:xelu86

Hey @rossmpersonal,
Thanks again for contacting Microsoft. We value your feedback.
A documentation change has been made adding the nltest command and will be live after the next business day. We are aware that some Windows Commands no longer appear in this list in favor of their PowerShell counterparts found in our Active Directory PowerShell Modules reference article.
We are encouraging our users to adopt PowerShell in place of Windows Commands for these commands and potentially more in the future. We will be closing this as resolved. Thank you and have a most pleasant day.
#please-close


Add IdentityT

Fixes #120
I likely haven't added every instance that IdentityT could have, and I'm not sure whether all of these instances are law-abiding. What I have below was based on MaybeT. I'm guessing this should also have instances for the Contravariant transformer classes as well?

Build is failing with this error. I think this was explained on Discourse somewhere.

$ TAG=$(wget -q -O - https://github.com/purescript/purescript/releases/latest --server-response --max-redirect 0 2>&1 | sed -n -e 's/.*Location:.*tag///p')
0.19s$ wget -O $HOME/purescript.tar.gz https://github.com/purescript/purescript/releases/download/$TAG/linux64.tar.gz
--2020-04-08 00:17:14--  https://github.com/purescript/purescript/releases/download//linux64.tar.gz
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2020-04-08 00:17:14 ERROR 404: Not Found.
The command "wget -O $HOME/purescript.tar.gz https://github.com/purescript/purescript/releases/download/$TAG/linux64.tar.gz" failed and exited with 8 during .

Ah yeah, here's the relevant thread: https://discourse.purescript.org/t/new-404-ci-failures-in-core-libraries/1225/8?u=hdgarrood
Would you like to try updating this repo? I think preferably the Travis fix would go into a separate PR.

Mind retriggering this build now that the CI script has been fixed?

Just restarting the build didn't seem to work, will try closing and reopening this. If that doesn't work, might need to rebase/merge master.

I think all of the instances you have explicit implementations for here, other than MonadTrans, can (and probably should?) be derive newtype instance.

:man_facepalming: You're right! Wow... I can't believe I did that. It's not the first time either...


Correct server-side-apply.md

Spelling mistake
DESCRIPTION: corrects spelling mistake

Hello, @wasimj You have to sign CLA to approve your PR.

/lgtm

Hi @wasimj,
Are you having issues signing the CLA?

signed

/check-cla

/lgtm
/approve


[OSDEV-944] Facility claims. Short-term new screen for claim documentation.

Fix https://opensupplyhub.atlassian.net/browse/OSDEV-944

Prepare basic FE for the file upload - DONE.
Connect to Redux state - DONE.
Change: LinkedIn Profile in current claims flow to Link to Facility LinkedIn Profile - DONE
Create model for storing uploaded attachments in PostgreSQL - DONE.
Add FE and BE validation (file size, file extensions, amount of files) - DONE.
Connect BE - DONE.
Connect S3 bucket - DONE.
Depict file links in Facility Claims dashboard per claim - DONE.
Add unit tests - DONE.
Remove related TODOs in this PR - DONE.
Update RELEASE_NOTES - DONE.

Improvements related to text fields during claim flow

Remove field for Preferred method of contact (preferred contact method can be deleted from database)  - TO BE DONE IN SEPARATE TICKET.
Adding the LinkedIn for the person’s contact - TO BE DONE IN SEPARATE TICKET.
Remove Any additional details? text field - TO BE DONE IN SEPARATE TICKET.

@VadimKovalenkoSNF S3 bucket will be connected in scope of this PR/task or as seperate PR/task?

@VadimKovalenkoSNF S3 bucket is already connected for this task - it works the same way as for the facility lists. Each Django model that expect FileField will store data to S3 implicitly. If you need info about local connection to the S3, contact me or @vladsha-dev


Make it easier to use Int types throughout

We may want to treat Int values as CGFloat types throughout material motion in order to ease use of simple constants, e.g. 0 or 1 without requiring need for explicit typing, e.g. CGFloat(0) or CGFloat(1).

This has been resolved. Reactive properties now default to CGFloat when using createProperty.


TX rejected

"I'm submitting a ... "

[ ] bug report
[ ] feature request
[X] support request
[ ] translation request

I have an Electrum XVG 2.4.1 wallet and I'm trying to send some coins to binance. I keep getting the error: TX rejected.
I've tried to change the fee manually and not, first to 0.1, then 1, then 2 XVG. I'm been able to make only 1 transaction of 100 XVG with a fee of 1 XVG. Does that mean that the fee is 1%?
I've also tried different servers, different amounts... nothing work. What should I do?

So the transaction fee for each transaction is always 0.1 XVG (by design)
See here: https://vergecurrency.com/faq/
And besides that, whats the current amount of XVG you have on your wallet.
I assume that you have 100 XVG, then you have to send 99.9XVG to binance as 0.1 XVG will be processed as transaction fees.

I have 1385 and trying to send 500 with 2 fee fails

if I try to use a 0.1 fee (sending 500) I get the message "this transaction requires a higher fee...)

I've successfully sent 500 XVG using a 2 XVG fee, but now even like this downs't work. Still getting "TX rejected"

now it's just stuck in the broadcast (I've waited a very long time)

Did these finally go through ?
I see the 100 and a couple 500's here:
https://verge-blockchain.info/address/DMNY4uyrVYxKQwcPY6NGkWqc7LVk8Lo5KQ
I did notice it said "synchronizing" in the bottom left of electrum client and not 'connected' .. probably had something to do with it ?

yes I've made 3 transactions, 100,500,500. With 1,2,2 fee. Now even that doesn't work anymore. Maybe the problem is the synchronization, but how to solve that?

Isn't this supposed to work?

Even with smaller amount and larger fee, it doesn't work

I'm not an Electrum guru unfortunately, hopefully someone else chimes in.
I think you just need a higher fee.  Just keep bumping it up by 1 until it goes through.  Unfortunately I can't speak to the formula in Electrum as to why:
https://www.reddit.com/r/vergecurrency/comments/82fi42/why_the_transaction_fee_of_electrum_wallet_is_so/
I mean I definitely would stop at like 5-10 if it's still being rejected
An alternate solution, although a lot different than a lightweight electrum wallet, is to use the QT wallet.  .01 fees all the time.

thank you for your help, I'll try rising the fee

Using 10 XVG as fee finally worked! I really would like to know why so much

was your balance made by alot of deposits? say your balance is 100 coins. it can be from depositing 1 coin 100 times, or depositing 50 coins twice. when you go to send, if it were from alot of small deposits, then the transaction is bigger because of all the inputs. the 2 50 transactions would be smaller because only 2 inputs. the more inputs, the higher the fee

Definitely! I've had many many small deposits. Thank you Justin for the explanation!


Player recording limit?/players not being recorded or saved correctly

Hey we added this mod to our server not too long ago but it looks as if some players are not being recorded on join or they are not having their replays saved correctly when we have "recording_enabled: true"
What we aim to have is automatic recording when a player joins and then have it saved once they leave
or have the entire server recorded into one file
At the moment we don't have clear documentation on how to do this or whether the mod is bugged and won't record more than 3 people at once
Please let me know how I can achieve this, thanks in advance.
here is our current config
#Config for Server Side Replay Recorder
##WARNING any comments in this file might get deleted

command_op_level: 4
replay_folder_name: "replay_recordings"
server_name: "My Server"
recordable_users: []
recording_enabled: true
assume_unloaded_chunks_dont_change: true
max_file_size:<PHONE_NUMBER>0
debug: false
use_username_for_recordings: true
invert_user_list: true
use_server_timestamps: true
render_distance_fog_fix: false
file_storage_url: "https://file.io/"

Should add that when a player joins it says recording started:"player" but when we check the status it is only 2 or three people being recorded

do you have the logfiles of the issue... we can't reproduce it as of now

Ahhh i can get them do you want them with the debug enabled or just logs?

do you have the logfiles of the issue... we can't reproduce it as of now

no the debug option only adds stuff to the replayfile, i just need the normal logs to see if for some reason it is stopping the recorders early
also do the folders for the non recorded players generate too?

At a glance it looks like the folders are being created
I will give you a log as soon as I am finished redacting ip's

2023-07-05-1.log
Heres a log file
We host the server using shockbyte so that could be why the mod is throwing not enough space error however we should have unlimited space (128GB per server)

Since this is a spatial issue, I'm gonna go ahead and close this now.
Best of luck to you of finding a storage solution!

Ahhh so its trying to allocate 10gb per player makes sense I didn't realise that's how it works
We plan to only keep a few hours of recordings sooo ill try a smaller size


Can’t comment

I’m able to view issues and PRs, lock them, assign milestones, etc... But I can’t send comments that I write. I get a double tap haptic feedback, but my comment isn’t posted.

Bug Report Dump (Auto-generated)

Version 1.23.0<PHONE_NUMBER>)
Device: iPhone 7 (iOS 11.4.1)
TestFlight: true

Is there an error toast that pops up? Or can you check the result of the networking call (three finger tap on the screen to open FLEX debugging)?

Right so the toast was hidden behind the keyboard. This is the Jason response:
  "query" : "mutation AddComment($subject_id: ID!, $body: String!) {\n  addComment(input: {subjectId: $subject_id, body: $body}) {\n    __typename\n    commentEdge {\n      __typename\n      node {\n        __typename\n        ...nodeFields\n        ...reactionFields\n        ...commentFields\n        ...updatableFields\n        ...deletableFields\n      }\n    }\n  }\n}fragment nodeFields on Node {\n  __typename\n  id\n}fragment reactionFields on Reactable {\n  __typename\n  viewerCanReact\n  reactionGroups {\n    __typename\n    viewerHasReacted\n    users(first: 3) {\n      __typename\n      nodes {\n        __typename\n        login\n      }\n      totalCount\n    }\n    content\n  }\n}fragment commentFields on Comment {\n  __typename\n  author {\n    __typename\n    login\n    avatarUrl\n  }\n  editor {\n    __typename\n    login\n  }\n  lastEditedAt\n  body\n  createdAt\n  viewerDidAuthor\n}fragment updatableFields on Updatable {\n  __typename\n  viewerCanUpdate\n}fragment deletableFields on Deletable {\n  __typename\n  viewerCanDelete\n}",
  "variables" : {
    "body" : "We can avoid the `repo update` step if we change install to `pod update SwiftGen`.\n\nSent with GitHawk",
    "subject_id" : "MDExOlB1bGxSZXF1ZXN0MjIyNjM4NjU1"
  }
} ```

Sent with GitHawk

So the issues maybe are: hide the keyboard on error, so users can see the error, and maybe show that specific error from github?
Sent with GitHawk

I think we have a ticket somewhere to show the toast above the keyboard.

I’m not sure if the is related but since the latest Testflight beta the notifications work but i cannot comment anymore.
With keyboard I the no toast and without keyboard it just says "something went wrong"

@mesqueeb “Something went wrong” is the generic error but I think there’s an issue for that as well
Sent with GitHawk


Fix Font Awesome font variant in the README

In the README, the font specified for Font Awesome uses Regular which results in icons not being rendered, whereas it should be Solid

Are you sure?  I use Regular in my config and it renders correctly.
spacebar -m config icon_font          "Hack Nerd Font Mono:Regular:30.0"
Installed nerd font with brew however

@nilsi this is related only to Font Awesome, as it doesnt have Regular

@nilsi this is related only to Font Awesome, as it doesnt have Regular

Huh. My Font Awesome 5 Free has a Regular listed, but I've never gotten the icons to work. Just changed my config to use Solid, and now I have icons! So…I wonder why it can't find the Regular variant. 🤷♀

Huh. My Font Awesome 5 Free has a Regular listed, but I've never gotten the icons to work. Just changed my config to use Solid, and now I have icons! So…I wonder why it can't find the Regular variant. 🤷♀

Oh weird, thanks for this @NickSeagull! I've been getting on just fine with the "Regular" style 🤷
But, based off the other comments here and trying out the "Solid" style myself, I've set the default style for the font in the bar manager and all the docs in ce0872c


for code

could you please release the whole code and data split files?

Hello @zhq-admin
Thanks for your interest in our work!
As I mentioned in README, we are now cleaning the code. If you need the preliminary version, please contact me via email<EMAIL_ADDRESS>


Address deprecation messages in bin/setup

Summary
We're getting some deprecation messages in bin/setup - address them before they become an actual issue
Details
The message in question is:
PG::Coder.new(hash) is deprecated. Please use keyword arguments instead!
We think that the gem for postgres has been updated, but whatever uses it has not yet been updated.   So we should look into what the implications are.
Criteria for completion

[ ] The message is addressed, and bin/setup still works properly!  Or we know what we have to lock down for awhile (report back.)

@cielf It looks like this may have been resolved in the new Rails patch release
I'm not seeing in when I run bin/setup anymore.

@DariBerrie Me either!  Thanks for looking into it!


Opening a notebook triggers a cell change

Version: 1.46.0-insider

Commit: cd41dd1f6065db76c77c6e2f659bb50e6f558dec
Date: 2020-05-29T05:45:24.735Z
Electron: 7.3.0
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.5.0

Steps to Reproduce:
1.Open a notebook
2.The cell change event gets fired.
User hasn't made any chanages, but opening a notebook triggers the change event to get fired. I think its unnecessary.

Does this issue occur when all extensions are disabled?: Yes/No
@rebornix

Good catch, the event should not be emitted.

the docs here could better describe when it actually gets called, I was expecting it to be called whenever a cells content changed, not when cellls get added/removed
https://github.com/microsoft/vscode-github-issue-notebooks/blob/e8ca5b4be951df8598d877d7603aa2804e0ef05d/src/vscode.d.ts#L1483


.shareReplay operator?

Should we have this operator? People could just ReplaySubject, but maybe this is nice to have.
Might require replay to be implemented if this were added though (which, iirc, just uses ReplaySubject under the hood anyway).
shareReplay in RxJS4

There's long discussions in https://github.com/ReactiveX/RxJS/issues/453, shorthanded summary's at https://github.com/ReactiveX/RxJS/issues/1110 also.

In short, for now shareReplay is not added and it's expected.

Oh, sorry, didn't find it in the search results.

@justinwoo Don't feel sorry, I also feel searching issue in github is bit hard sometime :) Glad questions solved.

.publishReplay().refCount()

We should have something similar ... but I'm not sure I'd want to name it shareWhatever at this point. share() has a slightly different and more ergonomic behavior than publish().refCount(). I'd like to add some sort of cache() operator that does what shareReplay was used for, but with perhaps more extensible arguments than a simple count to control things like expirey, etc. We started some discussion in #839 but it petered out.

I think we sort of agreed to cut the excess in share operators, and I like it if people understand what a ConnectableObservable is and that you need to call "connect()" and how refCount is sort of auto-connect. Because share() can sometimes be understood as a blurred concept of "make this cold become hot".


examples/animation: warnings on Firefox

WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow.
WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization.

This is shown on any examples.

It appears that this warning is just there to warn that WebGL is doing some non-trivial work and is not a problem worth fixing. Here is a fitting Stackoverflow answer to the same issue: https://stackoverflow.com/a/57734917

I see, thanks!


Model is not being trained

I am trying to train the 'Convolutional Neural Network' by following this tutorial
but while running the code it seems that no actual training is being done. You can see my code here.
Here is a log of code for first few epochs.
%run train.py
... loading data
float32
(35126L, 1L, 100L, 100L)
(35126L,)
  InputLayer            (None, 1, 100, 100)     produces   10000 outputs
  Conv2DLayer           (None, 1, 98, 98)       produces    9604 outputs
  MaxPool2DLayer        (None, 1, 49, 49)       produces    2401 outputs
  Conv2DLayer           (None, 1, 48, 48)       produces    2304 outputs
  MaxPool2DLayer        (None, 1, 24, 24)       produces     576 outputs
  DenseLayer            (None, 50)              produces      50 outputs
  DenseLayer            (None, 5)               produces       5 outputs

 Epoch  |  Train loss  |  Valid loss  |  Train / Val  |  Valid acc  |  Dur
--------|--------------|--------------|---------------|-------------|-------
     1  |         nan  |         nan  |          nan  |     73.50%  |  93.6s
     2  |         nan  |         nan  |          nan  |     73.50%  |  93.2s
     3  |         nan  |         nan  |          nan  |     73.50%  |  109.9s
     4  |         nan  |         nan  |          nan  |     73.50%  |  93.6s
     5  |         nan  |         nan  |          nan  |     73.50%  |  88.5s

I can't figure out what I am doing wrong

Is this a classification problem?  How does the network definition look like?

Yes it is a classification problem, my input is 100x100 gray-scale images which has to be classified in to 5 classes.  I have shared my code.
Here is a architecture of network.
	net = NeuralNet(
		layers=[
			('input', layers.InputLayer),
			('conv1', Conv2DLayer),
			('pool1', MaxPool2DLayer),
			('conv2', Conv2DLayer),
			('pool2', MaxPool2DLayer),
			('hidden4', layers.DenseLayer),
			('output', layers.DenseLayer),
			],
		input_shape=(None, 1, 100, 100),
		conv1_num_filters=1, conv1_filter_size=(3, 3), pool1_ds=(2, 2),
		conv2_num_filters=1, conv2_filter_size=(2, 2), pool2_ds=(2, 2),
		hidden4_num_units=50,
		output_num_units=5, output_nonlinearity=None,

		update_learning_rate=0.01,
		update_momentum=0.9,

		regression=False,
		max_epochs=5,
		verbose=1)

The dimensions and dtypes of X and Y which I pass to fit method are
net.fit(X, Y)

shape of X (35126L, 1L, 100L, 100L)
shape of Y (35126L,)
dtype of  X = float32
dtype of  Y = int32
and
theano.config.floatX = float32

@jayendra13 You just mentioned that this is a classification problem, right ? Then,
output_nonlinearity=None should be replaced by output_nonlinearity=lasagne.nonlinearities.softmax

@paipai880429 Thanks for your comment I changed output_nonlinearity to softmax from the None, still
I am getting the same results, I think still there is something where I am making silly mistake.
One thing I forgot to mention that whenever I use predict method, it returns all zeros

@jayendra13 It seems that the learning process has never been started. Then, did you try to decrease your initial learning rate?

That might not be issue because initial random weights should give me some non-nan values for train and validation losses

Hello I have the same problem. How did you fix it? Thank you

I solved my problem, there were a set of value equal to inf ( it was an error) in my dataset.

Had the same issue and "softmax" fixed it for me !
Thks :+1:

@paipai880429 In my case I had a learning rate of 0.01, changing it to 0.001 solved the problem, thanks for the tip. Why would the learning rate lead to this numerical instability?! Is it related to dataset size? Mine is big. Thanks


Spike: Legal disclaimer in context

Check placement of legal disclaimer requirements with Dave Mac - then create tickets as needed.

Consider if it would be needed on any interim page between website and console
Consider if we need it on landing on console for everyone
OR if we can show it in context i.e. when someone decides to deposit, show it as part of that journey? (which I think is our preference)

Dropping the current legal disclaimer here as it's hard to reproduce:

So… just spoken to Dave Mac and he did not recognise this content - it didn't come from him.
Looks like a 'starter for 10' from Barney has been built with the intention to update it later, but I think that bit may have been forgotten about.

One for @campbellssource to chase Dave Mac on.


[Bug] No model will run in an Iphone 13 mini

All the models available (even using testflight) will fail to run with memory issues or just crash when input any text on an Iphone 13 mini. If the app is not supported, it will good to know in the documentation or directly disallowing to install it from the app store.

Same issue but with an IPhone 13.
Did you find any way to get it working ?

No workaround so far :disappointed:

I think that is a problem with the redpajama models, as after the update, is the only available now for iphones with 4GB of RAM.

Alas the Phi model from microsoft was posted some hours ago so...

Is this available in the TestFlight releases or should we use the AppStore ones?

The TestFlight version is the same as i tested so far... Both have problems of crashing with the RedPajama model... There are two problems being more specific, the first is that the option to download other models from HF was removed in this new versions and the second one it's with the RedPajama model as this one is a new updated version from MLC HF repository...

checkout #1554 , clsing this one for now

Great news!, can we test this fix using a specific version of the App Store or Test Flight?


[Pagination][Mobile] Pagination breaks on small devices

Testdevice: Chrome / DevTools / iPhone SE
Bug description: On very small devices the pagination breaks in two lines.
Expected behavior: If all buttons are not fitting in one row, then the first ones and the last one should be visible – in between there should be a placeholder "..."

fixed in version 9.1.0


Error XTSE0660: Duplicate named template

This error occurs any time, if there are two scenarios with the same label in one XSpec file.
Well, for example:
<x:scenario label="test 1">

</x:scenario>
<x:scenario label="test 1">

</x:scenario>

The error occurs independently of the position or level of the scenarios. For instance they can also be nested into other scenarios.
This happens with the plugin only. The XSpec standard transformation scenario works fine with this.
Tested in oXygen versions 19.0 and 18.1 (both full & developer)

It is something that I've introduced in: Issue 17. I've overridden the template name generation so I can control which templates are invoked through a driver XSLT that imports the compiled XSLT. When I closed the issue I said "the chances for two scenarios to have the same name are pretty slim so I've decided to leave it like this for now". Boy, was I wrong!!!

Ok, I understand. :-)
Well, I think it is not a bad requirement to have unique labels, but:

I took a while, until I found the reason for the duplicated templates. So at least a (Schematron) validtion would help. I think it can happen very easy, during dirty work on your XSpec script (just copy a scenario, make some changes, try it out - and fail, because you didn't change the label...)

In my case I have two scenarios as Test groups and inside I test similar stuff with different sub scenarios. So the sub scenarios have unique labels inside of the group, but not in the whole sheet:

<x:scenario label="group 1">
	<x:scenario label="test 1">...</x:scenario>
	<x:scenario label="test 2">...</x:scenario>
</x:scenario>
<x:scenario label="group 2">
	<x:scenario label="test 1">...</x:scenario>
	<x:scenario label="test 2">...</x:scenario>
</x:scenario>

So one (simple i hope) enhancement would be, to take the nested scenario labels into account for the template names.

Both of these points are valid.

I'm sorry for the wasted time... I supposed I could also analyze the exceptions and if the "XTSE0660" code is present I could give a hint about the possible cause.
Yes, I can definitely take the labels of the ancestors into account when generating the ID.
I'll do these as soon as I have some spare time.

Thanks Alex! Don't worry about my time. It is normal for me to I try to understand an error, before I post it somewhere. I just wanted to point out, how helpful a validation or a concrete error message would be for this issue.

Hi Alex,
just an annotation to this. I run in the same problem, if I use x:like for one scenario, which contains other scenarios.
Example:
<x:scenario label="Shared" shared="yes">
	<x:scenario label="Sub scenario">
		<x:expect label="copy">

		</x:expect>
	</x:scenario>
</x:scenario>
<x:scenario label="Scenario 1">
	<x:context>

	</x:context>
	<x:like label="Shared"/>
</x:scenario>
<x:scenario label="Scenario 2">
	<x:context>

	</x:context>
	<x:like label="Shared"/>
</x:scenario>

Scenario 1 and 2 are using the scenario "Shared", "Shared" contains other scenarios.
With the Ant XSpec framework it works, with the plugin I get the Duplicate named template error.
Maybe, this should be respected during the fix. I think this is a real case, though it is special. My use case: I have a complex test scenario tree and want to test two different context variants. The differences shouldn't have an influence of the tests.
Best Regards,
Nico

It took a lot longer than anticipated but I finally managed to fix (hopefully) the template ID generation.
@nkutsche if you feel lucky, you can update to the new version :) . If you go to Help->Check for addons updates... you should be able to install the new version. The new version is available at the same update site:
https://raw.githubusercontent.com/xspec/oXygen-XML-editor-xspec-support/master/build/update_site.xml

Hi Alex,
thanks for the fix! I definitly will update it after my vacation.
Best Regards,
Nico


Final adjustments to CI and smoketest

This corrects some the issues identified in my recently merged CI changes and adds a CLEANUP var to the smoketest

test

test


The info links for ipfs-see-all on dist.ipfs.io are broken

https://dist.ipfs.io/#ipfs-see-all
The links to the project changelog, github page and so on are all broken.

@reit-c thank you for the report. the right repo for this issue is https://github.com/ipfs/distributions
opened an issue there: https://github.com/ipfs/distributions/issues/147