RemoteBox Logo

Open Source VirtualBox Client with Remote Management

Documentation

RemoteBox Manual

RemoteBox 2.5 : PDF Manual

RemoteBox Client Installation

Installing on Arch Linux [EXTERNAL]
Installing on Debian / Ubuntu Linux
Installing on Fedora Linux
Installing on FreeBSD
Installing on Mac OS X
Installing on Mageia Linux
Installing on Mint Linux
Installing on NetBSD
Installing on OpenBSD
Installing on OpenSUSE Linux
Installing on Red Hat Enterprise / CentOS / Oracle Enterprise Linux
Installing on Solaris / Indiana
Installing on Windows

Videos

YouTube : Installing Remotebox 2.5 on Windows 10
YouTube : Setting up VirtualBox Server and installing RemoteBox on Ubuntu [by Linux Help]

FAQs

When troubleshooting problems with RemoteBox, launching it from the command line may provide additional debugging information. Consulting the web service logs and the guest logs may also be useful. If you believe you've found a bug, please raise a ticket here

1. General FAQs
2. Connection FAQs
3. Display FAQs
4. Known Issues

General FAQs

  1. Why is RemoteBox restricted to certain versions of VirtualBox? VirtualBox versions are generally of the form Major.Minor.Micro (e.g. 4.2.8). VirtualBox only guarantees API compatibility between versions if it is the Micro suffix which has changed. For example 4.2.8 is compatible with 4.2.0, but 4.2.1 is not compatible with 4.0.0. RemoteBox only targets the latest version of the API at the time of release. RemoteBox will warn you, if you use an incompatible version.
  2. I run an old version of VirtualBox, what version of RemoteBox do I need? You can downloaded older versions of RemoteBox, but they are not supported. Bug fixes and updates are applied only to the latest version. You can see which version of VirtualBox is supported by looking at the 'About Menu' in RemoteBox.
    RemoteBox Version Required VirtualBox Version
    V2.4 and newer v5.2.x
    V2.3 v5.1.x
    v2.1 v5.0.x
    v1.9 v4.3.x
    v1.5 v4.2.x
    v1.3 v4.1.x
    v0.9 v4.0.x
    v0.5 v3.2.x
    NONE v3.1.x and earlier editions
  3. I have an old version of GTK2, what version of RemoteBox do I need? You can downloaded older versions of RemoteBox, but they are not supported. Bug fixes and updates are applied only to the latest version.
    RemoteBox Version Minimum GTK2 Version
    v1.6 and newer v2.24
    v1.5 v2.22
    v1.1 v2.16
  4. Does the OS that RemoteBox is installed on, need to be the same OS as the VirtualBox server? No, the client machine can be running a different operating system to the server. For example, you can have RemoteBox installed on a Linux machine and connect to a VirtualBox server running Windows.
  5. Which operating systems does RemoteBox run on? RemoteBox is known to run on Linux, Solaris, MacOS X, Windows, NetBSD, FreeBSD and others. It should run on any modern flavour of UNIX providing the required dependencies are installed.
  6. Which server operating systems running VirtualBox, does RemoteBox support? RemoteBox supports connecting to servers running Linux, Windows, MacOS X, Solaris and FreeBSD.
  7. Does RemoteBox support Teleport? No, not at this time. It is unlikely RemoteBox will ever support this feature.
  8. Does RemoteBox support iSCSI LUNs? RemoteBox does not support connecting to iSCSI LUNs directly from its Virtual Media Manager. However you can use vboxmanage on the server to attach an iSCSI LUN, which will then be visible as hard disk in RemoteBox.
  9. How do I install the VirtualBox Guest Additions? Ensure the guest has a virtual optical drive and attach the VboxGuestAdditions.iso to it. Run the appropriate installer inside the guest operating system. By default, RemoteBox automatically adds the VboxGuestAdditions.iso to the Virtual Media Manager (VMM) on login so it's always available for the guests.
  10. Can I convert a hard disk image to another format? Yes. Open the VMM and ensure the “Hard Disk” tab is select. Choose the hard disk to want to copy and convert. Select the “Copy & Convert” option and select the format you require. You will be prompted where you would like to save the new image. This operation will not alter the source image.

Connection FAQs

  1. What is the default port that the VirtualBox web service runs on? Port 18083
  2. Can I use RemoteBox to connect to VirtualBox on the same physical machine? Yes. Just ensure the VirtualBox web service is running on the same machine and by default connect to http://localhost:18083 with RemoteBox.
  3. Why do I repeatedly get disconnected from the server?
    • Ensure the heartbeat option is enabled in RemoteBox. 'File->Preferences->Heartbeat'
    • Ensure the VirtualBox Web Service has timeouts disabled. This is done by using the '-t0' option
    • If the issue persists then you have an underlying network problem

Remote Display FAQs

  1. What protocols are supported when using the Remote Guest Display? Starting with RemoteBox v2.5, both RDP and VNC are supported. Earlier versions of RemoteBox only had direct support for RDP although it's still possible to configure earlier versions to use VNC. Which protocol gets used depends on the extension pack installed on the server.
  2. Is it safe to close to the Remote Guest Display window while the guest is running? Yes, the guest will continue to run uninterrupted. The display can be reopened at any time by pressing 'Guest Display' on the toolbar.
  3. Can I use clipboard sharing (cut 'n paste) with the Remote Guest Display (RDP)? Yes you can.
    • In the guest's settings, set 'General -> Advanced -> Shared Clipboard' to 'Bidirectional'
    • VirtualBox Guest Additions must be installed and working in the guest
    • Your RDP client must have support for clipboard sharing and the option must be enabled.
    • For FreeRDP the option is '--plugin cliprdr'
    • For rdesktop the option is '-r clipboard:PRIMARYCLIPBOARD'
  4. Is sound supported when using the Remote Guest Display (RDP)? Yes.
    • In the guest's settings, set 'Audio -> Enable Audio' to enabled
    • Set 'Audio -> Host Audio Driver' to 'Dummy Audio Driver'
    • Set 'Audio -> Enable Audio Output' to enabled.
    • Set 'Audio -> Audio Controller' to a sound card which is supported by the guest operating system
    • The guest operating system must be correctly configured for audio, including the installation of drivers if necessary
    • Your RDP client must have support for playing audio and the audio option enabled
    • For FreeRDP the option is '--plugin rdpsnd'
    • For rdesktop the option is '-r sound:local'
  5. I get an error message saying 'Failed to Launch Remote Desktop Extension Server' You do not have the Oracle VirtualBox Extension Pack or the VNC Extension Pack installed on the server.
  6. Why are the mouse pointers are out of sync when using the Remote Guest Display? First ensure that the VirtualBox Guest Additions are installed and running within the guest. If the guest OS does not havd VirtualBox Guest Additions available for it, then changing the mouse type to 'USB Tablet' should aid synchronization. If that does not work, then it's not possible to sync the pointers.
  7. Can I use Remmina as my Remote Guest Display RDP/VNC client? No. Remmina does not support the required command line parameters to integrate with RemoteBox.
  8. Does RemoteBox support multiple virtual monitors for a guest? The short answer is no. If a guest is configured to have more than one virtual monitor, RemoteBox will only interact with the first display.

Known Issues

  1. I see SOAP versioning errors such as:
    Wrong SOAP version specified. Supported versions:
    1.1 (http://schemas.xmlsoap.org/soap/envelope/)
    1.2 (http://www.w3.org/2003/05/soap-envelope)
    
    You're affected by a bug introduced in RemoteBox v1.8. Upgrading to at least RemoteBox v1.8.1 should resolve the problem.
  2. I get an error message on the command line similar to the following:
    “Incorrect parameter at <path>/SOAP/Lite.pm” line 1993”.
    
    This is a bug in the implemention of Perl SOAP Lite that you have installed. If it's not possible to upgrade your installation, it can be worked around by editing the offending line in SOAP/Lite.pm as follows:
    die “Incorrect parameter” unless $itself =~/^d$/;
    
    replace with
    die “Incorrect parameter” unless $itself =~/^d*$/;
    
    (Note the addition of the asterisk *)
  3. I'm unable to login to the VirtualBox server, even though I know my credentials are correct. It occasionally works but mostly doesn't. This is a compatibility issue introduced in Perl v5.18 and fixed in RemoteBox v1.8.1. It's recommended that you upgrade to at least RemoteBox v1.8.1 or alternatively downgrade your Perl installation to v5.16. To discover your Perl version, you can use 'perl -v' from the command line.
  4. I'm using rdesktop as my RDP client but it gives the following error:
    Autoselected keyboard map en-us
    Failed to negotiate protocol, retrying with plain RDP.
    WARNING: Remote desktop changed from 800x600 to 1280x1024.
    X Error of failed request:  BadWindow (invalid Window parameter)
    Major opcode of failed request:  18 (X_ChangeProperty)
    Resource id in failed request:  0x0
    Serial number of failed request:  38
    Current serial number in output stream:  43
    
    This is caused by a bug introduced in rdesktop v1.8.0 and rdesktop v1.8.1 when used with VirtualBox. It's recommended that you migrate to using FreeRDP instead if it's available for your distribution. Alternatively, ensure you are using at least rdesktop v1.8.2 or a version lower than v1.8.0
  5. I'm using rdesktop as my RDP client and cannot use the mouse or keyboard, even though I know I have the guest configured properly.
    This is caused by a bug introduced in rdesktop v1.8.0 and rdesktop v1.8.1 when used with VirtualBox. Avoid these versions or use an alternative RDP client.
  6. Why is nothing displayed when I try to open the manual in RemoteBox? RemoteBox requires at least one PDF viewer to be installed. Secondly on UNIX & Linux systems, ensure xdg-open is installed. This is usually part of the xdg-utils package.
  7. I'm unable to take a screenshot of the guest or set a screenshot as an icon. Unfortunately this appears to be a bug with VirtualBox. Sometimes changing the configured video RAM can help, but not always.