- CheckMates
- :
- Products
- :
- Quantum
- :
- SMB Gateways (Spark)
- :
- SMB R81.10.15 CLI window access fails in FireFox
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
SMB R81.10.15 CLI window access fails in FireFox
One of the new, long awaited features for SMB R81.10.15 is an own CLI window in WebGUI. But while this works perfectly in GAiA, SMB R81.10.15 fails with a self-signed certificate error!
When first connecting to the SMB, i use no :4434 o.s. and click on accept risk and continue:
Now, i can log in to WebGUI and try to call the CLI wondow, but in vain:
Here, i can not accept the risk and continue again - i have really not being able to find out how i could enable the use of this CLI window...
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You will have to add the needed exception manually to FF:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I went into my system (using port 4434, typed "thisisunsafe" to bypass the TLS warning)...and clicked on the prompt button.
Spinning wheel...
Paging @Amir_Ayalon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Actually, it looked like it timed out.
When I refreshed the page:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Does it work if you try to open it from chrome?
Thanks,
Dafna
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Using Edge it does work - but not in FireFox ! What wants to use a Google/MS browser ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is not so easily done as you suggest - the first exclusion is easy as FF shows it for you to accept, but the second one for :5555 must be defined manually, see my screenshot above!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You will have to add the needed exception manually to FF:
