So, the website is back online, with some changes! There might be some issues still on some random link or database references to the old hosting directory structure but I will fix them as soon as I spot them.
Hope you will receive an email from this 🙂
This is what happened on GoDaddy:
The hosting was a “shared hosting”, basically a WordPress instance and a shared folder to host some content (the packages). This is how it was born and how it stayed for quite some years. At the time it was “ok” but it went downhill over the years.
Unfortunately for GoDaddy users, being a shared hosting, you have no choice but click on some web page to get what you need. One of these needs is an SSL certificate.
Yesterday my credit card was billed more than 200 USD for an SSL certificate signed by GoDaddy. Since they sell certificates and control the platform, switching to Let’s Encrypt is not possible.
After the billing, I could see the new certificate, but the certificate was not pushed to the instance. After almost a day on the chat with random people that just told me to wait an hour without getting anything fixed, I was put into phone contact with the “shared hosting” services.
There I was told that they were aware of the problem, and that all customers on the same shared hosting (“legacy”, according to what they said) were impacted since the 30th of April (seriously??) and there was no fix yet.
You are forced to pay a stupid SSL certificate a lot, you get an issue, the certificate can’t be used, they don’t fix it and good bye. Their service is beyond ridiculous.
After some more chatting with support it seems that at least I can be refunded for the last renewal of the certificate, let’s see if this happens.
After this bit of history, back on the new hosting.
The site is no longer hosted on GoDaddy, so now this time I picked up a dedicated sysmte where I have direct access to it and I can do much more than before. This has led me to being able to use Let’s Encrypt certificates and
certbot for automated renewals, thus saving money as well.
Bandwidth is much more stable, so download times should be greatly improved, especially for me for uploading the packages. I was able to sync the ~100 GB of packages in just a few minutes.
Having access to the system means that now there is also an RSYNC daemon running serving all the content of the
/repos folder. You can sync a specific repository with a command like this:
rsync -crlpvz --progress --delete-after rsync://negativo17.org:/repos/nvidia local/path
I’ve also added the instructions on the
/repos folder directly.
A big thank you
Thank you very much with all my heart for the round of donations received! This means a lot to me.
All the donations received on Paypal and the cheaper / more versatile hosting should be enough to keep this site alive for another couple of years!
I’m planning to add some more content (ARM packages) and maybe migrate to something else that is not WordPress. I was thinking about a wiki, probably MediaWiki to make it similar to the Arch wiki, which I found very clear and easy to read, if you have any preferences please let me know.