Hello world,
I am having a problem with externally accessing DSM using a subdomain address (dsm.mydomain.lol). I hoping someone can help!
I recently configured my own domain to use Cloudflare as the DNS nameserver. I have my router pointing to Nginx Proxy Manager (NPM), which is a Docker container on my Synology NAS. This, in turn, serves all of my other docker containers/web services based on their own subdomain (i.e. vaultwarden.mydomain.lol, freshrss.mydomain.lol, dsm.mydomain.lol, etc...).
On the Cloudflare side, I have an 'A' record that points to my router's public IP. I have a wildcard CNAME record (*.mydomain.lol) and a 'www' CNAME record.
On the NPM side, I have created a Let's Encrypt SSL certificate for "mydomain.lol" and "*.mydomain.lol", utilizing the DNS challenge and Cloudflare API token. With all of my subdomains, I have the following options checked (on) in NPM:
Examining the Firefox browser console, I see that I am met with several 522 error codes. For example:
This page gives me some clues, but I am still not able to identify what's going on. Again, all my other subdomains loads my pages perfectly fine, which makes me suspect there something particular about DSM that is preventing the page to load properly. I never had this problem when using Synology's DDNS (mydomain.synology.me).
Any suggestions?
I am having a problem with externally accessing DSM using a subdomain address (dsm.mydomain.lol). I hoping someone can help!
I recently configured my own domain to use Cloudflare as the DNS nameserver. I have my router pointing to Nginx Proxy Manager (NPM), which is a Docker container on my Synology NAS. This, in turn, serves all of my other docker containers/web services based on their own subdomain (i.e. vaultwarden.mydomain.lol, freshrss.mydomain.lol, dsm.mydomain.lol, etc...).
On the Cloudflare side, I have an 'A' record that points to my router's public IP. I have a wildcard CNAME record (*.mydomain.lol) and a 'www' CNAME record.
On the NPM side, I have created a Let's Encrypt SSL certificate for "mydomain.lol" and "*.mydomain.lol", utilizing the DNS challenge and Cloudflare API token. With all of my subdomains, I have the following options checked (on) in NPM:
- Details
- Block common exploits
- SSL
- Force SSL
- HTTP/2 Support
- HSTS Enabled
- HSTS Subdomains
Examining the Firefox browser console, I see that I am met with several 522 error codes. For example:
Code:
GEThttps://dsm.mydomain.lol/webman/modules/ResourceMonitor/style.css?v=1648633174
[HTTP/2 522 No Reason Phrase 15443ms]
GEThttps://dsm.mydomain.lol/webman/modules/StorageManager/style.css?v=1648633174
[HTTP/2 522 No Reason Phrase 15440ms]
GEThttps://dsm.mydomain.lol/webman/modules/C3/style.css?v=1648633174
[HTTP/2 522 No Reason Phrase 15675ms]
GEThttps://dsm.mydomain.lol/webman/modules/TaskSchedulerWidget/style.css?v=1648633174
[HTTP/2 522 No Reason Phrase 15404ms]
GEThttps://dsm.mydomain.lol/webman/modules/SystemInfoApp/style.css?v=1648633174
[HTTP/2 522 No Reason Phrase 15700ms]
GEThttps://dsm.mydomain.lol/webman/modules/ActiveInsightUpdateNotify/style.css?v=1648633174
[HTTP/2 522 No Reason Phrase 15405ms]
GEThttps://dsm.mydomain.lol/webman/modules/FileChooser/style.css?v=1648199907
[HTTP/2 522 No Reason Phrase 15484ms]
GEThttps://dsm.mydomain.lol/webman/modules/Widgets/style.css?v=1648633174
[HTTP/2 522 No Reason Phrase 15401ms]
GEThttps://dsm.mydomain.lol/webman/modules/UpdateMaskApp/style.css?v=1648633174
[HTTP/2 522 No Reason Phrase 15417ms]
GEThttps://dsm.mydomain.lol/webman/modules/SharingManager/style.css?v=1648199907
[HTTP/2 522 No Reason Phrase 15667ms]
GEThttps://dsm.mydomain.lol/webman/modules/AdminCenter/style.css?v=1648174904
[HTTP/2 522 No Reason Phrase 15700ms]
This page gives me some clues, but I am still not able to identify what's going on. Again, all my other subdomains loads my pages perfectly fine, which makes me suspect there something particular about DSM that is preventing the page to load properly. I never had this problem when using Synology's DDNS (mydomain.synology.me).
Any suggestions?