Website Redirecting With .Com

#1

All my links on my website now redirect to https://commsell/contact-us/ without .com in my domain name. Every my wp-admin links wont work because they keep redirecting without .com.

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.

My domain is: CommSell.com

I ran this command:
sudo apache2ctl configtest

It produced this output: (check image)

14%20PM
Screen Shot 2019-01-29 at 1.37.14 PM.png759×405 4.51 KB

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

My hosting provider, if applicable, is: digitalocean

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):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): 0.28.0

#2

40%20PM
Screen Shot 2019-01-29 at 1.43.40 PM.png832×101 1.89 KB

#3

That’s not very good. But it also isn’t something certbot would mess up. Did you manually edit your Apache configuration files?

Did you delete, move or modify any directory or file in your /etc/letsencrypt/ directory? Because Apache can’t find the certificate any longer… It’s gone. Or it’s a permission error. In any case, you’ll need to figure out why /etc/letsencrypt/live/commsell.com/fullchain.pem isn’t working. It should be an actual working symbolic link to a file in /etc/letsencrypt/archive/commsell.com/.

Also, the reason why your --standalone doesn’t work: probably Apache is still running and bound to port 80. Why do you want to use the --standalone plugin any way? Looking at the 000-default-le-ssl.conf, previously you’ve used the --apache plugin, correct? Perhaps you’re not using the Apache plugin any longer, because that plugin won’t work without a working Apache? And Apache isn’t working, b/c of the missing certificate…

#4

Hi @oday

looks you have some wrong redirects ( https://check-your-website.server-daten.de/?q=commsell.com ):

Domainname Http-Status redirect Sec. G
• http://commsell.com/
157.230.217.253 301 https://CommSell/ 0.216 E
• http://www.commsell.com/
157.230.217.253 301 https://CommSell/ 0.210 E
• https://www.commsell.com/
157.230.217.253 301 https://commsell.com/ 2.353 B
• https://CommSell/ -1 2.300 R
NameResolutionFailure - The remote name could not be resolved: ‘commsell’
• https://commsell.com/
157.230.217.253 200 3.447 B
• http://commsell.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
157.230.217.253 301 https://CommSell/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 0.214 E
• http://www.commsell.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
157.230.217.253 301 https://CommSell/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 0.213 E
• https://CommSell/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de -1 2.337 R
NameResolutionFailure - The remote name could not be resolved: ‘commsell’

Your two connections are ok, same with your certificate:

CN=commsell.com
	29.01.2019
	29.04.2019
	commsell.com, www.commsell.com - 2 entries

The http redirects are wrong. The one https - redirect is ok.

So share your vHost port 80, it’s “only” a problem of your http vHost.

#5

Im sorry this goes a little beyond my knowledge. What do you suggest would help fix this problem?

I am beyond impressed at how responsive this group has been, thank you guys!

#6

http://commsell.com/
http://www.commsell.com/
were redirecting to
https://CommSell/

[an incomplete domain name]