Why does the domain not work in the global network?

T

Toster1242021-06-06 15:59:36

Domain Name System

Toster124, 2021-06-06 15:59:36

There is a home server with a fixed ip on which a site with apache is raised. The domain stopped opening outside the local area with a Request Timeout error. By ip everything works. nslookup returns ip.
Domain ladurbo.tk

Reply

Answer the question

In order to leave comments, you need to log in

2 answer(s)

D

Dmitry, 2021-06-06
@Toster124

It responds over http, but not over https. Check the settings of your Apache (well, either the provider closed the 443rd port).

➜  ~ curl -v ladurbo.tk
*   Trying 85.21.240.124:80...
* TCP_NODELAY set
* Connected to ladurbo.tk (85.21.240.124) port 80 (#0)
> GET / HTTP/1.1
> Host: ladurbo.tk
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
< Date: Sun, 06 Jun 2021 14:20:59 GMT
< Server: Apache/2.4.41 (Ubuntu)
< Location: https://ladurbo.tk/
< Content-Length: 303
< Content-Type: text/html; charset=iso-8859-1
<
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="https://ladurbo.tk/">here</a>.</p>
<hr>
<address>Apache/2.4.41 (Ubuntu) Server at ladurbo.tk Port 80</address>
</body></html>
* Connection #0 to host ladurbo.tk left intact
➜  ~ curl -v https://ladurbo.tk
*   Trying 85.21.240.124:443...
* TCP_NODELAY set

G

gd1xza, 2021-06-06
@gd1xza

the reason can be any.
-ip is fixed but gray
-dns cache has not been updated yet
request timeout means that the connection to the address failed