Daniel Cook
Cadet
- Joined
- Jan 10, 2017
- Messages
- 5
I believe I'm running current stable FreeNAS 11.1-U7, or possibly 11.2-U2. If I get a chance to verify the next time I have 5 quality minutes with the machine before this bug repros I will edit my post.
My FreeNAS machine can get through a standard reboot without issue. At the console/command line I'm shown the 1-11 menu, the GUI can be logged into, the machine can be pinged from another device on the network, network shares are visible, and an SSH session can be established on Putty.
But within 5-10 minutes the UI goes unresponsive (mostly saying "Sorry, there was an error"), any active Putty session is closed by the host, shares are unreachable, and no new session can be started due to "Network error: connection refused". Note: the machine continues to be pingable on the local network, so it's not a full-blown network failure.
If I had a live GUI session going it gives the sorry message mentioned above. If I later try to re-establish the GUI by going to http://freenas/ui or similar I get the following in Chrome on Windows10:
This site can’t be reached
192.xxx.x.xxx refused to connect.
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
The only viable workaround is to restart the machine. I prefer not to upgrade to newer builds since the error might take place during the update and then I might be bricked.
My FreeNAS machine can get through a standard reboot without issue. At the console/command line I'm shown the 1-11 menu, the GUI can be logged into, the machine can be pinged from another device on the network, network shares are visible, and an SSH session can be established on Putty.
But within 5-10 minutes the UI goes unresponsive (mostly saying "Sorry, there was an error"), any active Putty session is closed by the host, shares are unreachable, and no new session can be started due to "Network error: connection refused". Note: the machine continues to be pingable on the local network, so it's not a full-blown network failure.
If I had a live GUI session going it gives the sorry message mentioned above. If I later try to re-establish the GUI by going to http://freenas/ui or similar I get the following in Chrome on Windows10:
This site can’t be reached
192.xxx.x.xxx refused to connect.
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
The only viable workaround is to restart the machine. I prefer not to upgrade to newer builds since the error might take place during the update and then I might be bricked.