Test Server Reachability Error

Help
1

My domain is: shs0262.duckdns.org

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

My hosting provider, if applicable, is:duckdns

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

In the Nginx Proxy Manager Test Server Reachability, an error keeps popping on.

  • There is a server found at this domain but it returned an unexpected status code Invalid domain or IP. Is it the NPM server? Please make sure your domain points to the IP where your NPM instance is running.

How Can I fix this problem??? I want the solution so bad!!!

2

That is probably something better asked at the NPM forum. That is an error message coming from their system. That said your DNS A record is pointing at a private IP address. That needs to be your public IP address

Also, your dns configuration looks faulty

https://dnsviz.net/d/shs0262.duckdns.org/dnssec/

4 Likes
3

@shs0262

Here is a list of issued certificates crt.sh | shs0262.duckdns.org, the latest being 2024-07-01.
However here https://decoder.link/sslchecker/shs0262.duckdns.org/443 and here Hardenize Report: shs0262.duckdns.org are showing the certificate being served is self-signed and not one of the issued certificates.

Testing and debugging are best done using the Staging Environment as the Rate Limits are much higher.

1 Like
4

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