@Hari said in Virtualmin Setup DigitalOcean:
is CF preventing port access?
Yes, but not at the port level. The reason for this is that CF is handling the DNS side of things so when you try to access using your browser, it’s going to resolve to the address in DNS that resolves to CF.
There’s a number of choices depending on your scenario.
The most common approach is to create a page page rule that bypass the CF proxy and allows direct access. The issue here of course is that the free plan on CF only allows a small amount of ports, so you’d need to change the VirtualMin listener port to something else dish as 8443 which is routable in the free plan. You can change the VirtualMin port as explained here
Another approach is to use a management station that has access, and then create a HOSTS file entry that contains a mapping from hostname to IP that overrides the DNS but only for your machine. The preferred order of resolution means host files are read before DNS, and if a match is found then that is used and DNS is ignored.
The drawback with this is that you’d need to make this change on every single machine where you wanted to gain access. Not insurmountable, but quite clunky if you frequently used multiple machine or your phone to get access.
The last method, which is by far optimum is to use a vacant or unused domain to access VirtualMin. I do this myself, and it just means that this domain has no other purpose other than to manage the VPS. In other words, it’s not used for web hosting etc. You can still host the DNS in CF, but you’d then need to ensure the proxy is disabled.