[NCP, Virtualbox, Ports] Can't reach Nextcloud in a Virtualbox VM (Debian)

ℹ️ Support
1

Hi community,

I run Nextcloud 27.1.3 on a dedicated machine with Debian 12 and PHP 8.2. I installed everything with the NextcloudPi install script from [GitHub - nextcloud/nextcloudpi: 📦 Build code for NextcloudPi: Raspberry Pi, Odroid, Rock64, Docker, curl installer...] (GitHub - nextcloud/nextcloudpi: 📦 Build code for NextcloudPi: Raspberry Pi, Odroid, Rock64, Docker, curl installer...) on Debian 11 and moved over to Debian 12.
I wanted to move NextcloudPi to a VM. So I installed Debian 11 on a VM in Virtualbox and ran the above mentioned install script. I was able to restore a NextcloudPi backup from my host machine and everything looks good except one thing. I can’t reach my instance inside the VM.
The Network interface for my VM is bridged and the VM appears in my network with a DHCP assigned IP. I’m able to SSH and can reach the Nextcloud WebUI via local IP of the VM.
I have a DynDNS setup which I used to reach my Nextcloud instance on the host from outside my network.

Now the point: if I change the port-forwarding in my router to the IP of the VM I can’t reach it via my DynDNS address. Seems like it still tries to open Nextcloud on my host computer. I did “systemctl stop apache2” on the host but it didn’t change a thing. If I change port-forwarding back to my host computer I can reach the host’s Nextcloud UI (after restarting apache2).

Do I have to stop more services on the host that could catch the access to the ports 443 and 80?

I don’t know how to get the ports forwarded correctly.

2

In fact I’m an idiot. After two days I figured out that I had setup a DNS rewrite in my AdGuard Ad Blocker some (long) time ago to troubleshoot connection problems and didn’t remove it afterwards. So any request was always sent to my host although the ports were open for my VM.
Now everything works fine again.

3

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.