Cant renew sertificate on QNAP server

[korzh_yura]

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:
korzh.myqnapcloud.com

I ran this command:
its on the qnap server
It produced this output:
cant connect
My web server is (include version):
QNAP 431p2
The operating system my web server runs on is (include version):
QTS 4.4.3
My hosting provider, if applicable, is:
MGTS, Russia
I can login to a root shell on my machine (yes or no, or I don't know):
I don't know
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
QNAP standart control panel
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
I dont know - its inside QNAP

[Osiris]

I too can't connect to the IP address 109.252.76.93. Is it still correct?

[Rip]

Host is up.

PORT    STATE    SERVICE VERSION
80/tcp  filtered http
443/tcp filtered https

[Osiris]

@Rip

Host is up.

I can't tell that from the NMap output you've provided? I can't ping the host, I can't connect to port 80/443 (filtered as your output shows), nor port 21 or 22 to sum up some other common ports..

[korzh_yura]

I think my ISP blocked 80 port

[Rip]

I added a couple more ports you mentioned. Don't really want to hammer the IP to hard.

sudo  nmap -sV -O -Pnu -p 21-443 109.252.76.93
Starting Nmap 7.80 ( https://nmap.org ) at 2022-02-22 10:17 PST
Nmap scan report for 109-252-76-93.nat.spd-mgts.ru (109.252.76.93)
Host is up.
All 423 scanned ports on 109-252-76-93.nat.spd-mgts.ru (109.252.76.93) are filtered

[Osiris]

@Rip

-Pn

That option makes every host being up, at least as NMap is concerend. From the man page:

         -Pn: Treat all hosts as online -- skip host discovery

Try it with a random IP address you know can't be reached, e.g. a private IP range not active in your network.

So the incorrect IP address is still on the table as far as I'm concerned.

[Rip]

Always Learning! Thanks @Osiris

Nmap scan report for korzh.myqnapcloud.com (109.252.76.93) [host down]