Remote access = blank config pages on OBi100!!!

<< < (2/3) > >>

aczu:
Quote from: Shale on March 28, 2013, 09:44:38 pm

Quote from: aczu on March 28, 2013, 08:18:26 pm

Thanks for the suggestions.

I was using Chromium 25.  Chrome 26 also displayed blank pages  Iceweasel 10 displayed error messages, typically an XML Parsing error.  I'll keep trying  :)


Well,I guess that covers a spectrum of browsers, but maybe you could try Firefox or IE also.


I use Debian Linux, and Iceweasel is a rebranded version of Firefox.  I happened to have IE6 on WinXP in virtualbox, so I tried it and it didn't work either.  Right now I don't feel like going through the process of upgrading my WinXP image - I only keep it for upgrading firmware of a couple of devices that don't support Linux.  I also tried Opera and it's a no-go too - invalid XSLT stylesheet errors everywhere.

So, I think I'll try a remote desktop approach and see if that works.  Thanks for the suggestions.

Shale:
I just tried using NoScript on Firefox to disable scripting to the OBi, and that hoses the right side. I don't think it needs Java, but it apparently needs some scripting to work. The right side is not blank but it appears as a bunch of non-informative text.

QBZappy:
Try this:
The Browser Sandbox lets you run any browser instantly from the web in an isolated virtual environment.

http://spoon.net/browsers/

Edit: Realized you run Linux. Spoon.net won't work for you.

QBZappy:
aczu,

In your case you might try installing a portable browser in your WinXP in virtualbox. No installation required.
http://mozilla-firefox-portable.en.uptodown.com/old

giqcass:
Try putting it in the DMZ temporarily for testing purposes.

Navigation

[0] Message Index

[#] Next page

[*] Previous page