ReadyPlayGo
Dabbler
- Joined
- Mar 2, 2016
- Messages
- 15
I'm running FreeNAS at 192.168.1.66. Here are my general system settings (all default).
I'm attempting to access the web GUI at my subdomain freenas.domain.com. I have an SSL cert from Letsencrypt, and the subdomain is reverse proxied to 192.168.1.66. For some reason, FreeNAS is refusing the connection to nginx.
Is there a setting in FreeNAS I'm missing that would affect how reachable/connectable it is?
I have plenty of other service running behind a reverse proxy, so it's not port 80/433 on my router.
nginx block:
I'm attempting to access the web GUI at my subdomain freenas.domain.com. I have an SSL cert from Letsencrypt, and the subdomain is reverse proxied to 192.168.1.66. For some reason, FreeNAS is refusing the connection to nginx.
Is there a setting in FreeNAS I'm missing that would affect how reachable/connectable it is?
I have plenty of other service running behind a reverse proxy, so it's not port 80/433 on my router.
nginx block:
Code:
server { #HTTP Config listen 80; server_name freenas.domain.com; root /var/www/freenas; index index.php index.html index.htm index.nginx-debian.html; location / { proxy_pass https://192.168.1.66; } listen 443 ssl; # managed by Certbot ssl_certificate /etc/letsencrypt/live/freenas.domain.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/freenas.domain.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot # Redirect non-https traffic to https # if ($scheme != "https") { # return 301 https://$host$request_uri; # } # managed by Certbot }