How to point to port 80?

I configured A and AAAA recordings. If I call https://api.meteointelligence.com , everything works fine (with my non valid local certificate). But if i call http://api.meteointelligence.com it points to my ip address and I guess this is the problem. So where do I have to configure that the port 80 should be used?
Or are there any issues with Strato? My Server is hosted by Hetzner but the Domain was bought on strato.

My domain is:
api.meteointelligence.com

I ran this command:

certbot --apache

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache

Which names would you like to activate HTTPS for?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: api.meteointelligence.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel): 1
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for api.meteointelligence.com
Enabled Apache rewrite module
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. api.meteointelligence.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://api.meteointelligence.com/.well-known/acme-challenge/8Too29EnWOrLqlk-zZuFnv-7s80ILMbT00fPnkqXwiQ: Connection refused

IMPORTANT NOTES:
 - The following errors were reported by the server:

   Domain: api.meteointelligence.com
   Type:   connection
   Detail: Fetching
   http://api.meteointelligence.com/.well-known/acme-challenge/8Too29EnWOrLqlk-zZuFnv-7s80ILMbT00fPnkqXwiQ:
   Connection refused

   To fix these errors, please make sure that your domain name was
   entered correctly and the DNS A/AAAA record(s) for that domain
   contain(s) the right IP address. Additionally, please check that
   your computer has a publicly routable IP address and that no
   firewalls are preventing the server from communicating with the
   client. If you're using the webroot plugin, you should also verify
   that you are serving files from the webroot path you provided.

My web server is (include version):

Server version: Apache/2.4.29 (Ubuntu)
Server built:   2019-09-16T12:58:48

The operating system my web server runs on is (include version):
Ubuntu 18.04

My hosting provider, if applicable, is:
Server is hosted by Hetzner, Domain was bought by Strato.

I can login to a root shell on my machine (yes or no, or I don’t know):
Yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
No
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
certbot 0.31.0

1 Like

Hi @meteoDaniel

checking your domain that doesn’t work - https://check-your-website.server-daten.de/?q=api.meteointelligence.com

Host T IP-Address is auth. ∑ Queries ∑ Timeout
api.meteointelligence.com A 176.9.117.21 Falkenstein/Saxony/Germany (DE) - Hetzner Online GmbH Hostname: kvm.esbmz.de yes 1 0
AAAA ::ffff:176.9.117.210 Falkenstein/Saxony/Germany (DE) - Hetzner Online GmbH yes
www.api.meteointelligence.com Name Error yes 1 0
api.meteointelligence.com A 176.9.117.210 Falkenstein/Saxony/Germany (DE) - Hetzner Online GmbH No Hostname found no

The 176.9.117.210 is your old ip address.

But the old answers, the new not:

Domainname Http-Status redirect Sec. G
http://api.meteointelligence.com/ 176.9.117.21 -2 1.127 V
ConnectFailure - Unable to connect to the remote server
http://api.meteointelligence.com/ 176.9.117.210 GZip used - 3138 / 10918 - 71,26 % 200 Html is minified: 223,78 % 0.063 H

So Letsencrypt can’t connect your domain because there is no running webserver or a blocking firewall.

And your ipv6 is wrong. That’s

::ffff:176.9.117.210

not a public visible ipv6 address.

2 Likes

After using one of the several inspection tools I saw that the IP for the A record was wrong. Now everything works fine. Thanks for your support

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.