Sad, Hosted four times with this and had almost flawless results. Gonna miss :(
This service allowed me to host my servers easily with the performance I needed, and I'd really like to salute Jincux's work and thank him for keeping this alive for the time it lasted. Thank you for your quick technical support and all the help, really gonna miss it.
Thanks for the kind words and I'm glad you guys enjoyed the service. Closing down is bittersweet.
Do we get refunds if our subscriptions are still active?
All active subscriptions were cancelled yesterday and all servers will have expired by August 31st. None of the 'token' servers have stockpiled past August 31st either.
wonder how much it costed u but im not surprised it end like that
next is blglass closing?
It wasn't consistently negative, hugged the break-even line pretty closely. My low-overhead approach somewhat doomed the system. Glass Hosting would automatically rent out a server from Linode and then host two Blockland servers on it. This process itself was buggy because Linode limited disk image sizes, meaning I needed a full installation and startup script to install all the needed software on the newly rented server, which never seemed to work consistently. With this system, I could easily end up with two half-full servers, which totaled as a loss of money. The entire system wasn't built with much central infrastructure, a lot more weight was placed on the nodes then there should've been - complicating stuff like wrapper configuration and file transfers. The relatively complicated file transfer made it difficult to promote "server migrations" that would've eliminated having two empty net-negative servers.
The panel was a bit of a pain. I used Socket.io which is a pain and a half more than it should've been. Users would visit the panel at host.blocklandglass.com, which would then connect to their server at ny##.host.blocklandglass.com. However, some of the forms of connections that socket.io chose to use really didn't like being on a different domain, all at the implementation level (so cross-origin settings weren't helping). Socket.io would sometimes lock up on the server side for no apparent reason, requiring a restart.
Managing a dozen security certificates and software that couldn't hot-reload the certificate when it renewed was a huge pain (and is actively occurring right now, as all the certificates are expiring).
Glass itself isn't going anywhere for the time being - it's secure for at least the next year, going to re-evaluate and see if it's worth renewing then. My current long-term plan is to keep Glass together as a content repository even if Blockland doesn't continue. Would definitely downscale, Glass Live would be cut in that scenario (which would only occur if the player count justifies it). Although, all of non-hosting Glass is open source, so anyone is free to host it if I were to stop.
Show Posts
