Where is the DNS section. You'll find one of those is proxied and the other is not
Please see the Cloudflare docs
5 Likes
IP 51.222.9.201 is not a Cloudflare CDN IP:
ARIN Whois/RDAP - American Registry for Internet Numbers
5 Likes
justlave.com = CF CDN IP
webb24h.com = CF CDN IP
server.justlave.com = CF CDN IP
server.webb24h.com = OVH IP [NOT a CF CDN IP]
2 Likes
Yes, it says "PROXIED".
Check your other domain it won't say that
4 Likes
Yet, nslookup shows other IPs [and works for you]:
Name: server.justlave.com
Addresses: 2606:4700:3036::6815:60d <<< CF
2606:4700:3034::ac43:8626 <<< CF
172.67.134.38 <<< CF
104.21.6.13 <<< CF
While:
Shows the SAME IP [no CF IP in DNS]:
Name: server.webb24h.com
Address: 51.222.9.201 <<< NOT CF
2 Likes
In layman terms, how do I fix this? Please just tell the solution. I've been stuck here for 48 hours straight.
Yeah, this is one for Cloudflare support. Both those domains should be using the CDN but they are not.
Also see this DNS Viz report. It shows very cleary the DNS records are not as they should be:
https://dnsviz.net/d/server.justlave.com/dnssec/
https://dnsviz.net/d/server.webb24h.com/dnssec/
That said, oddly the one that "works" is the one that should be proxied but is not.
4 Likes
Not ODD to me.
The port required is neither 80 nor 443, so it can't [easily] be proxied.
So, it shouldn't be proxied [behind the CDN].
Neither one of the "server" FQDNs should be proxied.
3 Likes
No, I get that. What is odd is that the Cloudflare DNS panel says it is proxied but it is not. So, it works because it does not use the CDN.
Maybe the Cloudflare Community has seen that before but I have not.
The CDN does not support the odd ports being used by this app so cannot work. We both agree on that.
5 Likes
Turn off "Proxied" status. Your working domain isn't using it even though it is configured as such.
3 Likes
Yes, the Cloudflare settings are ODD.
And more surprising is that both domains use the same two CF DNS servers:
dion.ns.cloudflare.com
athena.ns.cloudflare.com
Why the same two servers give these two FQDNs two different proxied DNS replies is very ODD.
3 Likes
Looks like your DNS for both are now NOT proxied. How did you fix that? Just by disabling proxied status for the one?
nslookup server.justlave.com
Address: 51.79.86.136
nslookup server.webb24h.com
Address: 51.222.9.201
3 Likes
Yes, I turned everything off and now we are GO!! Dude, I've been SWEATING dogs and cats with all that heavy breathing down my NECK! Marketing starts tomorrow and now boom; I'm meeting deadline. THANK YOU!
4 Likes
You are welcome.
When time permits you should ask Cloudflare (Community or support) why setting Proxied does not actually proxy and instead has your origin server IP in the public DNS.
Very weird
3 Likes
Yeah, free Cloudflare support for commercial projects ! 
3 Likes
Mike, our company will certainly donate to letsencrypt but it's a false alarm. If you visit justlave.com/app and open the console, yes I'm able to poll https://server.justlave.com:3008/socket.io/?EIO=4&transport=polling&t=ORXlzcC and access the socket https://server.justlave.com:3008/socket.io/socket.io.js?_=1678824065831 but now all the GET are blocked! Still not able to connect to the server.
e
It's polling just fine here.
Maybe check the console for the reason why it's not working for you. But I doubt it has anything to do with something that's within the scope of this Community.
3 Likes