SOLVED Freenas GUI not accessible from different subnet (but SSH access works fine)

blobtheblob

Cadet
Joined
Jun 21, 2019
Messages
1
Hi there,

I am having an issue accessing the Freenas GUI with a new IP. I have configured the Freenas network interface through the command line to the new IP. I can access the Freenas box from my main PC via SSH with no problems. I can also ping between freenas and my pc (both ways) with no issue.

When I access Freenas via my web browser, I get the HTTPS certificate error (which I accept) and then it just seems to hang. It seems to be trying to access the websocket and get some js files but nothing is happening. Eventually it times out.

I'm unsure as to the cause... If it was a network issue then I wouldn't be able to SSH into the box or get the HTTPS error. So it indicates something freenas side isn't happy. The freenas logs dont seem to be showing any errors either. I've restarted both nginx and django with no luck. Any ideas?

*solved* it was an issue with paravirtualised ports. changed to e1000 and fixed
 
Last edited:
Top