Error 523 and I don't know what I'm doing

DNS & Network
#1

I’m hosting RDWeb in IIS. The short domain name is hosted by iwantmyname, w/ nameservers set to Cloudflare. In my new Cloudflare account, I have the following entries in DNS:

A remote 70.89.84.93
CNAME cooks.ac custom.droplr. com
CNAME www custom.droplr. com
TXT record for SSL certificate

When I browse to https:// remote.cooks.ac/, I get the Windows Server IIS landing page, so that’s working.

When I browse to https:// remote.cooks.ac/RDWeb/Pages/en-US/Default.aspx, I get a Cloudflare Error 523 - origin is unreachable.

I’m sure I’ve made some mistake setting this up, because this is not my area of expertise. Please help! Thanks in advance!

#2

Also… when I ping remote.cooks.ac, the reply comes from 104.28.28.192 (cloudflare), not my web server that it’s supposed to be forwarding to

#3

The machine at the IP address you configured simply does not seem to respond. You need to check your server in that case.

#4

Thanks for responding…

But it does. I can substitute the IP address for the A name and access it with no problem. https:// 70.89.84.93/RDWeb/Pages/en-US/Default.aspx

#5

Alright, on HTTPS it does.

The problem in your case seems to be that you redirect to HTTP. What is your encryption mode on Cloudflare?

#6

I have tried both “off” and “flexible” and I think I tried “full” last night as well

#7

You should have at least Full, better “Full strict”. Only the latter is really secure.

Which one is it right now?

#8

Just changed it from “off” back to “full.”

#9

That explains it.

#10

I’m not positive, but I think it started out on “full” last night when I set it up and then I changed it. Do you think that will resolve the issue?

#11

Well, right now it loads on HTTPS via Cloudflare.

Again, “Full strict” would be a better choice and you should also enable “Always use HTTPS” as HTTP requests will still fail right now.

#12

It still doesn’t load for me… you’re saying it’s loading for you?

I re-enabled “always use https,” I disabled it last night

#13

It is working here -> sitemeer.com/#https://remote.cooks.ac/

What do these commands return for you?

ping remote.cooks.ac
nslookup remote.cooks.ac
#14

I was typing in https: in the browser and still not getting it, but after re-enabling “always use https”, it seems to work!

#15

remote.cooks.ac was working but not remote.cooks.ac/rdweb

#16

ping remote.cooks.ac returns 104.28.29.192, strangely.

C:\Users\Joel Becker>nslookup remote.cooks.ac
Server: dns.google
Address: 8.8.8.8

Non-authoritative answer:
Name: remote.cooks.ac
Addresses: 2606:4700:3031::681c:1cc0
2606:4700:3033::681c:1dc0
104.28.29.192
104.28.28.192

C:\Users\Joel Becker>

#17

That seems to be working too

sitemeer.com/#https://remote.cooks.ac/RDWeb/

#18

That the correct address. So I guess it is working now?

#19

But in any case it is working now. Thanks so much for your help!!

#20

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.