Good day! A very strange situation. I updated the certificate ahead of schedule, as a result, I and other people see 2 different pages (screenshots). The old certificate contains full data on the changes that occur on the site. On the new one, which is currently in effect, the contribution for 2-3 months disappears, new edits are not synchronized with the general database. How is this possible? And if possible, how can I synchronize the database with the new certificate? Spoiler: in an attempt to return everything, we have already restored the database twice in a few days - nothing came back. It is impossible to return the old certificate, which is expiring soon, it was deleted after the new one was issued. What should I do now?
Your certificate is not directly related to your database.
Right now I always see your domains using the cert from Apr19 issued by R10. Interestingly, you got a cert a day after that but your server is not using it.
I tried accessing both your domains using both the IPv4 and IPv6 addresses in your DNS. I consistently connect with the same cert (issued by R10 on Apr19).
Are the two certs you show happening now? Are you connecting from the public internet when you see those?
My guess is something has gone wrong with your nginx. If nothing else, your redirects are faulty. An incoming connection on HTTPS is sent to HTTP. You should not do that.
I suggest carefully reviewing your nginx config for any recent changes. Perhaps even just restart your server. I don't see anything wrong with the certificate or your TLS (HTTPS) connection.
curl -i6 https://fandub.wiki
HTTP/2 301
server: nginx
date: Sun, 20 Apr 2025 17:54:58 GMT
x-powered-by: PHP/7.4.33
location: http://fandub.wiki/index.php?title=%D0%97%D0%B0%D0%B3%D0%BB%D0%B0%D0%B2%D0%BD%D0%B0%D1%8F_%D1%81%D1%82%D1%80%D0%B0%D0%BD%D0%B8%D1%86%D0%B0
PS: I moved your post to the Help section where it more properly belongs.
5 Likes
Are you definitely writing wiki changes to the database you expect to? Edit an article and confirm that it changes in the database.
Most likely when you restarted nginx you loaded new untested configuration, discarding old configuration.
Restore you're database backup to a test server and examine the content. It's possible your backup is just old content and was never going to include the latest changes, because your backup process isn't working.
3 Likes
Thanks for the tips! The certificate is not the cause of the problem, but one of the factors that revealed it.
If anyone is looking for a similar problem, a tip - check the second hosting. Perhaps you migrated the domain from one hosting to another, but for some reason the data (settings) did not migrate completely and the backups continued to be saved on the first hosting. When you update the certificate, the data will start to sync with the new hosting, and a gap of 3 months will appear in the database. You will have to manually drag the database and site files from the old to the new one.
Perhaps my case is unique and will never happen again, but it is useful to know.