• Announcements

    • MannDude

      Current state of vpsBoard   02/04/2017

      Dear vpsBoard members and guests:

      Over the last year or two vpsBoard activity and traffic has dwindled. I have had a change of career and interests, and as such am no longer an active member of the web hosting industry.

      Due to time constraints and new interests I no longer wish to continue to maintain vpsBoard. The web site will remain only as an archive to preserve and showcase some of the great material, guides, and industry news that has been generated by members, some of which I remain in contact to this very day and now regard as personal friends.

      I want to thank all of our members who helped make vpsBoard the fastest growing industry forum. In it's prime it was an active and ripe source of activity, news, guides and just general off-topic banter and fun.

      I wish all members and guests the very best, whether it be with your business or your personal projects.



Verified Provider
  • Content count

  • Joined

  • Last visited

Community Reputation

31 Excellent

About ElliotJ

  • Rank
    New Member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    United Kingdom
  1. Cheers for the additional info eva2000 :) I'd never really benchmarked it against anything else in a technical way, besides 'well, this feels faster' testing. It's eyeopening to see how (relatively) slow it is compared with other methods. Perhaps putting the extra 30 minutes in for a faster set up is worth it, ah well :P
  2. FiOS customer discovers the limits of

    Crap, and I thought I downloaded a lot. I have had letters, but nothing threatening to disconnect me.
  3. I'm using it across the Gatsby.im network if you want a peak around. If you view the source of any page at the bottom it should indicate how fast the page was generated. It speeds up the page generation aspect of speeding a WordPress site up. It's not an alternative for a CDN - You can use caching and a CDN together though - I personally use Redis+CDN77. The real question is whether this is the best method for you. For me, security was a concern, and blog authors needed to be able to view their changes in real-time without having to wait for the cache to catch up. No other solution was as simple, reliable and fulfilled my needs like Redis.
  4. Hey everyone. Thought I should share this method of speeding WordPress up dramatically without much configuration. This is the caching method used over at Gatsby and any WordPress based client sites I maintain. As the cache is in-memory, it handles surges of traffic very well. Want to see how it handles? Head over to Gatsby. Requirements: The ability to follow simple instructions Root access to your server (Just incase this is picked up by Google) About 15 minutes of your time This tutorial assumes you already have WordPress set up and ready to roll. I personally use this in conjunction with APC. It should work with other caching methods as well, but your milage may vary. 1. Back your stuff up Although nothing we're going to be doing will touch your databases and whatnot, it's probably a good idea to make sure you're able to revert to how things were originally. Just incase you completely fudge something up. In all honesty, you should have robust backups in place already. If not, here's your gentle reminder to get backups set up. Also - It's not a backup unless you're able to restore it easily in an emergency. 2. Add a Repo This is genuinely the most taxing part of the process, although it's relatively simple. The issue is that most Linux distros have pretty outdated versions of Redis in their repositories. Although you could just install the respective .deb/.rpm, it's a good idea to get a frequently updated repository added to your system just incase an exploit is found in Redis. If you're running Debian Linux I personally recommend you use the DotDeb repository If you're running a RedHat based Linux distro, I personally recommend you use Remi Collet's repository Follow the respective instructions on each site! 3. Install Redis If you're running a Debian based Linux distro apt-get install redis If you're running a RedHat based Linux distro yum install redis Once installed, you can fire up Redis /etc/init.d/redis start OR /etc/init.d/redis-server start 4. Make WordPress Use Redis Here's the last step. We're going to need a couple of files to make WordPress interact with Redis. The idea is that we want to use a new index.php, so that every single valid request hits Redis before asking WordPress to regenerate the page. To do that, we'll have to move the original index.php mv index.php backup_index.php You'll then need to grab predis.php so PHP can interact with Redis wget http://uploads.staticjw.com/ji/jim/predis.php Finally, grab the new index.php wget http://pastie.org/pastes/7953263/text -O index.php If all goes well, load up your WordPress site and pages should appear. If not, you've probably done something wrong. Final Statements I do not claim any credit for this caching method, all of which goes to Jim Westergren. In regards to security, it only displays the cached pages if the visitor isn't logged in - That means that whilst you're logged in pages may load slower. To refresh a page's cache, force a page reload (F5). Pages aren't regenerated if you're simply clicking through pages.
  5. How To Contact Support, Properly.

    Thanks for the feedback guys! I've added reading the ToS as it's been mentioned a couple times.
  6. Any mirrors needed?

    This was a few months ago when I had a few high-bandwidth servers free, awaiting cancellation. The particular server I was mirroring Tails on was unmetered, so the extent of bandwidth monitoring for it was minimal; I'd certainly expect about 5TB bandwidth for peak times (new releases) If you're in it for the long haul, keep up to date with Linux distro releases, sometimes there are new distros starting up without any real distribution network. Get in contact with them, Ubuntu et al. already have enough people mirroring them.
  7. How To Contact Support, Properly.

    Also clients spending $3 generally need more hand-holding than those spending significantly more :(
  8. Any mirrors needed?

    Keep up with new releases, you can always seed ISOs to contribute to the initial surge. Tails is always looking for a few more web/bittorrent mirrors, especially outside of the EU. When I've been mirroring, it's reached 40MB/sec for hours at a time. Also, consider running a Tor Relay if you have bandwidth spare.
  9. Many a time we've seen threads arise due to 'poor support' and slow turnaround times. Whilst there's the unavoidable fact that the provider can be slow to respond, it's always a good idea to make their understanding of your problems as clear as possible. Keep the upper hand by giving them all the tools they need to resolve your ticket as quickly as possible. These pointers are written from my own experiences with receiving support and giving support. 1. Read Their Terms Of Service It's important for you to get a grasp on what you can/can't expect from your provider. Although you should do it before ordering services, have another read through just to make sure your request is reasonable. The vast majority of providers on this forum are unmanaged which means besides the hardware and network aspects of your server, you're on your own. If you're having an issue with a particular piece of software, they'll be unable to help you however may point you in the right direction to get help. Better still, you can always ask on forums like this when you're having an issue. Generally speaking, people are pretty helpful in diagnosing, troubleshooting and resolving server related problems. 2. Appropriate Ticket Priority & Title Although your problem may be annoying you, unless the server is completely offline refrain from using 'High Priority'. Questions regarding upgrades, downgrades and cancellations should realistically be placed under the 'Low Priority' category. Performance issues, depending on the severity should be Low/Medium priority. Try and keep down to a few words, 'Slow Network Throughput', 'High Disk Latency' and 'Service Cancellation' are directly relevant to the problem at hand. Y U NO MAKE HAPPY' probably won't be too helpful, neither will 'YOU'RE LOSING ME MONEY'. 3. Clear & Polite Language Although their service might be a tad awful at the time, you'll be talking to human beings. Remember that how you interact with them will influence how they interact with you. Try to be courteous, don't give them an excuse to lower the priority of your ticket. If English isn't your native language, it may be a good idea to first attempt to articulate your problem in English, but write the same below in your native language. If the employees are having trouble understanding you, a quick Google Translate might be able to clear things up. 4. Provide Relevant Information Provide evidence for your problem - This may be in the form of benchmarks, traceroutes or outputs from other statistic generating programmes. Also, make it clear that it's an ongoing and not a sporadic problem by generating your evidence at different times. 5. Be Patient If you're dealing with an unmanaged service, understand that there may be a wait until you get a response. Response times may be dependent on your timezone, the provider's timezone, whether it's the weekend or not, public holidays, etc. 6. Be Appreciative As pathetic as it may seem, it's important to maintain your relationship with your provider. If you're a nuisance, they'll remember it. In the future you may really need them on your side, for example if you're the victim of a DDoS attack; don't give them another reason to kick you out. If I've missed anything, give me a buzz and I'll add it on.
  10. Sounds about right, it's been opened up to EU residents recently. Hexonet.net offers a trustee service, might be worth looking into - They also offer fairly cheap .io domain names.
  11. Wonderful site, old sport.

  12. Dirt cheap domains - EU/PW/DE/MX

    You should probably also mention that residence within the European Union is required for .EU domain names, at least in their whois. That can quite easily be evaded by using the SwissPost's free online postbox :)
  13. Post your desktop!

    It makes a lot more sense for me to just show my desk's top :P http://i.imgur.com/9DDfuZQ.jpg MacBook Air powering the right monitor, an additional laptop being suspended underneath the desk powering the left monitor. The Mac is acting as the 'server' with Synergy, sharing keyboard/mouse with the second desktop seamlessly - Helps when testing how fonts/webpages render on other operating systems.
  14. KVM/Xen/VMware in Scandinavia

    Indeed, they backhaul a lot of their bandwidth through Sweden these days so the latency is fairly unnoticeable. Have a look at Glesys and CityCloud, they have fairly good reputations.
  15. Untapped locations?

    The Middle-East - Okay, I accept that certain countries may have legal systems that could make things a lil' difficult, but surely Israel might be possible? India - Huge population, very few offers that have actually lasted.