David Dyer-Bennet
Patron
- Joined
- Jul 13, 2013
- Messages
- 286
This is with FreeNAS 9.10 stable and Firefox current (Windows). I read the old thread on this error message, but it seems to be entirely about fixes that should be in 9.10. Also, I get the problem on a straight HTTP connection as well as with HTTPS.
I get the login window, enter username and password, click the button to proceed, and get the login window again. If I proceed a second time then I get a bare screen with the error message.
I don't have physical access to the box right now; I'm getting to it via port remapping in a firewall (I've got separate ports mapped to the HTTP port and the HTTPS port at that IP address). I'm using the same general port-forwarding setup for another box at the same location, and I can get into it fine.
So, "https://<name of firewall system>:8143" is mapped to 192.168.1.181:443 at that site, for example, and port 8022 is mapped to port 80 at that site. If I try things like "http://<name of firewall system>:8143" I get the expected error saying I can't talk http to the https port, which tends to confirm that the port mapping is doing what I think it does.
GUI access worked locally last night what I was at that site (when I wasn't going through the port remapping), so the probability that that's somehow part of the problem is very high .
I get the login window, enter username and password, click the button to proceed, and get the login window again. If I proceed a second time then I get a bare screen with the error message.
I don't have physical access to the box right now; I'm getting to it via port remapping in a firewall (I've got separate ports mapped to the HTTP port and the HTTPS port at that IP address). I'm using the same general port-forwarding setup for another box at the same location, and I can get into it fine.
So, "https://<name of firewall system>:8143" is mapped to 192.168.1.181:443 at that site, for example, and port 8022 is mapped to port 80 at that site. If I try things like "http://<name of firewall system>:8143" I get the expected error saying I can't talk http to the https port, which tends to confirm that the port mapping is doing what I think it does.
GUI access worked locally last night what I was at that site (when I wasn't going through the port remapping), so the probability that that's somehow part of the problem is very high .