This site can’t be reached, connection refused

Help
,
1

I’ve purchased a domain from https://qservers.ng udalice.com.ng and changed it’s nameservers to vercel’s nameserver on the 26th of Feb and till now i keep getting this error in the image below

image
image1919×749 28.5 KB

URL: https://udalice-integrated.vercel.app
framework: NextJs
environment: production

2

The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points.

You can also use v0 to narrow down the possibilities.

3

Hello, We have seen government of Nigeria and ISP often blocks the requests. Have you tried contacting your ISP?

1 Like
4

Yes i have and i have they have also assisted in pointing the DNS to Vercel servers on their end and have confirmed to me that they didn’t block requests. They suggested i reach out to Vercel support since the DNS is configured properly. I have pointed domains i bought from them to my Render static sites with no problem at all, and decided to try Vercel since the project is a NextJs project.

1 Like
5

Can you run following command and share us the output:

curl -s https://raw.githubusercontent.com/vercel-support/vercel-connect-debug/main/vercel-debug.sh | bash | tee vercel-debug.txt
6

Done here’s the vercel-debug.txt file content:

Domain to test (e.g. example.com):
┌───────────────────────────────────────
├─────── STARTING
│
│ Domain to test: udalice.com.ng
│ Timestamp (UTC): Wed, Mar 12, 2025 8:08:17 PM
| Timestamp (Local): Wed, Mar 12, 2025 9:08:17 PM
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── IP Information

{
“ip”: “102.89.23.24”,
“city”: “Lagos”,
“region”: “Lagos”,
“country”: “NG”,
“loc”: “6.4541,3.3947”,
“org”: “AS29465 MTN NIGERIA Communication limited”,
“timezone”: “Africa/Lagos”,
“readme”: “IP Address data API - IPinfo.io”
}
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.21

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 66.33.60.33

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 66.33.60.34

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 66.33.60.35

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 66.33.60.65

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 66.33.60.66

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 66.33.60.67

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 66.33.60.129

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 66.33.60.130

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 66.33.60.193

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 66.33.60.194

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.9

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.22

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.61

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.93

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.98

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.123

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.142

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.164

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.241

Access denied. Option -c requires administrative privileges.

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig udalice.com.ng

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig udalice.com.ng via 8.8.8.8

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig udalice.com.ng via trace

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Output of udalice.com.ng

  • processing: https://udalice.com.ng
  • Trying 76.76.21.21:443…
  • connect to 76.76.21.21 port 443 failed: Connection refused
  • Failed to connect to udalice.com.ng port 443 after 2262 ms: Couldn’t connect to server
  • Closing connection

└───────────────────────────────────────

┌───────────────────────────────────────
│ Time elapsed: 5 seconds
│
├─────── FINISHED
└───────────────────────────────────────

File can be found at /c/Users/HP/Desktop/work/web/vercel-debug.txt

7

The site is working for me. It must be your DNS, ISP, region, or something.
Also, I should note — the site redirects to www.udalice.com.ng by default. Not sure if that is of importance to you…

8

Yeah the redirection is expected which you can configure from Domain Settings in your project. Also the curl result is incomplete as most of the comment couldn’t run in your system. Are you on corporate restricted computer of something? Regardless, your DNS isn’t allowing to connect to Vercel server:


processing: https://udalice.com.ng
Trying 76.76.21.21:443…
connect to 76.76.21.21 port 443 failed: Connection refused
Failed to connect to udalice.com.ng port 443 after 2262 ms: Couldn’t connect to server
Closing connection```
1 Like
9

Ok how do i stop the redirect to www.udalice.com.ng at least, maybe that might improve the experience.

10

You should be able to delete www domain from vercel dashboard > Project > Domains section.

1 Like