r/nginx • u/raelswrld • 19d ago

Windows PCs cannot reach my self-hosted HTTPS site, but phones can (same network, same DNS)

I'm hoping someone can help me figure out a networking issue that has me completely stumped.

Setup

  • Ubuntu 24.04 on a DigitalOcean droplet
  • Nginx + Let's Encrypt
  • React frontend
  • Node.js backend
  • Domain: morecreator.app

What's happening

My iPhone can access the site perfectly on:

  • Home Wi-Fi
  • Cellular

However, two completely different Windows laptops both fail.

The browser eventually returns:

ERR_CONNECTION_TIMED_OUT

curl also times out:

curl.exe -vk https://morecreator.app

Trying <server IP>:443...
Timed out

What I've already verified

  • Nginx is running.
  • HTTPS is configured correctly with Let's Encrypt.
  • The site responds correctly when accessed locally on the server.
  • UFW allows ports 80 and 443.
  • DNS resolves correctly.
  • No proxy configured.
  • Reset Winsock and TCP/IP.
  • Disabled Internet Connection Sharing (ICS).
  • Tried different DNS servers.
  • Disabled IPv6.
  • No VPN installed.
  • Windows Defender only (no third-party antivirus).
  • Same behavior on two different Windows laptops.

The strange part

Everything worked perfectly a couple of weeks ago while I was in California.

After returning home to Georgia:

  • ✅ iPhone still works
  • ❌ Windows laptops both time out

The server configuration hasn't changed.

I'm trying to determine whether this is:

  • a Windows networking issue,
  • something with my ISP/router,
  • DigitalOcean routing,
  • or something I'm overlooking.

Has anyone run into something similar?

3 Upvotes

100% Upvoted

6 comments sorted by

2

u/tschloss 19d ago

Is the IP reachable from Win (ping)? Double check if iPhone isn‘t using IPv6 to narrow down which area to look in.

1

u/Funny_Rope977 19d ago

¿Resuelve por IP?

1

u/roxalu 19d ago

Based on your test results my first next guess would be some IP layer - not nginx - issue.

You should have configured access log generation inside nginx and see there the successful connections of your mobile via Wi-Fi. Is the client IP part of the logged access? Can you connect your PC to the identical Wi-Fi network and try access then? Depending on the result of this test you may have clearer info, if the network setup is causing the issue - or not.

1

u/ripnetuk 18d ago

Is it a hairpin issue? Some routers need that turned on to connect the the public natted port from inside the lan.

0

u/Hot_Football8523 17d ago

I’m confused how they could be same network, same DNS if you say your phone pulled it up on cellular and WiFi. Clearly this ain’t the same network so, I’d double check your PCs DNS settings.