Eu configurei o servidor web apache no Ubuntu 16.04, apresentado na Internet usando o dyndns com no-ip.com. A porta 80 é redirecionada automaticamente para a porta 443, o certificado vem de Vamos criptografar. Isso funciona bem para mim na minha própria rede, também fora da minha rede aqui na Tailândia, mas se eu tentar acessar da Europa, recebo um erro. Para testes, fiz o seguinte: De um servidor localizado na Alemanha eu testo usando wget, aqui está a saída do meu teste:
wget -d -v https://mydomain.ddns.net
Setting --verbose (verbose) to 1
DEBUG output created by Wget 1.15 on linux-gnu.
URI encoding = ‘UTF-8’
--2017-11-24 15:46:28-- https://mydomain.ddns.net/
Resolving mydomain.ddns.net (mydomain.ddns.net)... 110.78.XXX.XXX
Caching mydomain.ddns.net => 110.78.XXX.XXX
Connecting to mydomain.ddns.net (mydomain.ddns.net)|110.78.XXX.XXX|:443...
Closed fd 3
failed: No route to host.
Releasing 0x00000000021fa060 (new refcount 1).
wget -d -v mydomain.ddns.net
Setting --verbose (verbose) to 1
DEBUG output created by Wget 1.15 on linux-gnu.
URI encoding = ‘UTF-8’
--2017-11-24 15:50:29-- http://mydomain.ddns.net/
Resolving mydomain.ddns.net (mydomain.ddns.net)... 110.78.XXX.XXX
Caching mydomain.ddns.net => 110.78.XXX.XXX
Connecting to mydomain.ddns.net (mydomain.ddns.net)|110.78.XXX.XXX|:80...
connected.
Created socket 3.
Releasing 0x000000000195b9e0 (new refcount 1).
---request begin---
GET / HTTP/1.1
User-Agent: Wget/1.15 (linux-gnu)
Accept: */*
Host: mydomain.ddns.net
Connection: Keep-Alive
---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 301 Moved Permanently
Date: Fri, 24 Nov 2017 14:50:29 GMT
Server: Apache/2.4.18 (Ubuntu)
Location: https://mydomain.ddns.net/
Content-Length: 319
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1
---response end---
301 Moved Permanently
Registered socket 3 for persistent reuse.
URI content encoding = ‘iso-8859-1’
Location: https://mydomain.ddns.net/ [following]
Skipping 319 bytes of body: [<!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://mydomain.ddns.net/">here</a>.</p>
<hr>
<address>Apache/2.4.18 (Ubuntu) Server at mydomain.ddns.net Port 80</address>
</body></html>
] done.
URI content encoding = None
--2017-11-24 15:50:29-- https://mydomain.ddns.net/
Found mydomain.ddns.net in host_name_addresses_map (0x195b9e0)
Connecting to mydomain.ddns.net (mydomain.ddns.net)|110.78.XXX.XXX|:443... Closed fd 4
failed: Connection timed out.
Releasing 0x000000000195b9e0 (new refcount 1).
Releasing 0x000000000195b9e0 (new refcount 0).
Deleting unused 0x000000000195b9e0.
Resolving mydomain.ddns.net (mydomain.ddns.net)... 110.78.XXX.XXX
Caching mydomain.ddns.net => 110.78.XXX.XXX
Connecting to mydomain.ddns.net (mydomain.ddns.net)|110.78.XXX.XXX|:443... Closed fd 4
failed: Connection timed out.
Releasing 0x000000000195b9e0 (new refcount 1).
Retrying.
--2017-11-24 15:52:36-- (try: 2) https://mydomain.ddns.net/
Found mydomain.ddns.net in host_name_addresses_map (0x195b9e0)
Connecting to mydomain.ddns.net (mydomain.ddns.net)|110.78.XXX.XXX|:443... ^C
Se eu fizer exatamente o mesmo de um local em algum lugar aqui na Tailândia, mas fora da minha rede privada, tudo funcionará como excluído.
Como se pode ver, não há problema de resolução, porque quando eu faço o segundo wget, eu uso a porta standart, e isso é encontrado e então redirecionado.
Eu não configurei nenhuma regra de firewall, mas pode haver alguma coisa ???
O que poderia ser mal configurado na minha instalação para ter esse comportamento?
thanx antecipadamente