You are here
DFromen - Tue, 2013/11/19 - 16:21
New virtual machine - LAMP Stack (version 13), VMWare Player (6.0.1 build-1379776). Static IP (10.20.0.40), behind a firewall.
When trying to access Web Shell (10.20.0.40:12320) I see a black screen - no login prompt. I'm running a Joomla website (restored from an akeeba backup). Webmin (:12321) and PHPMyAdmin (:12322) work correctly.
I really have no idea where to start. Any suggestions for a novice?
Thanks!
Forum:
Tags:
Try a different browser - worked for me
I had the same happening last week (in fact I still have it happening on one Machine, in Chrome Browser).
Works on other machines and in Firefox. Remember though, in Firefox you need to use a MINUS "-" rather than a DASH "-" as, at least for me, dashes don't make it to Webshell.
Re: Try a different browser
Thought I had checked all browsers, but apparently not. Firefox does work.
Thanks. :)
let me know how to fix Chrome if you find out.
My Chrome (one one XP box) not mending in WebShell. If you find a fix for Chrome let me know. Until then lets use Firefox. (In Fact the normal dash(-) is working in FireFox now.. way cool. Now just to make a Firefox base "self contained" appliance button like Chrome has with "Create Application Shortcuts"...(thoughts on that?.).. no need if none.. :)
Not sure...
There used to be an easy way to make a 'chromless' Firefox window (basically a browser window without any of the browser buttons or menus) but I haven't used Firefox for a long time so not sure how easy it is...
As for Webshell, a quick google turned up this: https://code.google.com/p/shellinabox/issues/detail?id=245
So looks likes it's a known issue and technically a Chrome bug. Although just like the previous Firefox issue (technically a Firefox bug) it will require Shell in a Box (the actual name of the Webshell software) to resolve it from their end... There is some workaround code provided but it may be easier to just use Firefox...
I have lodged a bug on the TKL Tracker
See here: https://github.com/turnkeylinux/tracker/issues/142
Add new comment