The problem is https: calls to the server fail. with the browser error page HTTP: or just the ip or domain this takes one to Nextcloud. It happens for domains and the IP address.
This is the content of that page.
Nextcloud
This application requires JavaScript for correct operation. Please enable JavaScript and reload the page.
Did you install Virtualmin on an existing server with sites already on it? It is meant to be installed on top of a fresh, clean OS install.
Where is the server located? With an ISP or some other provider? Home network? I have no clue where the Nextcloud is coming from but I don’t think it would be Virtualmin.
You mention https. Are the proper certs installed?
It on a nat router, on hard metal and completely new install OS and vitrualmin. enom is my domain supplier. I just went to them to see if they could give me some insight. Nothing of any value. They say it is the the DNS setup on wirtualadmin.
I just searched Vitualamin for Nextcloud and it seems that it is an application scheam the they promote. Is this where the redirection is coming from? Anyone had this issue where you are blocked from accessing https: and forced to the addvertizing for NextCloud. Where is this happing in the code of Virtuaadin to change this behaviour.
computersystemconsulting.ca
Where in Virtualmin is the default home page found? so I can check it for errors. It doesn’t matter what domain or IP you go to it returns the same page.
Networking wise I can’t seem to get there via icmp. Ping or traceroute.
My get ip in the browser does show 209.121.123.102.
I can get there via port 22 but not 80 or 443. Does your provider have a firewall?
mit@~:traceroute -p 22 209.121.123.102
traceroute to 209.121.123.102 (209.121.123.102), 30 hops max, 60 byte packets
1 _gateway (192.168.0.1) 0.239 ms 0.237 ms 0.282 ms
2 142-254-157-021.inf.spectrum.com (142.254.157.21) 7.944 ms 13.904 ms 13.795 ms
3 * * *
4 lag-25.pltsohae01r.netops.charter.com (24.33.103.230) 17.067 ms 15.452 ms 15.433 ms
5 lag-25.rcr01clmkohpe.netops.charter.com (65.29.1.28) 19.356 ms lag-30.rcr01clmkohpe.netops.charter.com (65.29.1.40) 19.358 ms 19.365 ms
6 lag-1-100.rpr01cleyohdh.netops.charter.com (65.29.33.89) 25.273 ms 19.636 ms 26.455 ms
7 * * *
8 4.69.219.210 (4.69.219.210) 78.546 ms 78.500 ms 78.548 ms
9 * * *
10 * * *
11 * 209.121.123.102 (209.121.123.102) 95.664 ms *
12 * * *
13 * * *^C
mit@~:traceroute -p 80 209.121.123.102
traceroute to 209.121.123.102 (209.121.123.102), 30 hops max, 60 byte packets
1 _gateway (192.168.0.1) 0.258 ms 0.253 ms 0.315 ms
2 142-254-157-021.inf.spectrum.com (142.254.157.21) 9.358 ms 15.322 ms 15.172 ms
3 * * *
4 lag-25.pltsohae01r.netops.charter.com (24.33.103.230) 16.964 ms 16.838 ms 16.794 ms
5 lag-25.rcr01clmkohpe.netops.charter.com (65.29.1.28) 20.722 ms lag-30.rcr01clmkohpe.netops.charter.com (65.29.1.40) 20.673 ms lag-25.rcr01clmkohpe.netops.charter.com (65.29.1.28) 20.682 ms
6 lag-1-100.rpr01cleyohdh.netops.charter.com (65.29.33.89) 27.033 ms 22.923 ms 26.772 ms
7 * * *
8 4.69.219.210 (4.69.219.210) 80.519 ms 80.388 ms 80.344 ms
9 * * *
10 * * *
11 * * *
mit@~:traceroute -p 443 209.121.123.102
traceroute to 209.121.123.102 (209.121.123.102), 30 hops max, 60 byte packets
1 _gateway (192.168.0.1) 0.246 ms 0.229 ms 0.269 ms
2 142-254-157-021.inf.spectrum.com (142.254.157.21) 9.051 ms 16.539 ms 16.402 ms
3 * * *
4 lag-25.pltsohae01r.netops.charter.com (24.33.103.230) 17.957 ms 17.874 ms 17.775 ms
5 lag-30.rcr01clmkohpe.netops.charter.com (65.29.1.40) 21.766 ms lag-25.rcr01clmkohpe.netops.charter.com (65.29.1.28) 21.772 ms 21.759 ms
6 lag-1-100.rpr01cleyohdh.netops.charter.com (65.29.33.89) 27.648 ms 21.960 ms 25.835 ms
7 * * *
8 4.69.219.210 (4.69.219.210) 82.472 ms 82.419 ms 82.451 ms
9 4.35.244.230 (4.35.244.230) 91.451 ms 91.468 ms 91.464 ms
10 * * *
11 * * *
12 * * *
13 * * *
I have dropped nat and gone to a direct pass-through. so the redirect is no longer happening. though DNS issues are not the major problem.
Thanks for the help.
Shanta