question

MattRiches-7473 avatar image
0 Votes"
MattRiches-7473 asked SaiKishor-MSFT commented

My DNS has resolved, but my site won't serve

All of this is on Azure

have 2 vps behind a loadbalancer.

1 VPS is currently off to eliminate loadbalancer issues

loadbalancer has http and https (ports 80 and 443), both ports are mapped front end to back end.

on one vps I have added a letsencrypt cert (DNS verified) to a site.

pinging the domain name points to the LB so the domain has propogated

navigating to https://testdomain.com throws up an ERR_CONNECTION_TIMED_OUT

navigating to https://www.testdomain.com throws up an ERR_CONNECTION_TIMED_OUT

navigating to http://testdomain.com throws up an ERR_CONNECTION_TIMED_OUT, but inspecting the url it has somehow reverted to https://testdomain.com

before I deployed the site I was using a test domain. This test domain still serves the files so I know the site is fine.

I want to say that this is just propogation, but being as ping finds the site via its name, I don't believe that this is the case, unless ping uses a different dns to everything else.

So have I missed anything obvious to try here, or is this really just a propogation issue, and ping sitename is somehow working faster than the rest of the dns?

windows-server-iisazure-load-balancer
· 6
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@MattRicher-7794 According to your description, it is difficult for me to reproduce your problem. Can you tell me how to configure your loadbalancer?

0 Votes 0 ·

Apologies, It looks like the issue is with the load balancer. If I change my DNS to point direct to one of my servers, then it all works, http and https.
If I go back to the load balancer then only http works.

Load balancer has 2 Front end rules, http and https (ports 80 and 443)
Each Rule maps direct front to back end (so 80 -> 80 and 443 -> 443)

The Back End pool has both my servers in it.

Both Web servers associate with an NSG that allows 80 and 443 traffic to flow both ways.

Its certainly a configuration / understanding issue on my side, but I can't figure it out, and I am just going round in circles!

0 Votes 0 ·

@MattRiches-7473 It seems difficult to troubleshoot your problem, I suggest you open a support ticket for this, one of our engineers will help analyse the root cause.


0 Votes 0 ·
Show more comments

0 Answers