Cloudron Forum

@girish I came across this when I was doing some research on the issue.

"you can run your container in host mode and you will see the same networking that you see on the host, but there is no network isolation. When there is a bridge in between the packets from the container have to be natted and so one interface has to be chosen"

This explains why I didn't see the issue on my other systems since Guacamole is running in host mode there. I'll need to look at a different work around or create a seperate bridge and add the container to it.

@girish No route to host for anything on ENS4. Checked using the web terminal as requested.

.

Cloudron is setup in the typical manner with the public IP sitting on ENS3. Everything works as expected and no issues. I have a second interface, ENS4 which is connected to a number of servers internally. From the CLI I can reach everything just fine. When I deployed Guacamole I found it was unable to connect to any systems on ENS4. It would connect externally just fine. Is there something I can do to enable this? I imagine this is a pretty common use case for Guacamole and it's worked well for me in the past. Thanks in advance for any help.

This is my fourth time setting up Cloudron on a server and till now everything has gone well. Yesterday I sat down to do a generic install on a VM and I get this error.

echo "==> Installing node.js"
==> Installing node.js
mkdir -p /usr/local/node-10.15.1
curl -sL https://nodejs.org/dist/v10.15.1/node-v10.15.1-linux-x64.tar.gz | tar zxvf - --strip-components=1 -C /usr/local/node-10.15.1

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now

Tried manually installing node.js and I get the same error on a clean build. Has anybody else seen this? I've spent a few hours messing around with ubuntu and there doesn't seem to be a way around this error that I can find. Any help would be greatly appreciated.

Robert

You were right. "unbound" was failed. Turns out IPV6 was disabled which was causing "unbound" to fail and in turn causing the issues with resolving domain names in Nextcloud. This is a vanilla install of Ubuntu 16 LTS so I'm not sure what happened. I enabled IPV6 and rebooted and everything started working. Thanks for the tip.

When I log in to Nextcloud and look at the apps I noticed that only the official apps are present. I looked at the logs and saw that the Nextcloud docker image is unable to resolve Nextcloud and Github which is preventing the app store within Nextcloud from updating. Is this by design? If it isn't is there a recommended way to fix the issue that won't compromise security?