I cant renew my certificate

[Aion]

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: escolares.conalepquintanaroo.edu.mx

I ran this command: certbot --apache

It produced this output: Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: escolares.conalepquintanaroo.edu.mx
Type: connection
Detail: 187.157.191.149: Fetching http://escolares.conalepquintanaroo.edu.mx/.well-known/acme-challenge/yy16SWf4eoIqvouYGJoBe4-dxKJJx7xnpyTrCSyAboE: Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.

My web server is (include version): wordpress

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

My hosting provider, if applicable, is:

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 2.10.0

[orangepizza]

I can't assess your site (timeout) so it looks indeed like firewall problem
LE uses few observation points from worldwide so geofirewall will block them

[Aion]

Ok, I already checked my firewall, but what IP does the cerbot use to renew the certificate? or what region?

[schoen]

The validation comes from about 5 different data centers around the world and the IP addresses are not published because they can change at any time (in fact, there was a relatively recent change).

In a certain sense they are supposed to be a representation of how "the whole Internet" sees your site (to prevent someone who controls a portion of the network from tricking Let's Encrypt into issuing a certificate with inaccurate contents). If "the whole Internet" isn't allowed to connect to your site, the HTTP-01 method (used by certbot --apache) may not be appropriate.

[webprofusion]

Another possible option is a content-aware (web application) firewall which can see the http request and specifically allow /.well-known/acme-challenge/ requests through.