core dumped from Uncaught SyntaxError: Unexpected end of JSON

[jaredatron]

Fresh docker install cannot create first SSL Cert. Throws JSON Parse error.

v2.9.19 © 2022 jc21.com. Theme by [Tabler]

Steps to reproduce the behavior:

1. using this Dockerfile:

version: "3"

services:
  app:
    image: docker.io/jc21/nginx-proxy-manager:latest
    restart: unless-stopped
    ports:
      - '80:80' # Public HTTP Port
      - '443:443' # Public HTTPS Port
      - '81:81' # Admin Web Port
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

2. docker-compose up -d
3. visit http://${ipAddress}:81
4. login as admin@example.com
5. change admin password
6. hit "add SSL Certificate"
7. enter domain anme
8. click "Test Server Reachability"

browser error: Communication with the API failed, is NPM running correctly?

logs:

[2/2/2023] [8:17:20 PM] [SSL      ] › ℹ  info      Testing http challenge for carbonlinc.io
Uncaught SyntaxError: Unexpected end of JSON input

FROM
./run: line 19:   299 Trace/breakpoint trap   (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

Operating System

• Ubuntu 22.04.1 LTS
• podman version: 3.4.4
• podman-composer version 1.0.3

The data and letsencrypt directories started out empty but now look like:

$ tree data
data
├── access
├── custom_ssl
├── database.sqlite
├── letsencrypt-acme-challenge
├── logs
│   ├── fallback_access.log
│   └── fallback_error.log
└── nginx
    ├── dead_host
    ├── default_host
    ├── default_www
    ├── dummycert.pem
    ├── dummykey.pem
    ├── proxy_host
    ├── redirection_host
    ├── stream
    └── temp

12 directories, 5 files

$ tree letsencrypt
letsencrypt
└── renewal-hooks
    ├── deploy
    ├── post
    └── pre

4 directories, 0 files

[jaredatron]

This could be a duplicate of #2442

[timnolte]

I too cannot use the "Test Server Reachability" functionality as I'm also seeing the same error response and core dump in the logs. Whether this is a duplicate of #2442 or not is not clear. Though I also have problems with renewing certificates and had to simply request a new certificate on a domain that is expiring soon.

[robsiera]

Me too. Fresh docker install v2.9.2. Same OS (Ubuntu Linux 22.04.2). Same issue. Same Errors.

[zero-thermo]

Also running into these errors with NPM v2.9.21 docker-compose setup on Debian 11 (bullseye).

[durzo]

+1 here too

[Will2knz]

Same issue here too

[nrgbistro]

Also getting this issue. Renewal seems to work but I cannot test or add a new domain to create a cert for.

[oliversturm]

FWIW, I see the same problem. However, when I tried to ignore the error and create the certificate, it worked fine. Now it's already in the list, when I run "test server reachability" from the menu the same error comes up. I don't care too much since everything else seems to be working, just thought I'd mention it because it seems to be a bit different from other experiences described here.

[EmileSpa]

The same error still exists in version 2.10.3.

[DartLazer]

I have the same error in version 2.19. It only prevents me from creating a certificate for one of the domains, the others seem to work fine.

[lloydsmart]

Getting the same error, running in Docker on Unraid. Can't add an SSL certificate and clicking "Test Server Reachability" crashes the container, every time.