- Minor
Yeah, well... thats what happened. Unfortunately, having a valid cert for the <myhash>-subdomain apparently caused my unraid server to perform redirects. Which DOES make sense, but only if said record exists.
In addition to fixing the vanishing-record problem, I would propose the following:
- Make the SSL connection optional, i.e. if a user wants to use http instead of https, let him. In particular for local connections that is less of an issue.
- Make the redirect optional, i.e. if the server is addressed via a domain that does not fit to its cert, it does not "force" the redirect. The user will have to deal with the ensuing warning, but he can at least still access his server.
- Maybe: allow for specifying an explicit redirection address (again, never mind the cert)
- Maybe: Make the redirect-module/nginx check if there actually IS a DNS record that matches the redirect, if not... do NOT redirect ;). Checking "once in a while" would be a start.
This would safe your customers the hassle of having to enter the https://<my-local-ip> alternative, avoiding any DNS resolution and hence the redirect.
Btw: Great product, still on the trial version but I really love it so far, truenas and proxmox can't compare! Keep it up =)!