I have set up an ubuntu server VM and want to install nextcloud on it, did that, so now I need to configure. I want to access it from the host of the VM, as it is just for testing purposes.
The installer hints at " *Set up your domain correctly to point to your home network"
Since I don’t have a domain registered, can I do that with an IP only? And if so…how?
Thanks in advance!
Edit: Additional info: I got no access to the router etc. if I need to open ports. It all has to run within this physical machine.
You must setup your Virtualbox Network to attach a Bridged Adapter:
Bridged: Not usually default, puts the Guest machine on the same network as the Host Router and Host machine.
You can now use the Virtualbox console to find out which IP address the VM has been assigned by the network:
ip address show
That IP address is now exposed to your local network, including your host. Your Nextcloud server can be reached under that address. You can even ssh into it from a Windows host with MobaXterm, PuTTy or winSCP, which makes life a lot easier.
I use such Virtualbox VM’s myself (but no AIO so far).
If I want/need SSL functionality I use self signed certificates and bypass the browser warnings. Perfectly adequate for testing purposes.
Under the assumption #2 or #3 would work:
Which webserver is installed by AIO? On which path? I tried to look for apache but couldn’t find anything.
And the very stupid question: Do I need to register an internet domain for making these things work? I was at first under the impression I could circumvent that.
Btw, I just forgot to mention that the AIO-VM does not support being installed behind a reverse proxy so you would need to create your own VM and follow the steps that I’ve linked above in order to install AIO in there.
This! However, if you don’t have full control over your device or network, like e.g. on corporate devices and / or in a corporate network, this might not work.
if you cannot use Bridge Mode for whatever reason, please read this: Chapter 6. Virtual Networking , especially section 6.3.1 Configuring Port Forwarding with NAT seems to be relevant for your usecase:
As the virtual machine is connected to a private network internal to Oracle VM VirtualBox and invisible to the host, network services on the guest are not accessible to the host machine or to other computers on the same network. However, like a physical router, Oracle VM VirtualBox can make selected services available to the world outside the guest through port forwarding. This means that Oracle VM VirtualBox listens to certain ports on the host and resends all packets which arrive there to the guest, on the same or a different port.