NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Unable to check for site reachability/create SSLs on Debian 11
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker image? Yes - Are you sure you're not using someone else's docker image? Yes
- Have you searched for similar issues (both open and closed)? Yes
Describe the bug
When trying to "Test Server Reachability", I get the following error on the dashboard:
Communication with the API failed, is NPM running correctly?
When looking into the container logs, I get this error:
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
Model#$omit is deprected and will be removed in 3.0.
[11/29/2022] [4:59:56 PM] [SSL ] › ℹ info Testing http challenge for pics.mysite.com
Uncaught SyntaxError: Unexpected end of JSON input
FROM
./run: line 19: 331 Trace/breakpoint trap (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
Nginx Proxy Manager Version
v2.9.19
To Reproduce
Steps to reproduce the behavior:
- Go to add SSL
- Click on Let's Encrypt
- Add Domain
- Click "Test Server Reachability"
- See error
Expected behavior
I expect it to tell me whether or not it can reach the domain so I can generate the SSL.
This has only started happening recently
Operating System
Debian 11 on Linode
Additional context
I've also tried downgrading as far down as 2.9.15 just to troubleshoot. I'm able to use the sites that were up prior to the issues starting, but I'm unable to add any additional SSLs, which prevents me from adding more domains.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Add SSL and Test Server Reachability flow on the reported Nginx Proxy Manager v2.9.19 Docker image, then inspect the container logs around the SSL HTTP challenge. Done means the reachability check returns a result without crashing and a reachable domain can proceed to SSL creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, docker, nginx, node.js, typescript
- Domain
- backend, devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100