I recently created a new nextcloud server by downloading the snap package. It worked fine so I decided to add ssl encryption. I had my subdomain cloud.fluxhub.net redirecting to a dns fluxhub.cloudwatch.net and I encrypted the dns. It worked perfect (I should have just stopped) however I wanted to see if I could switch my cloud.fluxhub.net to be the url and not use the dns. That’s where my issue starts. I went into my cpanel that hosts cloud.fluxhub.net and changed it to redirect to my static server ip address and then I couldn’t get my ssl to show up anymore. I created more ssl certificated for cloud.fluxhub.net and fluxhub.cloudwatch.net which didn’t help.
Now I am trying to add ssl encryption the same way I have done before. I removed my cloud.fluxhub.net redirects and deleted off any ssl from Bluehost associated with cloud.fluxhub.net. I deleted my dns (fluxhub.cloudwatch.net) and created a new one to start from scratch. The only thing pointing to my server is my new dns fluxhub.palvelin.net, but when I add my ssl certificate it doesn’t encrypt and still says my ssl is issued to cloud.fluxhub.net. Is there anyway to stop this from happening? I have read the rate limits (maybe I just have to wait a week) and I have tried revoking certificates, but I’m still clueless what I should do or how long I should wait.