@wraeuk Hello again. Nice find and thanks for the report; but if nginx is no longer requesting port 80 I’m puzzled on why it’s fussed that it’s not available. Also I wasn’t able to reproduce this:
No rock-ons Rockstor admin UI OK (https only)
install http->https redirect (using suggested 80 port)
admin UI OK still (but also worked via http)
reboot
admin UI OK still by http & https
and after the reboot I also have:
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
d1860402e5d7 geldim/https-redirect "/bin/sh -c nginx" About an hour ago Up 21 minutes 0.0.0.0:80->80/tcp redirect-http-to-https
second reboot and no change.
However my test setup was a KVM virtual machine using DHCP.
Not sure what could be going on.
Have you looked at your:
/var/log/nginx/error.log
for any clues?
The Rockstor version I tested this on was my current dev release which is ahead of testing but don’t think there has been any network or docker related changes since 3.9.0 anyway.
With the Rock-on switched off I get:
curl -i -k "http://rockdev.local"
curl: (7) Failed to connect to rockdev.local port 80: Connection refused
and with it switched back on again I get:
curl -i -k "http://rockdev.local"
HTTP/1.1 301 Moved Permanently
Server: nginx/1.6.2
Date: Sun, 14 May 2017 12:23:05 GMT
Content-Type: text/html
Content-Length: 184
Connection: keep-alive
Location: https://rockdev.local/
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.6.2</center>
</body>
</html>
And Rockstor’s version of nginx is much newer:
yum info nginx | grep 'Version'
Version : 1.10.2
Hears a thing though:
curl -I -k "https://rockdev.local"
HTTP/1.1 200 OK
Date: Sun, 14 May 2017 12:34:34 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Keep-Alive: timeout=20
Server: gunicorn/0.16.1
Vary: Cookie
...
Note the Server: gunicorn/0.16.1
So looking to your:
/opt/rockstor/var/log/gunicorn.log
Might be of use also.
Hopefully this will help with diagnosing things further, but I don’t get the same admin UI blocking behaviour you describe here.