Update port to brew ?
Remote file manager
Been on hold for 8 years. Marking as won't fix.
IPv4 port forwarding GUI not responding
Just putting on-hold as I'm undecided longer term if I will change this behaviour due to resourcing.
Groups not sorted alphabetically
Indeed, you are correct.
Remotebox segfaults on Gnome 44.1
RemoteBox is written in Perl. If it segfaults, then I'm 99.999% certain it's an issue with one of the dependencies it relies on, especially on a distro like ArchLinux.
Option to mute VBox/VNC Ext Pack message on every connection
Cannot cancel a connection attempt
The installation instructions are based on the packages directly from Oracle, so if there's an issue with Ubuntu's own VirtualBox install then that is out of scope for the installation instructions and they should indeed fix their packages. Please let me know if that is the case. A package could be made for apt and Ubuntu, but I do not have the resources to maintain packages for specific operating systems. Please clarify whether the amendment is needed due to Ubuntu's own VirtualBox package? Tha...
Ubuntu 24.04 support Client / Server
Multi server management
No indication for changes after last snapshot
Teleportation/Migration
Request created over 10 years ago. It's safe to say it's not gonna happen.
Update port to brew ?
It's something I'm willing to consider, depending on the work involved in maintaining it, but in general I'm struggling to find time to keep RemoteBox running with the latest version of Virtualbox so maintaining specific packages for operating systems is tricky.
Update port to brew ?
RemoteBox freeze
RemoteBox freeze
Works for me fine, I cannot reproduce your issue, is it still happening?
No indication for changes after last snapshot
Importing appliances with old names lying around
Tarball Install dependencies to run RemoteBox from Ubuntu 21.10 don't work
Works for me. I'm assuming you don't have standard repos enabled or and outdated cache.
Works for me. I'm assuming you don't have standard repos enabled or and outdated cache.
gtk_buildable_get_name: assertion 'GTK_IS_BUILDABLE (buildable)' failed
remotebox3.1
Not a bug. You don't have your X display setup configured correctly.
Not a bug. You don't have your X display setup configured correctly.
See the attached screenshot - those two buttons control whether groups are shown as expanded or minimised by default. The last button used, sets that preference. Unfortunately there's no way currently to have it remember on a "per group" basis, so when the list refreshes it'll default to all expanded or all minimised. I concede that it's not great from a UI perspective With regards to the order of the groups, I thought they were in alphabetical order so if they aren't, I'd consider it a bug, so feel...
That's good to hear, a work around at least
All good - you got it working that's the main thing
RemoteBox certainly does work on a Raspberry Pi 4 providing you're running some kind of Linux distro on it.
You haven't installed xfreerdp which is one of the requirements stated in the docs. What distribution are you using, from the screenshot it suggests Ubuntu based in some way? xfreerdp needs to be installed on the same system that RemoteBox is installed on. Try: sudo apt-get install libgtk3-perl libsoap-lite-perl freerdp2-x11 tigervnc-viewer Then relaunch RemoteBox There's also a newer version of RemoteBox available than 2.7
Interesting issue there Kevin. Tanks for pointing that out. Seems like a compatibility issue with the Xserver in MobaXterm. Please let me know if you find it gets fixed in MobaXterm. I'll add a note to the FAQ about it. I'll leave the "bug" here for the moment
You haven't installed xfreerdp which is one of the requirements stated in the docs. What distribution are you using?
I wouldn't say it's excessive in itself, I have around 50 guests but then between my desktop and my server it's a 10Gbit link, so latency isn't an issue. It boils down to, the more guests you have, the more API calls RemoteBox has to make to grab the list of guests. Those calls occur synchronously and in serial so on a high latency link or a link with some packet loss, performance just sucks. There's 100% no problem running RemoteBox within a VM, even under the VirtualBox instance you're connecting...
Do you have a lot of guests? Although I'd expect it to be quicker than 7 minutes (depends on how many guests you have really), RemoteBox will not perform well over high latency connections and particularly if there's any kind of packet loss.
Do you have a lot of guests? Although I'd expect it to be quicker than 7 minutes, RemoteBox will not perform well over high latency connections
What does the message log in RemoteBox say? What user are you running the web service as? What user are logging in with?
Glad it's working now at least. Creating a NAT Network is simply how VirtualBox works. It lets you create multiple NAT networks for any number of VMs and so RemoteBox essentially has to follow that design.
Hi Charles. Ok those messages are benign and can be ignored. I'll see if I can replicate under 20.04
Thanks Charles. Does there happen to be any output on the command line behind where you've launched RemoteBox? That might be be able to give me some indication. What are the symptoms you're seeing when it's not OK is the GUI hanging or something else? Thanks
Thanks Charles. Does there happen to be any output on the command line behind where you've launched RemoteBox? That might be be able to give me some indication. Thanks.
If you're not launching it from MobaXTerm, it will not work unless you have a separate X server installed and running. If you are launching from MobaXterm, ensure it's internal X server is running and you have firewalled off the open ports.
UI hangs
A late reply, but can you try with RemoteBox 2.8?
Perl dependency repository down
Future versions will require Gtk3. This is not a bug of RemoteBox so please post in the discussion forum
Gtk-WARNING **: cannot open display:
This is not a bug, but your configuration of WSL. Please post in the discussion forum
no more libgtk2-perl in debian bullseye... libgtk3-perl ?
RemoteBox has been ported to Gtk3 and will likely be available in the next major release (probably 3.0)
My internal version of RemoteBox has been ported to Gtk3 and is undergoing testing. The next major release will require perl-Gtk3 with the Gtk2 version being deprecated.
Unfortunately I don't have a work around at this point in time, but someone else might. Debian are doing their best to remove most of the GTK2 stack entirely which is only going to make it harder to retro-fit. I'm considering options because continuing to use GTK2 is only going to get harder, unfortunately switching to GTK3 isn't going to be trivial and it's definitely a case of work versus reward. The other interim solution I'm considering is maybe a flatpack or something like that.
No worries, I just can't repeat the issue you're having as it's working perfectly fine for me. A couple of questions though to rule some things out. What version of VirtualBox are you using with RemoteBox and what OS is VirtualBox running on? Are you running RemoteBox on Ubuntu? If so, which desktop environment are you using?
Invalid managed object reference
No response
2.7 no virtual machines shown.
No response
You will need to use the 'WSL' method on Windows in that case. Links to video files showing how to do it are available here https://remotebox.knobgoblin.org.uk/?page=installwindows
There's not really enough information on what was done there, but it looks to me like stale data. I'm suspecting something was changed on the VM without RemoteBox being refreshed for example.
RemoteBox is free to use and modify, however if you find RemoteBox useful, please consider sending a donation. Thanks https://www.paypal.com/donate?token=ZG2PIGf5ynxG5ACSbqKMyETpyZIPF0m6raRjlvHUqbgYsPsG2INWmWwWdD6pRNb7mrKfxNsYXinRygAV
I'd suggest running it manually on the server as the user you intend to run it as like this: vboxwebsrv -t -H 192.168.2.187 It should output any errors. If it doesn't connect to it. Are you using VirtualBox directly from VirtualBox or your disto's packages?
I also meant to add, that I'm pretty sure when you do systemctl status is should be report as active running, NOT active exited. This tells me your vboxweb service is quitting. Look at your /var/log/vboxwebservice.log file to see any error. If it's empty or doesn't exist then your web service doesn't have permissions to write to it. This will also cause it to fail.
It tentatively looks fine, but on the windows box can you install telnet (if not already installed). It's part of the Windows Features options. With telnet, do the following: telnet 192.1682.187 18083 This should verify network connectivity at least. On the linux box I'd check that the weboxwebsrv process is actually running with ps -aef also
You're right it would, but there hasn't been much call for it, essentially myself being the only person that's written any of the code. I'm more than happy to consider contributions from others though. Probably as a unified diff against an official release at this stage, unless there was a sudden rush of active contributors
Fixed now. Version 2.7 has also been placed on SourceForge. Thanks for letting me know.
Yes I neglected to upload version 2.7 to sourceforge. However 2.7 is available at this link http://remotebox.knobgoblin.org.uk/downloads/RemoteBox-2.7.tar.bz2 There's nothing to compile, it's written in Perl so the "binary" IS the source code.
Hi, No worries. :-)
In general RemoteBox runs on the client machine and not the same machine that VirtualBox is on. I have no idea what you're trying to do there.
Looks OK to me. I don't think you need quotes unless you've got things like spaces in the filenames, but mine has quotes.
And did you do apt-get install libgtk2-perl libsoap-lite-perl freerdp-x11 tigervnc-viewer as per the manual?
What does your config file show? They changed the behaviour in recent editions of VirtualBox with regards to logfile writing. It might be that you're hitting. On your VirtualBox server try this instead Change the "virtual" user to be whatever you use... mkdir -l /var/log/vbox chown virtual:virtual /var/log/vbox Change the logfile as appropriate in your /etc/default/virtualbox file. VBOXWEB_LOGFILE="/var/log/vbox/vboxweb.log" Restart the web service
Hi, Honestly, if you read the manual it tells you exactly what to do. Not only is it included in the archive, but available right here: http://remotebox.knobgoblin.org.uk/docs/remotebox.pdf But firstly, it's not a shell script but a perl script/ ./remotebox is all you need if the dependencies are installed
Might be a stupid question, but you definately have VirtualBox installed right? Those files belong to the VirtualBox package. Are you using a VirtualBox package made by Ubuntu or the official VirtualBox one?
What does the message log show at the bottom? What user is the vboxwebsrv running as? What user are you connecting as?
What do the contents of your file /etc/default/virtualbox show?
auto-connect reset
Invalid managed object reference
What this really means is that the underlying state of VirtualBox has changed with RemoteBox knowing, so it's using old references. This could be for a number of reasons including: Using the virtualbox web service simultaneously with other software The virtualbox back end process being restarted or crashing * Using the wrong version of VirtualBox for the client you're using I'll need more info to be able to detemine what is going on.
auto-connect reset
Yes, there does seem to be an issue around saving of profiles when using the normal close button. Explicitly clicking from the menu seems to work as expected. I will look into this By the way, it's possible to override the login using command line paramters to remotebox also.
Guest Display will not work using "External" authentication
Guest Display will not work using "External" authentication
Strawberry Windows Docs Outdated
Updated the docmentation as requested. Thanks.
The long winded answer is it depends on the XDG definitions your distro is using for the user specific configuration directory. But in most cases this is usually ~/.config/remotebox-profiles.conf in your homespace, which should be the case with Ubuntu.
I've checked here and it's working for me as expected. If you launch RemoteBox from the command line and then try to open the guest display, does xfreerdp show any more information? Note, when using username (ie %U) and password (ie %P) substituion these are substituted with the exact same username and password that you logged in to remotebox as. This user must also exist on the server. On the server, are you able to run the dmesg command? Does it show errors such as this at all? VRDEAuth[1547]:...
Guest Display will not work using "External" authentication
I've reassigned to 2.6 and will take a look. Thanks for reporting
Asking for vbox:IVirtualBox_getVersion generates error 500
That's great news then so far. There's an updated pre-release available. 2.6-PR2 with quite a few changes although most of it being eye candy. Happy New Year.
Yes there's a pre-release available for download aty the link below (RemoteBox 2.6-PR1) which adds VB 6.0.0 compatibility and a few other bits. http://remotebox.knobgoblin.org.uk/downloads.cgi I actually thought I'd published this about a week ago, but realised I forgot to make it 'live'. RemoteBox v2.5 will mostly work with VB 6.0.0. The main API changes are around video capturing, so if you don't use that you'll be mostly fine.
Good idea regarding a Windows Icon. I've added one on the downloads page for RemoteBox and will include it in new releases. If you download the .ico file, place it in the RemoteBox folder you can then change the icon of the shortcut to use it.
Remote RS232 port
You'll need to connect directly to the RS232 port of the server that VirtualBox is running on. However it is possible to redirect the serial port anywhere by using socat if you're using Linux or at least a UNIX type system as both the server and client.