streetartlist Posted December 9 Posted December 9 Today I noticed that there was a little notice in my dashboard that "WWW domain not secured". I tried reissuing the certificate and got this error (see image). I remember seeing something about www DNS records not carrying over a month or so ago, so perhaps this is related? Everything else works as it should, but I can't secure the www prefix and the site doesn't load if I prefix the URL with "www." Site: thestreetartlist.com
MoneyBroz Posted December 9 Posted December 9 it seems that the www record is non-existent on your domain. Escalating this post so a root admin can add the record for you. 1
MoneyBroz Posted December 9 Posted December 9 Also as side note, the www record isn't required for the certificate to be issued for your domain.
wolstech Posted December 9 Posted December 9 Yeah, the www record was indeed missing. It's been fixed and the cert has issued successfully. 2
Krydos Posted December 10 Posted December 10 Yeah, this is a strange side effect of transferring accounts from one server to another on our ancient DNS system, that will be upgraded before much longer. Once the DNS system is updated users will be able to edit, create, and delete DNS records themselves through Plesk. In the meantime, all accounts transferred have a patch that re-adds the www cname.
streetartlist Posted December 10 Author Posted December 10 Hm.. So, the ssl certificate is now there, but now my site just shows a 404 error regardless of being prefixed with www. or not. Previously, everything else worked, it was just that I couldn't include links with the prefix. Is there something else that I need to do now, following the addition of the www record? All of my files are still there and nothing else has been changed that I can see.
streetartlist Posted December 10 Author Posted December 10 (edited) The domain was previously used on Johnny, so maybe there's an issue from that? Update: just got home for a sec and checked again. The ssl was being flagged by antivirus, so I reissued it and that stopped. Now none of my js is working. I realize that this seems to be a compounding issue, but is there a reason why it could stop working as a result of the www record being added? I'm leaving for a bit and will check to see how I'm constructing the js paths when I get back, but wanted to ask as everything worked yesterday aside from the www prefix and nothing else has been changed. Edited December 10 by streetartlist Update
wolstech Posted December 10 Posted December 10 Tommy had a bunch of issues last night. Apache is (was?) broken, among other things. This is part of an ongoing issue on Tommy.
streetartlist Posted December 10 Author Posted December 10 Another update: I think that this can be marked as solved. I don't know if Apache was causing the issues, but I saw the notice regarding PHPMyAdmin on Discord and reset my password. Following that, everything is working, so I think the database pw issue was causing an error that made the js hang up. At any rate, seems to be working now 👍 1
Krydos Posted December 10 Posted December 10 Glad everything seems to be working now. Going to mark this as solved again. Let us know if you notice anything else acting strangely. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now