--> 184.168.131.241 ===> this is GoDaddy that make a forward to the other server
--> 144.91.105.68 ===> is the real server
What I think and would say to you, and what I guess, is that into the "challenge" function the certbot check only for one occurrences of DNS records and the result is a failure.
To achieve the certificate I create temporally this condition:
K http://wapp.urbedrive.com/ 144.91.105.68, Status 302
http://wapp.urbedrive.com/ 184.168.131.241, Status 200
configuration problem - different ip addresses with different status
K https://wapp.urbedrive.com/ 144.91.105.68, Status -2
https://wapp.urbedrive.com/ 184.168.131.241, Status 200
configuration problem - different ip addresses with different status
The second - you see the problem.
You can't install a certificate on that GoDaddy server:
Why would you point your subdomain to the GoDaddy IP address in the first place? You say for a "forward to the other server", but I don't understand that? What kind of forward? Which other server?
The situation is:
on GoDaddy I have a normal hosting server, no VPS I haven't a full control.... I could set only manually SSL from a panel configuration, or buy from them. Here another collaborator has installed a wordpress.
I wish a subdomain that point to an IP address that I have on Contabo.com, and here I have .NET core framework over Debian.
From GoDaddy panel I have the option to create a subdomain forward with URL masking, and this option create the double IP address.
unfortunately I need a quick and easy solution for my level, in the future I will find a solid, convenient and functional solution.
Just like @JuergenAuer said, you don't need that URL Forwarding from GoDaddy.
The url Forwarding is a feature primarily for people who don't have control over the host they are forwarding to (and it's becoming more and more useless in the past few years).
If you have control with the destination IP, you just need to point your subdomain to that IP with an A record, then at your destination server, setup a virtual host (configuration) for your subdomain.
In addition to the answers other people have given (which I fully agree with), it might be helpful to know more about how this part works. The challenges aren't performed by Certbot, but by the certificate authority, which tries to connect to your server to check that you really control the names for which you're requesting a certificate.
Certbot's role here is requesting the challenge from the certificate authority, then performing steps on the server to satisfy the challenge, then requesting the certificate when the certificate authority has verified that the challenge was satisfied. But the verification is not performed by Certbot or anything else on your server.
As other people's replies indicate, having both the DNS records for the server itself and the GoDaddy forwarding service does not provide any benefit, but does create a likelihood that the certificate authority will encounter a failure when checking the challenge.
