How to Install Oracle VirtualBox On Ubuntu 18.04 LTS Headless Server

Install Oracle VirtualBox On Ubuntu 18.04

15 Responses

  1. Gianni Franceschinis says:

    Hello,
    This is a great guide.
    Thanks so much!!!

  2. Daryl Lee says:

    Nice work. But when I browse to phpvirtualbox and log in, I get a failure to connect to “http://127.0.0.1:18083/”. Any idea what that’s all about? The userid/pwd is correct

  3. Chuck Razalas says:

    Great tutorial but like every other time I have tried I get the same issue about failure to connect to “http://127.0.0.1:18083/” and I have changed the IP and I have changed the usernames and I have made sure to allow the port 18083 and no matter what I do it NEVER works. I have tried on CentOS 7 and now Ubuntu 16.04 LTS and same issue every single time no matter what tutorial I try. I followed this guide to a “T” and same as all the rest. Why is this so complicated and why does it NEVER work?

    • Chuck Razalas says:

      Ok never mind. I finally got it to work. I didn’t change the 127.0.0.1 this time and most importantly, I made sure I did all the steps with the correct User this time. So overall your tutorial was 100% dead on I just didn’t follow the users clause so that was on me. Thanks so much for providing a tutorial that was easy to follow and that actually worked for me.

  4. Chuck Razalas says:

    Quick question SK. Ok so I have everything working perfectly and I did end up having to change the IP to my actual server IP after all. I can login to the PHP Virtual box login and I can see the VM I created and it’s running and all is well except one problem. I can only see it in the console screen and I cannot access the VM from a web browser. My VM is Univention Corporate Server and again I can see it running in the Console but I need to access the Univention Portal from a web browser and not the Virtual Box console. How can I see a VM I create from the outside? No matter what I do I just can’t access it. Thanks in advance.

    • SK says:

      If both systems (VM and the host) are in the same network, you can access it from the web browser. Check the network settings of your VM and make sure you have selected the “Bridged network” option. https://uploads.disquscdn.com/images/c7dfe4ff585e8150a3dd24b0bcf1fd317cc89dd4af5d06cca3f8b74e4689a4c3.png

      • Chuck Razalas says:

        One problem with that SK. My hosting company 1&1 doesn’t allow Bridging, go figure right? So what I have tried is using adapter 1 as Host Only and adapter 2 as Nat but no luck. I even tried port forwarding from my server ip to 192.168.56.1 and still no luck. Also tried adding the following command in IP Tables: iptables -t nat -A PREROUTING -p tcp -d my.server.ip –dport 80 -j DNAT –to-destination 192.168.56.1:80 and also no luck. I have tried with Ubuntu 16.04 LTS and now trying again with CentOS 7 as the base. The VirtualBox install process goes off without a hitch. I am then trying to install Univention Corporate Server as a VM in VirtualBox and it installs but always says it could not set a default route and makes me manually enter my netwwork details. I input my server ip, then the submask comes up and it’s different than what the host server submask actually is. I change it to what it is on the actual host server, then when Gateway comes up I try what my hosting company says the host Gateway IP is and always get an error saying it’s unreachable. I then try again with the auto defaults that pop up and again nothing. I’m so frustrated with this at this point. Any other ideas?

        • SK says:

          Hello Chuck, enabling bridge network on VM has nothing to do with hosting provider as far as I know. Because, you’re enabling it on your VM, not in the host system. The VM (The univention server) should be reachable in-order to access it from a remote system. I am not a expert in networking. I don’t know how to do it. My apologies.

  5. Lucien Bunel says:

    Hello !
    I just switched from Ubuntu server 16.04 LTS to Ubuntu server 18.04 LTS
    and I lost my PhPvirtualbox … so I did your tutorial like I did for 16.04, but the Apache2 does not want to start?
    root @ proliant: ~ # journalctl -xe
    – Support: http://www.ubuntu.com/support

    – The vboxdrv.service unit (unit) has completed its startup, with the RESU result
    Aug 30 10:58:40 proliant systemd [1]: Starting The Apache HTTP Server …
    – Subject: The unit (unit) apache2.service started to start
    – Defined-By: systemd
    – Support: http://www.ubuntu.com/support

    – The unit (unit) apache2.service started to start.
    Aug 30 10:58:40 proliant apachectl [5348]: (98) Address already in use: AH00072:
    Aug 30 10:58:40 proliant apachectl [5348]: (98) Address already in use: AH00072:
    Aug 30 10:58:40 proliant apachectl [5348]: no listening sockets available, shutt
    Aug 30 10:58:40 proliant apachectl [5348]: AH00015: Unable to open logs
    Aug 30 10:58:40 proliant apachectl [5348]: Action ‘start’ failed.
    Aug 30 10:58:40 proliant apachectl [5348]: The Apache error log
    Aug 30 10:58:40 proliant systemd [1]: apache2.service: Control process exited, c
    Aug 30 10:58:40 proliant systemd [1]: apache2.service: Failed with result ‘exit-
    Aug 30 10:58:40 proliant systemd [1]: Failed to start The Apache HTTP Server.
    – Subject: The unit (unit) apache2.service failed
    – Defined-By: systemd
    – Support: http://www.ubuntu.com/support

    – The unit (unit) apache2.service failed, with result RESULT.
    proliant root @: ~ #
    do you have an idea ?
    Thanks part ahead
    cordially

  6. Lucien Bunel says:

    hello it works now after installing
    soap extension

  7. Tanvir says:

    Thank you .
    it worked fine

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.