Can't reach setup IP
On a fresh install I'm having trouble accessing the IP to continue the setup. It's not an issue with certificates. When I try accessing the IP from a windows machine and run diagnostics it states that the IP is online but not responding to connection attempts.
Message given: "The remote computer isn’t responding to connections on port 443, possibly due to firewall or security policy settings, or because it might be temporarily unavailable."
I have tried this from two computers on my network, one without firewall and one with windows firewall. Is this a router issue? And how do I fix it?
When entering my router I don't see my virtualized linux running cloudron on connected devices. I have tried to turn off the router firewall without success.
My linux skills are limited.
My setup is:
Ubuntu 20.04.03 LTS desktop where I have cloudron running virtualized with VMM on Ubuntu 20.04.03 LTS server on a fresh install. I think setup ran smoothly.
Another windows machine on my network also trying to access.
@ascua Make sure the firewall that the server is behind is allowing the traffic. what ISP / VPS are you using?
@Ascua From german Ubuntu wiki: No network despite the "default" setting in VMM
If the virtual machine has no network connection, it may be because the virtual interface used is vnet0not configured correctly by NetworkManager. This can be easily remedied by adding the following line to the / etc / network / interfaces file :
iface vnet0 inet manual
@ascua As a first step, you can check if cloudron setup did succeed properly in the Cloudron VM.
systemctl status nginxand
systemctl status boxshould say Running/Active. After that, you can also do
curl -k https://localhost. It should print some html.
Thanks for the input.
@girish All your commands show green, and I am able to for example ping websites.
However I am guessing that not setting up bridging before setting up the vm is the issue. I will look further and read into how to do it correctly tomorrow. Any tips or references appreciated. Right now I'm running network source: "virtual network 'default' : NAT and Device "virtio".
@murgero Ive tried with all firewalls off. The usecase here is to migrate a digital ocean VPS to instead run out of my home. I have a subscription.
@DigitEgal im guessing this is not relevant given that I have internet access from the VM?
@ascua If the new instance is in your house then you need to port-forward (or if your router/modem support - DMZ (AKA 1:1 NAT) ) the server.
I remember I had a problem connecting to a modem because it overheated because it was over a radiator.