We are back up...for now!
Finally able to get us back online. Things will take a few hours to shake out, like lost email, etc. But we should be caught up soon.
We'll have another downtime either tomorrow afternoon or Saturday. It won't be as long ::knock wood:: but it's putting more preventative measures in place.
Thanks for your patience, folks!
What is allowed:
- Creating fanfiction for personal use, sharing it on squidge.org or an affiliate site
- Creating fanart for personal use, sharing it on squidge.org or an affiliate site
- In either your profile on a shared site, or on your personal page/space, offering fanart for sale, as long as the sale covers the cost you incurred. You cannot profit off of it, within reason. If a print costs you $5.75 and mailing costs $2.00, then charging $8 is appropriate. But charging $20 or more is not.
- In either your profile on a shared site, or on your personal page/space, calling for submissions and offering for sale Fanzines. Fanzines are designed to share stories, not for profit.
- Hosting a non-profit fundraising event for the sole purpose of raising money for a specific function like our Help Japan auction a few years ago, or as a surprise to help fun raise events for people in extenuating circumstances.
- Putting a statement in your personal profile on a shared site, or on your personal page/space, that you are taking money for the creation of fanworks.
- Having a link to Patreon, Gofundme, etc for the express use of raising money for the act of creating fanworks.
- Anything else not covered that would allow a person to use Squidge.org or its resources for the act of raising money solely for their own benefit.
Over the next few days, you may have your web browsing session interrupted slightly. I am installing SSL certificates for every domain that is hosted on Squidge.org, which is quite a few in number. Now anytime you go to a website hosted on Squidge.org without the secure "https://" prefix, your browser should be redirected to the secure session instead.
Doing this means that we have to move configuration files around, causing us to have to cycle the webserver twice per domain group. This is going to be a bit frustrating, and I'll apologize in advance. But we need to have https everywhere for everyone's web surfing safety!
Questions? Let me know!
Our server farm is located in our home, specifically in a loft in the detached garage. As it's a separate building, it has its own power, which is fed from a powerline from the house.
This winter has been more brutal than most, and the powerline to the garage (which is original to the dwelling) has frayed with the influx of ice. This fraying has caused the line to short out. This is why the power is out, and Squidge.org is down.
An electrician was able to come out last night on an emergency call (electricians are about 30 days out where we are, due to weather). He diagnosed the issue, and said that he was going to have to replace the line between the house and the garage. He was going to expedite it; someone is supposed to come out today - but that doesn't necessarily mean that the job will be completed today. I'm hoping it will be, but I'm not holding my breath.
More updates as I get them. Think good thoughts for them to complete the work today and that we can come up later on - hopefully that will happen.
First, there was intermittent Internet outages due to our ISP. Then, our mini "datacenter" (which in reality is a loft in our garage) started having power fluctuation issues. The circuit breaker to the garage blew for some unknown reason, and stayed on for a short period of time.
During that time, it was found that the power issues caused the firewall server to go kaput; so the firewall machine is dead. It will not boot at all, so I took it out of service and started installing on another machine as a backup.
Then the circuit breaker tripped a few more times. After doing research, it seems that there is a short somewhere in the wiring, so the system is shutting itself off - which means no power to the garage, and thus, no power to the servers.
So an eletrician is being contacted to come out and figure out what's going on. They'll have to fix whatever the issue is, and then we'll be able to restore service. Hopefully that will be in the next 24 hours. Then once completed, we'll run without a firewall until a new one is put into place.
My apologies for this unforseen issue; we've been running in this space for 12 years now with no real power issues (besides the occasional outage) so I know this is disconcerting. More updates as I get them.