Cannot stop proxing through cloudflare my hostname

Community Support DNS
1

I cannot stop proxing through cloudflare my hostname: svr1.hasalat.com

My domain register is cloudflare
I turned off proxy in dns settings it’s dns only.
For ssl I’m using let’s encrypt.
I’m using 2083 port for cloudflare but if i change it doesn’t work, i accept port from hestia firewall because cloudflare, it doesn’t load my hestia panel. Except if i change again port to 2083.
It’s only work i mean show my server ip when i pause cloudflare but that’s not what i want, i only want my hostname show my server ip.

Now i don’t know it’s hestia problem or Cloudflare problem.

2

Hi @Saifullah,

I tested it and Cloudflare is no proxiying your domain:

❯ curl -IkL svr1.hasalat.com
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Mon, 01 Apr 2024 13:11:37 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Location: https://svr1.hasalat.com/

HTTP/2 200
server: nginx
date: Mon, 01 Apr 2024 13:11:38 GMT
content-type: text/html; charset=utf-8
content-length: 2564
last-modified: Wed, 27 Mar 2024 18:13:37 GMT
vary: Accept-Encoding
etag: "660461d1-a04"
strict-transport-security: max-age=31536000;
accept-ranges: bytes

❯ curl -IkL svr1.hasalat.com:2083
HTTP/1.1 302 Moved Temporarily
Server: nginx
Date: Mon, 01 Apr 2024 13:12:00 GMT
Content-Type: text/html
Content-Length: 138
Connection: close
Location: https://svr1.hasalat.com:2083/
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block

HTTP/2 302
server: nginx
date: Mon, 01 Apr 2024 13:12:01 GMT
content-type: text/html; charset=UTF-8
set-cookie: PHPSESSID=sjkvjopqlrtpaok4a9h7pi77fp; path=/; secure; HttpOnly
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
location: /login/
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block

HTTP/2 200
server: nginx
date: Mon, 01 Apr 2024 13:12:02 GMT
content-type: text/html; charset=UTF-8
vary: Accept-Encoding
set-cookie: PHPSESSID=qqfmlbmgmro71vmfhfsl9ftdu9; path=/; secure; HttpOnly
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block

And you are serving the Let’s Encrypt certificate on port 443:

❯ openssl s_client -connect svr1.hasalat.com:443 -servername svr1.hasalat.com 2>/dev/null </dev/null | openssl x509 -noout -issuer -dates -subject -ext subjectAltName | sed -E -e 's/^\s*//' -e '/^X509v.*/d'
issuer=C = US, O = Let's Encrypt, CN = R3
notBefore=Mar 27 17:21:20 2024 GMT
notAfter=Jun 25 17:21:19 2024 GMT
subject=CN = svr1.hasalat.com
DNS:svr1.hasalat.com

And port 2083:

❯ openssl s_client -connect svr1.hasalat.com:2083 -servername svr1.hasalat.com 2>/dev/null </dev/null | openssl x509 -noout -issuer -dates -subject -ext subjectAltName | sed -E -e 's/^\s*//' -e '/^X509v.*/d'
issuer=C = US, O = Let's Encrypt, CN = R3
notBefore=Mar 27 17:21:20 2024 GMT
notAfter=Jun 25 17:21:19 2024 GMT
subject=CN = svr1.hasalat.com
DNS:svr1.hasalat.com

Change your browser or try to connect using the private/incognito mode in your browser. Also, maybe your os is still caching the old dns records for your domain.

3

Because I Paused my cloudflare, now I resume my cloudflare same port 2083, also my hostname dns only in cloudflare. I posted after 8 hours wait.

4

Sorry but that is not what you want?

Maybe I don’t understand what you want to do. But now that is is using Cloudflare as proxy. I can connect to your server using https://sr1.hasalat.com or https://svr1.hasalat.com:2083, the same way as before that it was not using Cloudflare as proxy.

5

Actually I don’t want to proxy this domain through cloudflare, but problem is it is proxy my domain (svr1.hasalat.com) even though I turned off proxy from cloudflare DNS setting I mean no orange colour,
I only face this problem in this subdomen not other subdomain.

6

It wasn’t when I tested it the first time and that’s the reason I don’t understand the issue.

7

Because that time I completely paused cloudflare not only this subdomain

Screenshot_20240401_173216_Chrome
Screenshot_20240401_173216_Chrome720×485 30.3 KB

8

If Cloudflare doesn’t work as expected, then you should ask to Cloudflare’s support team.

9

Pop over to the Cloudflare Community. It is usually faster than Cloudflare support and it is not dependent on having a paid Cloudflare plan. It is an official Cloudflare site and tends to be quite active.