Project

General

Profile

Bug #26410

Browser Access to FreeNAS

Added by Charles Elliott almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
No priority
Assignee:
Release Council
Category:
GUI (new)
Target version:
Seen in:
Severity:
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

There is no way to file a bug from this URL: bugs.freenas.org, or if it is possible, I cannot find it.
In the past, I could only log in to FreeNAS with Chrome; I could not access FreeNAS with IE, and Edge did not exist. After the last update (9.10.2-U6), Chrome cannot access FreeNAS. Chrome requests the login name and password, but thereafter displays a blank page. Chrome still can access the Asus TM-AC1900 router, but that has not been extensively tested. However, now it is possible to use IE 11 and Chrome to access FreeNAS, but it is read-only; as soon as I try to input data to the shell, Chrome and IE break the connection. In any case, the connections sustain for only a few minutes.


Related issues

Has duplicate FreeNAS - Bug #25830: Update Dojo Toolkit to 1.12.2 Resolved2017-09-10

History

#1 Updated by Charles Elliott almost 3 years ago

  • File debug-FreeNAS-20171030121941.txz added

#2 Updated by Dru Lavigne almost 3 years ago

  • File deleted (debug-FreeNAS-20171030121941.txz)

#3 Updated by Dru Lavigne almost 3 years ago

  • Has duplicate Bug #25830: Update Dojo Toolkit to 1.12.2 added

#4 Updated by Dru Lavigne almost 3 years ago

  • Private changed from Yes to No
  • Seen in changed from Unspecified to 9.10.2-U6

Charles: this is fixed in 11.1-BETA1.

#5 Updated by Dru Lavigne almost 3 years ago

  • Status changed from Unscreened to Closed: Not Applicable
  • Target version set to N/A

#6 Avatar?id=14398&size=24x24 Updated by Kris Moore over 2 years ago

  • Status changed from Closed: Not Applicable to Closed

Also available in: Atom PDF