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. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
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.
My web server is (include version): Rumpus server software 7.2.2
The operating system my web server runs on is (include version): Mac OS 10.14
My hosting provider, if applicable, is: Strato AG
I can login to a root shell on my machine (yes or no, or I don't know): I don't know
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 1.14.0
I'm using a server software on my Mac with DynDNS from my hoster with the subdomain above and portforwarding in my router FritzBox 7490.
I have installed Brew and Certbot with the terminal. By completing the validation with the command above in the terminal to get the certificate I get the error message above.
In a Mac forum some users have told me that the issue is the appearing "/Login?" in the URL that is attached by the server software.
How can I complete the validation?
Regards
Thobie
You'll need to look into modifying your Rumpus webserver configuration to add an exception for serving /.well-known/acme-challenge/ without the redirect.
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.