Shell in a box is no longer working from VB Deck. I've really got used to this to save me logging in to the VB directly. Network settings are ok as I can access everything else.
Shell in a box is no longer working from VB Deck. I've really got used to this to save me logging in to the VB directly. Network settings are ok as I can access everything else.
Correction: Can't get Webmin either.
The old version of shellinabox from the VortexBox repository (2.10-2) works.
The new version of shellinabox from the Fedora repository (2.14-4) does not have the proper configuration file for VortexBox.
What happens when you go to http://vortexbox:4200 in your browser?
When you login to VortexBox, what does
show?Code:rpm -qi shellinabox
You have several choices:
1. To use shellinabox-2.14-4, you will have to edit /etc/sysconfig/shellinaboxd and change the line
toCode:OPTS="-s /:LOGIN"
and then enterCode:OPTS="--no-beep --disable-ssl --service /:SSH"
2. If you are using the Firefox browser, use fireSSH.Code:systemctl enable shellinaboxd.service systemctl stop shellinaboxd.service systemctl start shellinaboxd.service
3. If you are using the Chrome browser, use the Chrome extension for remote login.
See http://info.vortexbox.org/tiki-index.php?page=Login for details.
I updated the shellinabox wiki page to have the correct instructions for using version 2.14-4 from the Fedora repository; see http://info.vortexbox.org/tiki-index...ge=shellinabox
shell in a box stopped working
Ron,
Yesterday I updated my Vortexbox. Up until yesterday Shell in a box worked fine. Today it can no longer access the VBA. I confirmed that the VBA IP address is still 192.168.1.7. I tried both http://192.168.1.7:4200 and http://vortexbox:4200. Neither works. I tried it in Chrome and IE9.
I was able to verify in the VBA that I have shell in a box 2.14. I confirmed that the code was edited (previously) as per your instructions above and the shellinabox wiki page. I even stopped and restared shellinabox. Could the lastest update have somehow disabled or messed up the connection to shellinabox? I have Fedora 16 and Vortexbox 2.2. Any help would be much appreciated.
Jamie
Last edited by Flair; 12-05-2012 at 12:15 PM. Reason: added name and title
Has anyone actually managed to get ShellinaBox (v2.14) working?
After successfully using v2.10-2, as discussed by several people, the upgrade to v 2.14 appears to have broken it! rpm -qi shellinabox reports that I am running shellinabox-2.14-14.fc16.src.rpm and I have made the changes to the shellinaboxd config file detailed in the wiki. However, neither http://vortexbox:4200or http://<vortexbox-ip-address>:4200 work, both returning an 'unable to connect' error in Firefox and IE, even though I have manually restarted the service.
It's no big deal cos I can always use Putty but Shellinabox was defo handy so has anyone got any idea why 2.14-14 doesn't seem to work?
It's no big deal cos I can always use Putty but Shellinabox was defo handy so has anyone got any idea why 2.14-14 doesn't seem to work?[/QUOTE]
In the meantime I am using Chrome Secure shell.
I have got ShellinaBox v2.14 running.Originally Posted by enz01
Has anyone actually managed to get ShellinaBox (v2.14) working?
After successfully using v2.10-2, as discussed by several people, the upgrade to v 2.14 appears to have broken it! rpm -qi shellinabox reports that I am running shellinabox-2.14-14.fc16.src.rpm and I have made the changes to the shellinaboxd config file detailed in the wiki. However, neither http://vortexbox:4200
It's no big deal cos I can always use Putty but Shellinabox was defo handy so has anyone got any idea why 2.14-14 doesn't seem to work?
I recall while running a general Vortexbox upgrade through ShellinaBox ('yum clean all; yum update'), my session got stuck because Shellinabox was upgrading itself while running.... (I saw this in the lines, infact it was the last scrolling line).
If I remember right it took me some time.
I used 'Chrome Secure shell' to login again and tried several things to get it working again.
Please someone correct me if I'm wrong (or use on your own risk):
- 'yum check' will give an overview of anything not installed properly.
- 'yum-complete-transaction' will try to complete pending transactions.
Again I'm not sure what did the trick for me (NOTE-TO-SELF: must start keeping a Log of my adventures in Linux), whether it was the 'complete-transaction' or just deleting/reinstalling "shellinabox-2.14-14.fc16.src.rpm'.
hope you got it figurred, succes
cheers, bart
EDIT: Now I think longer about it, I'm quite sure it was just re-install the right rpm.
Because I always struggle with 'Chrome Secure shell', very long startup and I cannot get 'Copy-Paste' working, so I think I precisely wrote the name down and typed the command manually.
Last edited by bart; 12-17-2012 at 12:57 PM.
Following on from Bart :-
yum erase shellinabox
yum install shellinabox
Now follow Ron Olsen's instructions and it should work - it did for me just a few minutes ago
Posting Permissions
Reply With Quote
Bookmarks