phpVirtualbox console not working - blank

    • OMV 3.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • phpVirtualbox console not working - blank

      phpVirtualBox 5.0-5

      I start the VM, can connect with VNC on port 9000, RDP also works fine, the preview in phpVirtualBox browser window shows the correct preview.
      But when i click on the Console button, the console is blank, only showing "Requested desktop size:" followd by a "Detach" Button.


      Source Code

      1. root@nas:~# service vboxweb-service status
      2. ● vboxweb-service.service
      3. Loaded: not-found (Reason: No such file or directory)
      4. Active: inactive (dead)
      5. root@nas:~# service vboxweb-service start
      6. Failed to start vboxweb-service.service: Unit vboxweb-service.service failed to load: No such file or directory.
      That doesn't seem right... ?
    • Hey,
      Console will not allow you to connect because of java security policy.
      I found some thread on google to activate it but you need to add exceptions for all ports so I considered it as pain in the ass and use VNC/RDP.

      Also Chrome not support java more so no option here.
      Firefox will exclude java soon so also dead.
      Only IE will support java, so still bad choice :)

      Effort is not woth of this option.
      Debian 8.6 Jessie + OMV 3.0.latest Kernel: Linux 4.8.0-0.bpo.2-amd64
      Processor: Intel Core 2 Duo E8400@3GHz
      Memory: 4GB RAM
      OS-HDD: Samsung SSD 120 GB +LVM

      Full media and download center configured.

      BIG and special thanks for OMV-Extras team for great plug-ins (especially: TeamSpeak, VirtualBox, Sonarr, Radarr, and rest I use :))

      ------------------------------

      Wise guy don't know everything, he can search or ask!
      Don't ask me via PM!
    • xtrumph wrote:

      Any help please....
      Enable remote desktop and connect to the omv ip with the port specified in phpvirtualbox. Never used the console even when I did use virtualbox.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • xtrumph wrote:

      How can i do that?
      I don't have virtualbox/phpvirtualbox installed anywhere. Did look in each VM's settings under display properties or something like that?
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • If it is on by default, then you should be able to use the remote desktop client to connect to the ip:port that it lists there. This is the same as connecting to the console.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Tii wrote:

      is the shell output as quoted in the OP expected behaviour ?
      No. Usually that happens when the vbox user has a different password than what is stored in /etc/default/openmediavault-virtualbox. We usually tell people to uninstall all virtualbox packages and plugin, delete vbox user, and the virtualbox files in /etc/default/. Then reinstall.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Tii wrote:

      is that a hash or plain text ?
      plain text. I suppose you could try setting the vbox user password to whatever is in that file. Then restart vboxweb-service.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      try setting the vbox user password to whatever is in that file. Then restart vboxweb-service.
      to no avail ...

      Shell-Script

      1. root@backup-nas:~# passwd vbox
      2. Enter new UNIX password:
      3. Retype new UNIX password:
      4. passwd: password updated successfully
      5. root@backup-nas:~#
      6. root@backup-nas:~# service vboxweb-service stop
      7. Failed to stop vboxweb-service.service: Unit vboxweb-service.service not loaded.
      8. root@backup-nas:~# service vboxweb-service start
      9. Failed to start vboxweb-service.service: Unit vboxweb-service.service failed to load: No such file or directory.
      10. root@backup-nas:~# service vboxweb-service status
      11. ● vboxweb-service.service
      12. Loaded: not-found (Reason: No such file or directory)
      13. Active: inactive (dead)
      Display All
    • Shell-Script

      1. root@backup-nas:~# apt-get install --reinstall virtualbox-dkms
      2. Reading package lists... Done
      3. Building dependency tree
      4. Reading state information... Done
      5. The following package was automatically installed and is no longer required:
      6. linux-image-4.8.0-0.bpo.2-amd64
      7. Use 'apt-get autoremove' to remove it.
      8. 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
      9. Need to get 661 kB of archives.
      10. After this operation, 0 B of additional disk space will be used.
      11. Get:1 https://dl.bintray.com/openmediavault-plugin-developers/erasmus/ jessie/main virtualbox-dkms all 5.1.14-dfsg-1 [661 kB]
      12. Fetched 661 kB in 34s (19.2 kB/s)
      13. (Reading database ... 83846 files and directories currently installed.)
      14. Preparing to unpack .../virtualbox-dkms_5.1.14-dfsg-1_all.deb ...
      15. -------- Uninstall Beginning --------
      16. Module: virtualbox
      17. Version: 5.1.14
      18. Kernel: 4.9.0-0.bpo.2-amd64 (x86_64)
      19. -------------------------------------
      20. Status: Before uninstall, this module version was ACTIVE on this kernel.
      21. vboxdrv.ko:
      22. - Uninstallation
      23. - Deleting from: /lib/modules/4.9.0-0.bpo.2-amd64/updates/
      24. - Original module
      25. - No original module was found for this module on this kernel.
      26. - Use the dkms install command to reinstall any previous module version.
      27. vboxnetadp.ko:
      28. - Uninstallation
      29. - Deleting from: /lib/modules/4.9.0-0.bpo.2-amd64/updates/
      30. - Original module
      31. - No original module was found for this module on this kernel.
      32. - Use the dkms install command to reinstall any previous module version.
      33. vboxnetflt.ko:
      34. - Uninstallation
      35. - Deleting from: /lib/modules/4.9.0-0.bpo.2-amd64/updates/
      36. - Original module
      37. - No original module was found for this module on this kernel.
      38. - Use the dkms install command to reinstall any previous module version.
      39. vboxpci.ko:
      40. - Uninstallation
      41. - Deleting from: /lib/modules/4.9.0-0.bpo.2-amd64/updates/
      42. - Original module
      43. - No original module was found for this module on this kernel.
      44. - Use the dkms install command to reinstall any previous module version.
      45. depmod...
      46. DKMS: uninstall completed.
      47. -------- Uninstall Beginning --------
      48. Module: virtualbox
      49. Version: 5.1.14
      50. Kernel: 4.9.0-0.bpo.3-amd64 (x86_64)
      51. -------------------------------------
      52. Status: Before uninstall, this module version was ACTIVE on this kernel.
      53. vboxdrv.ko:
      54. - Uninstallation
      55. - Deleting from: /lib/modules/4.9.0-0.bpo.3-amd64/updates/
      56. - Original module
      57. - No original module was found for this module on this kernel.
      58. - Use the dkms install command to reinstall any previous module version.
      59. vboxnetadp.ko:
      60. - Uninstallation
      61. - Deleting from: /lib/modules/4.9.0-0.bpo.3-amd64/updates/
      62. - Original module
      63. - No original module was found for this module on this kernel.
      64. - Use the dkms install command to reinstall any previous module version.
      65. vboxnetflt.ko:
      66. - Uninstallation
      67. - Deleting from: /lib/modules/4.9.0-0.bpo.3-amd64/updates/
      68. - Original module
      69. - No original module was found for this module on this kernel.
      70. - Use the dkms install command to reinstall any previous module version.
      71. vboxpci.ko:
      72. - Uninstallation
      73. - Deleting from: /lib/modules/4.9.0-0.bpo.3-amd64/updates/
      74. - Original module
      75. - No original module was found for this module on this kernel.
      76. - Use the dkms install command to reinstall any previous module version.
      77. depmod...
      78. DKMS: uninstall completed.
      79. ------------------------------
      80. Deleting module version: 5.1.14
      81. completely from the DKMS tree.
      82. ------------------------------
      83. Done.
      84. Unpacking virtualbox-dkms (5.1.14-dfsg-1) over (5.1.14-dfsg-1) ...
      85. Setting up virtualbox-dkms (5.1.14-dfsg-1) ...
      86. Loading new virtualbox-5.1.14 DKMS files...
      87. Building for 4.9.0-0.bpo.2-amd64 4.9.0-0.bpo.3-amd64
      88. Building initial module for 4.9.0-0.bpo.2-amd64
      89. Done.
      90. vboxdrv:
      91. Running module version sanity check.
      92. - Original module
      93. - No original module exists within this kernel
      94. - Installation
      95. - Installing to /lib/modules/4.9.0-0.bpo.2-amd64/updates/
      96. vboxnetadp.ko:
      97. Running module version sanity check.
      98. - Original module
      99. - No original module exists within this kernel
      100. - Installation
      101. - Installing to /lib/modules/4.9.0-0.bpo.2-amd64/updates/
      102. vboxnetflt.ko:
      103. Running module version sanity check.
      104. - Original module
      105. - No original module exists within this kernel
      106. - Installation
      107. - Installing to /lib/modules/4.9.0-0.bpo.2-amd64/updates/
      108. vboxpci.ko:
      109. Running module version sanity check.
      110. - Original module
      111. - No original module exists within this kernel
      112. - Installation
      113. - Installing to /lib/modules/4.9.0-0.bpo.2-amd64/updates/
      114. depmod...
      115. DKMS: install completed.
      116. Building initial module for 4.9.0-0.bpo.3-amd64
      117. Done.
      118. vboxdrv:
      119. Running module version sanity check.
      120. - Original module
      121. - No original module exists within this kernel
      122. - Installation
      123. - Installing to /lib/modules/4.9.0-0.bpo.3-amd64/updates/
      124. vboxnetadp.ko:
      125. Running module version sanity check.
      126. - Original module
      127. - No original module exists within this kernel
      128. - Installation
      129. - Installing to /lib/modules/4.9.0-0.bpo.3-amd64/updates/
      130. vboxnetflt.ko:
      131. Running module version sanity check.
      132. - Original module
      133. - No original module exists within this kernel
      134. - Installation
      135. - Installing to /lib/modules/4.9.0-0.bpo.3-amd64/updates/
      136. vboxpci.ko:
      137. Running module version sanity check.
      138. - Original module
      139. - No original module exists within this kernel
      140. - Installation
      141. - Installing to /lib/modules/4.9.0-0.bpo.3-amd64/updates/
      142. depmod...
      143. DKMS: install completed.
      144. root@backup-nas:~#
      Display All
    • Users Online 1

      1 Guest