Hello everyone, While using the browser developer tools for debugging, I noticed that the time taken to establish a connection is excessively long, leading to very slow page load times. I have attached a screenshot of the “Timing” tab below:  Here are some detailed observations: Queued at: 29.38 seconds Started at: 29.41 seconds Initial connection time: Displays “CAUTION: request is not finished yet!” To better diagnose the issue, I have tried the following actions, but there has been no significant improvement: Checked the network connection to ensure it is stable. Verified the server performance to ensure it is not overloaded. Cleared the browser cache, restarted the browser, and tried using different browsers. Confirmed that the SSL certificate provided by Cloudflare is correctly configured and not expired. Despite these efforts, the problem persists. I suspect there might be other factors contributing to the excessive connection time. Has anyone in the community encountered a similar issue? Are there any additional suggestions or steps I can take to resolve this problem? Thank you very much!
What feature, service or problem is this related to?
Can’t seem to reproduce this at my end. This is what I get:
This might be a best case scenario, but I’ve tested from multiple locations with Chrome and FF and it seems pretty consistent.
I’d say that there’s something happening either at your local network or your ISP. Try changing your local computer DNS to Cloudflare’s 1.1.1.1, Google’s 8.8.8.8 or OpenDNS’s 208.67.222.222 and see if it makes any difference. If it does, then you’ll know that the ISP dns resolver, or whichever DNS you have set at your router does not perform well.
Alternatively you can also test this by installing Cloudflare WARP:
Thank you for your assistance and for looking into this matter. I’d like to clarify a few points:
In my region, DNS pollution is a severe issue, well-known to everyone. Initially, I thought this was the cause of the problem.
I tried using Cloudflare’s 1.1.1.1 DNS service.
Using curl -v, I was able to pinpoint the problem. Ultimately, I discovered it was a simple mistake on my part – I hadn’t opened the port for Nginx reverse proxy.
I apologize for any confusion caused. I was working on this issue late into the night and didn’t retract my previous message in time.
Thank you again for your understanding and support.
