[redacted] normally uses encryption to protect your information. When Google Chrome tried to connect to [redacted] this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be [redacted], or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged.
You cannot visit [redacted] right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.
What I used on my NAS is I ask Synology to "reverse proxy" everything that needed a certificate or have a webUI. If you didn't have that setup in your NAS, then you probably need to provide certificate to each instance of webUI application and keep it updated. I'm guessing the certificate served (in that error) is one that self-signed or provided by the application, not intended for production use.
It's just like running a Nginx or whatever web server on port 80 and 443, proxy everything on that server. It's much easier to manage certificate and diagnose issues with the proxy than digging into each application.
I'm using Nginx Proxy Manager and I'm receiving this error when I try to request a certificate.
Error: Command failed: /opt/certbot/bin/certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-7" --agree-tos --email "[redacted]@gmail.com" --preferred-challenges "dns,http" --domains "pham#ine.myasustor.com"
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Performing the following challenges:
http-01 challenge for pha#mine.myasustor.com
Using the webroot path /data/letsencrypt-acme-challenge for all unmatched domains.
Waiting for verification...
Challenge failed for domain pha#mine.myasustor.com
http-01 challenge for pha#mine.myasustor.com
Cleaning up challenges
Some challenges have failed.
at ChildProcess.exithandler (node:child_process:326:12)
at ChildProcess.emit (node:events:369:20)
at maybeClose (node:internal/child_process:1067:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)