Last edited:
I'm hoping someone can help confirm if this is an issue with my set up, or an issue introduced by DSM 7. I have a reverse proxy set up that successfully directs subdomains to different applications running on my DS720+. I set this up years ago and have not had any issues. However, when I tried to add a new rule I could not get it to work. While troubleshooting, I tried changing the subdomain of an existing entry (i.e., video.mydomain.com > newvideo.mydomain.com). As expected the video subdomain stopped working, but the newvideo subdomain did not resolve. I did not change any other settings. When I changed the subdomain back to video it worked again. I followed these steps on 2 other existing subdomains with the same results. Note that these subdomains are defined only in my reverse proxy, not with my registar, so I do not think this is a DNS propagation issue.
Can someone using a reverse proxy and running DSM 7 try renaming one of their subdomains to see if the new subdomain can be reached? Thanks!
Nevermind. Of course 2 minutes after I post this I see my mistake. I forgot that rather than figuring out wildcards and Let's Encrypt certificates I had just requested a bunch of subdomains. I just ran out of them so my new reverse proxy entries did not match my certificate which was the cause of things not resolving.
Can someone using a reverse proxy and running DSM 7 try renaming one of their subdomains to see if the new subdomain can be reached? Thanks!
-- post merged: --
Nevermind. Of course 2 minutes after I post this I see my mistake. I forgot that rather than figuring out wildcards and Let's Encrypt certificates I had just requested a bunch of subdomains. I just ran out of them so my new reverse proxy entries did not match my certificate which was the cause of things not resolving.
