SSL Everywhere (Again)

It’s almost hard to believe it’s only been 2 years since Let’s Encrypt came out of beta and began providing SSL Certificates to the general public. I wrote a post at the time calling it a turning point for the web, but cPanel support was pretty much non-existent. Since then much has changed. Just 2 months after that post was written we began using a plugin that offered Let’s Encrypt support directly in cPanel for all users on Reclaim Hosting and announced general support for free SSL certificates. In August of 2016 we began employing ways of scripting the ability for domains to get certificates automatically using the plugin and hooks from our billing system and I wrote a post aptly titled SSL Everywhere where I wrote:

After testing over the past 2 weeks I’m pleased to announce that going forward every domain hosted by Reclaim Hosting will automatically be provisioned with a free and renewable SSL certificate by default.

Around that same time cPanel had also made strides to offer their own support for automatic certificate provisioning with a feature announced called AutoSSL. Initially AutoSSL only supported cPanel’s own certificates issued through Comodo but later Let’s Encrypt support was added. Rate Limits employed by both certificate providers made it difficult to truly promise SSL everywhere and one issue we found was that notifications were a real problem.

Normally receiving a notification that your domain was secure would be a good thing, however often we have found this can confuse a customer that thinks they might have been charged for something, or possibly that the email is spam, especially if they didn’t specifically issue a certificate themselves (and remember we were attempting to issue certificates for all users so that would often be the case). Our ideal scenario is one in which all domains have certificates but no one gets needless emails regarding the provisioning of them (success or failure). Our plugin offered such granular notification settings and at the time AutoSSL did not so given the conflict we decided to double down on the Let’s Encrypt plugin and disable the AutoSSL feature across the board to streamline things.

We have more recently found out that there is a key difference between what the AutoSSL feature can accomplish and the plugin we use cannot. AutoSSL can (and has in many cases) replace and renew certificates for expired domains. That is a good thing in that even if you had a self-signed certificate or previously paid for one and it had expired you’d get a new free one. What we didn’t know was that our plugin was not able to do this, so when we disabled cPanel’s AutoSSL feature we suddenly had a large number of domains with cPanel-issued certificates that the Let’s Encrypt plugin could not renew or replace leading to confusion with folks waking up and finding their sites didn’t work over https.

In the past we have pointed folks to our documentation on installing a Let’s Encrypt certificate but remember our goal was that no one was supposed to have to do that. SSL Everywhere was and still is the goal. We needed to fix this. I’ve reached out to the plugin developers who are now aware of the issue and have committed to working on a fix that could be released along with wildcard support in the next 2-3 months. But that’s a long time to continue fielding issues of certificates not renewing which can render a site inaccessible.

We decided this week that a better short term solution was to turn the AutoSSL feature back on and have it issue certificates for any domains that did not have them or were expired. We would continue to have the Let’s Encrypt plugin exist but with the goal being that users would have a certificate from one or the other automatically and either way they would be renewed automatically. Unfortunately an attempt to ensure that users didn’t receive a bunch of notifications of this failed. cPanel provides an API call to change the setting and it returned the correct response so I didn’t think to check and make sure the setting was actually changed and it wasn’t. Long story short there, many users got emails for every certificate provisioned. But we’ve fixed that now so that the emails won’t be sent in the future and meanwhile the good news overall is that I think we’re much closer to the goal of SSL Everywhere, provisioned by default and renewed automatically with no work on the part of users.

We’ll continue to keep an eye on this in case the landscape changes (with technology it always does) and as always reach out if you have any questions or concerns!

Patching Meltdown and Spectre

Patching Meltdown and Spectre

Seems like every 1-2 years we get a major security scare in the form of a global exploit that effects server infrastructure in some fashion and requires a response. We’ve had Heartbleed, Poodle, Shellshock (who comes up with these names anyway?). 2018 didn’t wait long to bring us that gift in the form of Meltdown and Spectre. https://meltdownattack.com/ has a lot of great information about these two exploits but the short story is that rather than taking advantage of any particular software configuration, these exploits expose vulnerabilities in pretty much all modern CPUs. That means not only does this require patching for server admins like me at Reclaim Hosting and across the web, but every operating system from all computers including mobile devices and personal computers are vulnerable. The vulnerability takes advantage of exploits at the hardware as well as software layer to leak data into memory that can then be read by the attacker. It’s not a question of whether or not you are affected, you are affected.

Antivirus can’t block it either, only patching the underlying systems will resolve it and thankfully companies have been hard at work at getting these patches developed since long before the news became public. Intel became aware of the exploit last fall and many major companies have been under an NDA as they developed patches to secure their systems. Due to the complexity of this exploit however, we are still awaiting patches for some systems and now it is public (which will hopefully light a fire under certain groups to get these patches out).

Thankfully when we at Reclaim became aware of the issue last week CentOS, the distribution of Linux that powers over 90% of our server infrastructure and the only supported distribution for cPanel, was already releasing patches. We had to do some testing as well as await patches by Cloudlinux which is a third party that we use for our kernel software, but by Monday we felt confident the patches were safe and we set to work to patch our entire fleet. Normally with maintenance that involves downtime we like to give customers a heads up and with this kernel update requiring a reboot sites would indeed be offline for a few minutes, however we made the judgement call to rip the bandaid off and favor getting these patches in place as soon as possible rather than risk data being exposed as a result of the vulnerability. By 6PM Monday our entire infrastructure that runs cPanel and all CentOS servers were patched for these exploits with minimal downtime across the majority of our servers.

We have a small number of Ubuntu servers that we are still awaiting a production patch on and hope to receive that sometime this week. If you want to make sure you are secure, the best thing you can do is run all updates for your operating system and browser to make sure you’re running the absolute latest version. Due to the nature of the exploit there is no way to trace whether the vulnerability has been taken advantage of (it does not log any of its actions) so it’s particular important to be proactive. I’m proud of the capacity of Reclaim Hosting as a small operation to remain aware of these events and to stay on top of them in a timely manner.

Now can we take a nice long vacation from these major exploits? My spidey sense tells me that’s likely not to be the case as we come to rely more and more on computers and specifically internet-connected devices in our lives. It’s the new normal and the best security we can hope to have is proactive patching and awareness.

Embedding Myself into the Professional World

Well, #domains17 is done! We’ve wrapped up on Tuesday and are all home by now. I definitely needed a few days to gather my thoughts for this post. I’m so grateful for this chance to experience what the Ed Tech world is like before I even start my job with Reclaim Hosting. It was a great way to meet tons of new people I will interact with. 

wanted to talk a bit about what I wanted to get out of the conference, how the conference actually was, and what I’m doing after it. 

So I knew that Reclaim was planning a conference in OKC back when I was an intern. Lauren would send messages on Slack of updates to her planning and it was very cool to follow how she was planned out the entire thing. I was looking forward to hearing about all the fun once I started at Reclaim. Then about 2 weeks ago, I received an email from Tim asking me if I could come along with them to OKC. I was on board immediately! I definitely didn’t want to miss the chance to get to hang with the full team before I started and to see what the Ed Tech world was all about.

Now flash forward to Saturday. I was so nervous, anxious, but mostly excited. I was nervous because it was my first exposure to a business conference. I was anxious because I really only knew the Reclaim and UMW crew out of the 80 people that attended. But I was mostly excited for this wonderful opportunity to really jump into my career with both feet before it even begins. 

I arrived at the hotel by the early afternoon and met the whole team to get things set up for the conference. Although the conference really started on Monday, we used Saturday and Sunday to get acclimated to the space and have everything ready for when people got in on Sunday. We all got dinner together along with Adam Croom, the University of Oklahoma liaison for the conference. He and Lauren worked closely to plan. It helped to have someone on the ground who knew the surrounding area and was able to provide awesome recommendations. 

Sunday rolled around and it was a great day full of awesome conversations. Lauren and I started the morning by walking to a local coffee shop called Coffee Slingers. And when I say walked, I mean like 30-40 minutes through the city. OKC is a weird mix of open space, but also you get into the city quickly. It was such a nice morning, despite the rain that I totally didn’t mind walking. I enjoyed the time to get to know Lauren a little more than just from our Internet class with Jim in 2014. It was a great girl bonding morning. After the morning, we met for lunch with Jim and Tom Woodward for another meal full of awesome conversation. Tom talked about his work with Georgetown University. He gave a presentation on his work during the conference, you can read that here.  He also took some awesome photos as well. 

This was my first experience with a conference like this where I am actually involved. I’ve been to other conferences before but never on my own and in this capacity with people who are now colleagues.  But honestly, I couldn’t think of a better way to be introduced to the new professional world than through this conference. Jim, Tim, and Lauren both helped make me feel very welcome by introducing me to people and asking me to be involved with a lot of the conference. 

We kicked off the conference with a Domain Fair, where participants had numerous booths talking about the different projects they were working on. It was a great chance for people to catch up. For me, it was a great experience to see for the first time what people were working on. I was also recognized from Twitter which was insane, I hadn’t thought that my profile would be recognizable!

Then it was time for Martha’s Keynote! Martha Burtis was my boss at UMW, the director of the DKC, and I knew she was going to talk at the conference but I had no idea that I was going to see it. It was totally awesome. At UMW, the Domain of One’s Own project has been around for 4 years. I was a student there when the program started and I’ve seen it grow so much over the years. Martha talked about the DoOO program being at a point of “inflection,” as she called it, to shift the focus from getting the program set up, to a point of deeper thinking about what DoOO really is. Martha said

“I want to spend my time here dwelling on the the inextricable, in this case, why we in higher education must teach our communities to grapple with the Web in these deep and discerning ways — how the Web, and our culture, and our systems of education are bound up with each other and why they demand a particular responsibility of us.”

For me, this quote really stuck. I have noticed a lot of times that people don’t really understand how to navigate the web. And not just students I’ve encountered as a DKC tutor either. Other students and friends take the web for granted very often. It’s important that we teach others how to use the web, what the web represents in our society today, and promoting digital citizenship. Martha continued to talk about DoOO and provided some thought-provoking points. Towards the end of her talk, she mentions my name. I was totally surprised!  She talked about my individual study I did last semester and one of the questions I asked, during the interview process, if the web was a concrete space what would it be? Martha put together all of the answers to that question. It was such a cool video, take a look:

She challenged us to think about what the web would look like if it was a concrete space to us. After I interviewed everyone for the project, I had an idea of what everyone else was saying but I never really put it together like the way Martha did. I thought about and thought about it, then, it hit me that the web was a shipping container. You can do a ton of things with shipping containers, build shelters, buildings, and ship things in them. But when I’m talking about the web as a shipping container, I don’t mean just one of them, there are thousands of them around the world. And they can be transported anywhere in the world. There’s not just one item in them either, there can be a bunch of different products in one container. Just like websites, there are tons of different things within a website.

I thought this example is perfect for what the web represents in my life. My dad works on ships, piloting them from the mouth of the Chesapeake Bay up to Baltimore Harbor in Maryland. He travels on all types of ships, car, container, and tanker ships. So I thought to illustrate my example of the web as a concrete space, I would use some of the photos he’s taken from the ships perspective:

Panorama Shot my Dad Took

 

I took this in London when studying abroad.

Another photograph my dad took while on a ship

After Martha’s keynote, the group broke into sessions for the remainder of the conference. This was another great opportunity to see what others are working on. This was very new to me, which was very exciting. But there was a chance for me to step out of my comfort zone as well. I’m used to being behind the scenes of events not presenting in front of other people. During a few of the sessions, I was introducing the speaker. It may seem like a small thing introducing someone but for me, especially since I’m so new to the field, it was pretty daunting. Luckily I got to introduce some of the UMW DTLT crew, so that took a little bit of the nerves away.

The first talk I introduced was Sean Morris and Jesse Stommel’s “If bell hooks made a Learning Management System (LMS).” Their talk was awesome, diving into the question: If bell hooks Made an LMS: Grades, Radical Openness, and Domain of One’s Own. Here are a few quotes from the talk:

I also introduced Jordan Noyes and Lora Taub who examined archiving protests. This was something that I’ve never really thought about. I haven’t participated in a protest before, but after their talk, I was intrigued. So I’ve set this as a new goal, start archiving protests, or participating for that matter.

One of the other talks I went to was from Jess Reingold and Jenna Azar. Jenna is an Instructional Designer at Muhlenberg College, who also runs the Digital Learning Lab, which is just like the DKC. She brought her son along, Jarrett. Jarrett is a Digital Learning Assistant and helps students with their digital projects. It was really interesting to see how the Digital Learning Lab is run as compared to the DKC, and really cool to see the concept that the DKC started to continue to grow.

Jess talked about her time as an Instructional Technology Specialist at UMW. It was really interesting to see that perspective. Here are some quotes:

Overall this trip was one of the best things I could have done to kick off my career. It still hasn’t hit me that I start at Reclaim Hosting this week. I feel refreshed, excited, and motivated to get a start and jump into my work at Reclaim. Thank you, Tim, Jim, and Lauren for this opportunity!

Wrapping Up as an Intern

Well as this semester is wrapping up, I just wanted to write a reflection of my time at Reclaim Hosting. It’s really weird to talk about as the last weeks of my undergraduate finishing up. It still hasn’t officially hit me yet that I’m graduating in May. But things are finalizing all over the place, I just had my last classes and I’ve got a job lined up! I’ve officially accepted a position to stay on the team at Reclaim! I start in June, so I have a little time to enjoy my summer and it will be exciting to move back up to Fredericksburg.

Enough chatter though! Time to get into it. Not too much has been going on. I was still working on documentation for the new company the team has started called Rockaway Hosting (I’ll talk a little more about it in a little). I created a style guide to use with the new articles. Style guides are vital in technical writing. These articles are what the clients will look at if they have a problem. They keep the article flowing in a precise way so that the readers don’t spend too much time on the article. The goal of each article is to solve the client’s problem efficiently. The tricky thing too is that you want clients to stay on your website because they are more likely to click on more pages and posts. Luckily I didn’t have to write the articles, if I did, I would have no idea what to do. Most of the topics were written on topics I never really thought about until I started with Reclaim. But there was a major learning curve, and I actually used the articles to figure out what I needed to do. When I started to go through each article, I learned a lot about the different topics as well, because as I was combing through each article, I would go through the steps to make sure they were accurate. Unfortunately, I did not finish all of the articles, but that’s okay! I can continue going through them when I start in June.

I also wanted to talk about what I’ve learned throughout my time as an intern. For starters, I got to see what it was really like to be in a workplace. I’ve had summer lifeguarding jobs and most recently my job at the Digital Knowledge Center, but those helped me gain skills that I can put towards my career. They were a professional environment to some extent, but they are nothing like a real office space. Even though Reclaim is as casual as it gets, there is still a professional feeling to it that I hadn’t experienced while at my other jobs. I was given projects and I would work on my own. A lot of the time in my other jobs, I would work on projects with other people. This was such a change to start working by myself. I learned a lot about time management and staying away from online distractions.

I learned a ton about web hosting and a lot of components that go into it. It is really such an interesting field in technology. I never realized how intense web hosting is. There are a ton of moving parts, you have what the clients see and what the administrators see. There is a community forum used by the clients to search for help when they run into trouble. Of course, there’s the support side of things, which I have to say is the best part but I’m biased. It’s so fascinating to explore the ins an outs of webhosting, that field is really something I’ve come to enjoy.

So let’s talk about Rockaway Hosting! Jim wrote about it on his blog here (he explains it way better than I will). But Rockaway Hosting is the non-educational counterpart to Reclaim Hosting. Reclaim Hosting is mainly about Domain of One’s Own, which I’ve been involved with through Mary Washington since I started there in 2013. I’ve been working on a project for the program for my individual study, which you can read about here. So Reclaim has been all about educational web hosting. Now Rockaway is different to Reclaim in that it provides different hosting plans and support features for an additional fee. The company was still being built when I first started at the Reclaim, but it has grown so much to start a ‘soft-launch’ and hopefully, soon it will be fully operational! I’m really excited to see Reclaim growing!

But that’s it for me as an Intern! I’m really excited to join the Reclaim/Rockaway Team in June, I’m so fortunate to begin my career with them!

New Projects With Reclaim

Well I’ve been at Reclaim for 6 weeks now! I can’t even believe it, it feels like I’ve been there for months. I’m really enjoying my work and I’m definitely getting the hang of things when answering support tickets. I still ask Tim a ton of questions throughout the day because there is just so much to learn. But in this post I wanted to talk about some new projects I’m tackling for right now, one I started before my spring break and another just this week.

Just before break (so two weeks ago) I started learning a network protocol called Secure Shell or SSH. SSH is a cryptographic network protocol used to navigate through servers remotely, that means you don’t have to log into your account in your browser like you would normally. You use a separate program entirely. On the Mac its called Terminal. Its a very quick, secure, and efficient way to view files and error logs. This comes in very handy for numerous tickets. One ticket came in where the user was having a problem accessing their site at all giving a HTTP 500 error. That usually means that some aspect of the site is broken thus completely breaking the entire site. Using SSH we can go into the site and clear out the bad file to fix the site. Another ticket came in where the user was having trouble with their storage quota. SSH can read the error log right in the program and that allows us to figure out what went wrong. I’m actually struggling with SSH quite a bit however. My brain and code do not mix at all. So its difficult for me to wrap my head around this new type of navigation. But I think I’ll get the hang of it slowly but surely.

 

I started the second this past week. I am now tackling documentation on the community pages. I’m going through all of the articles to update screenshots, and rewrite a few if the process has completely changed. I’m enjoying that as well! Back in the summer of 2015 I tackled that same sort of project for the Digital Knowledge Center. The DKC was in the process of migrating its documentation to another site and I was in charge of creating a style guide and rewriting the documentation accordingly. So I felt like an old pro going through the other documentation at Reclaim. Its very different though. There is a lot more information to understand and a ton of different topics. Its actually helping me learn a lot about other topics that I didn’t know at the DKC, like nameservers, domain management, and other open source platforms.

I also wrote a new article on the community page, for installing themes to an Omeka site. That was a lot of fun, I’ve never used Omeka before and I had to experiment with it before I could write the article. Omeka is relatively intuitive so I was able to write the article very quickly.

On another note, I continually run into a problem when I’m answering tickets. At the DKC we tutor WordPress, which means we can help students edit their website, but at Reclaim the support we provide stops when it comes to actually editing the clients website. I’ve had a few tickets where clients want help actually editing their site and I’ve had to tell them I can’t. I want to help but its out of Reclaim’s wheelhouse. I guess I’m still getting used to the fact that the DKC and Reclaim are two completely separate companies.

But other than that I’m still having a ton of fun and I’m learning every time I step into the office. Stay tuned for more posts!

Learning New Content Management Systems

When I started at Reclaim I realized that I needed to learn some more open-source web platforms than I thought. At Mary Washington, I mainly work with students on WordPress, which makes up the majority of the domains. That’s a different story at Reclaim.  There are multiple applications that access the file manager (which is like the file manager on your computer). I’ve had a couple of tickets where clients needed help with two applications that have access to the file manager: Omeka and Drupal. So I decided I would set up my own subdomains for each application and learn as much as I could. I figured this would help me more when clients need support on those applications.

Drupal:

Drupal is a content management system similar to WordPress. The Interface looks very similar to how you would navigate WordPress, and even add content. But it definitely is not WordPress. Drupal looks a little rudimentary to WordPress but it gets the job done. I spent some time adding test content, pages, themes, and plugins as well. Drupal mainly operates through the interface itself so it does not use the file manager but it’s still very useful to learn since people still use the platform to create content.

Problems I ran into: I struggled when trying to install some themes. There is a specific file type you need to use when installing the specific one I found.  Drupal’s main website has tons of themes and I found it hard to pick just one. When it was time to install the theme I had to download the file to my computer then upload it to my Drupal install. Pro Tip: Don’t use the .zip form of the theme, use the .tar.gz part of the file. That’s where I hit a road block. For a while, I wasn’t able to install a theme and I couldn’t figure out why. Now it really seems obvious that I needed to use that specific file type, but now I know.

 

Omeka:

Omeka is another content management platform where you can create posts for specific items to document them. The items can range from specific historical artifacts to pieces of artwork, and really any item you’d like to document. At Mary Washington, the history department utilizes this tool more than any other department. Omeka mainly uses their interface to create their own content through the back end of that specific install. But Omeka uses the file manager to install and manage themes and plugins. This is a little different than expected but it was very easy to get the hang of. Reclaim has a great documentation website where I was able to look at how to add themes and plugins through the file manager.  I had one support ticket where she needed help with the file manager. After looking into how to use the file manager it takes just a little bit to get used to but it’s useful to have the themes and plugins held in a separate area on the file manager. Using Omeka is very intuitive, the interface lays out all of the options you will need when posting an item.  When you customize the space as well Omeka gives you all the options for customizing the theme around all in one page.

 

All in all both applications are good options for content management. But if it were up to me, I’d definitely recommend using WordPress over anything else 😀

Continuing on the Learning Curve

These past two weeks have flown by! I’ve just completed week three at Reclaim Hosting and I have to say it’s been really enjoyable. Things on support tend to be a little slow while I’m working which is good and bad. Good because that means things are running smoothly for clients but also bad because that means I don’t have much to do! I’m still in the learning phase for sure but I’m getting the hang of things. This week I was able to solve a few tickets on my own!

So in this post, I wanted to talk about a few things that are going on in my internship. 1. Some things I’ve learned in these past two weeks while filling out support tickets. 2. The current projects I’m working on or going to work on in the very near future.

Support tickets! A lot of people asked me when I first got my internship: “Why support?” “Why would you want to handle all the problems people run into?” And for me, the answer was really simple. I like helping people. My on-campus job at Mary Washington is to tutor people on digital projects at the Digital Knowledge Center. Students come in who need help with their websites, mainly WordPress, domain management, video projects, audio projects, and image projects. A lot of the time when they come in for help it’s really just the basics of getting set up with a domain name or even installing WordPress through Installatron. After working at the center since it first opened back in 2014, I’ve learned a lot about the ins and outs of WordPress help and was able to take those skills to my own website.

^^The office does not look like this at all. But it would be really cute if it did!

But support at Reclaim is very different. I don’t think I realized this at first and I was surprised to see the wide range of topics each support ticket covered. And I have a lot of new topics to learn. I started looking through the documentation that Lauren wrote back when she started at Reclaim and that is extremely helpful. I’m a very visual learner so I learn by actually completing the tickets as well. But it’s also really weird to try to complete the ticket because I’m not sitting right next to the person like I would be at the DKC. That was a major adjustment I am still getting used. Sometimes people will submit tickets with not a lot of information on their problem and I just want to jump through the screen to see what they see on their computer screen.

Another major learning curve is with applications. Since I mainly tutor on WordPress, that’s the application I know the most about. Reclaim supports a ton of other applications, though. At one point last week I was trying to help someone upgrade their Drupal install to the most recent version and I had absolutely no idea what I was talking about. Luckily Google was on my side for this ticket and I was able to quickly find the solution to the problem (or at least find a tutorial to help the person through it). The same thing happened with Omeka. Now I know a little more about Omeka because some classes in the History department at UMW use it. But I don’t know much.

I’ve been talking with Tim this past week about things to start working on when support is not so busy. We came up with a few projects I could start working on. I am going to start working on my own Omeka and Drupal installs on my own subdomain to learn all I can to prepare for potential support tickets. Tim also suggested that I start learning SSH, a command line language to navigate around the servers efficiently.

So stay tuned for the next couple of weeks to see my progress and how the internship is going! I’m excited to keep learning all I can!

Reclaiming my Internship

Hello everyone! I haven’t posted in a while. But I’m really glad to get back to the blog! You’ll see a lot more posts from my this semester because I am blogging for two major things happening as I begin to finish up my time at Mary Washington. I can’t believe I’m set to graduate in May! I have bunch of exciting projects coming up as well so stick around to hear more about those.

Reclaim’s logo

So this post is going to be about my internship! I’m currently working for Reclaim Hosting, a web hosting company based here in Fredericksburg. They currently host the all of the University of Mary Washington’s websites through the Domain of One’s Own program, which is where I was able to get this website. Reclaim also hosts numerous other schools websites as well, some of those schools use the same program that UMW has.

My first day was on Monday and I have to say it was so much fun! I’m tackling the support side of the company, so I will be helping clients with anything they need help with. That could be something as simple as giving them more information about the products Reclaim offers, to domain migration, and broken websites. And that doesn’t stop there. There’s a ton of things that could potentially go wrong. Way more than I thought.

It’s a little overwhelming at the moment because I really have no clue where to begin when a new support ticket comes in. But I’m taking it one ticket at a time and Tim is so helpful when I have a question. Jim and Lauren both work remotely and they also help out so much when Tim is unavailable. The group is very supportive and I’m very grateful for each of them.

I’m currently working my way through some online documentation on the Reclaim website to learn more about how to solve the potential problems clients could have. I’ve been going through previous support tickets as well. It’s a lot of research! I have a little bit of experience through my tutoring job at the Digital Knowledge Center but its more support for what the client sees. I work directly with WordPress, and cPanel. Reclaim is different in the sense that we work one level up through the servers to provide support. I had a few flashbacks to my sophomore year starting at the DKC and having absolutely no clue what I was doing. But I’m genuinely enjoying the work at Reclaim, I like helping people through problems and teaching them how to use specific parts to their account.

But one thing I definitely want to work on in the coming weeks, I need to get better at writing descriptions and I need to proofread before sending out the correspondence. I find I tend to repeat phrases multiple times within a ticket. So that is one thing I want to improve in the next few weeks.

So that’s it for this post! Keep checking back here throughout the semester. I will post regularly to document what I learn. I’m excited to continue learning more and more while working with Tim, Jim, and Lauren throughout the course of the semester!

Domain SEO Service Registration Corp. is a Domain Scammer!

While I’m on the topic of domain scams on the bava, I got another good example of how these human cockroaches work. Below is a copy and paste of one of two emails I received via email last week from the scam artists at Domain SEO Service Registration Corp. The other one I got was identical, it was targeting the ds106.us domain rather than bavatuesdays.com. At first glance the email below reads like an expiration notice for the domain. I know this is a scam because I control the vertical and horizontal of this domain through Reclaim Hosting. Another hint for me here is the date is all wrong, I registered bavatuesdays for the first time on October 12th, 2005, I remember the day well. Reading the email I also notice they’re using the public whois data provided by ICANN because I used UMW’s street address as a way of deflecting any personal info from being out there—a cheaper ID protect option

Read more

Reclaim Your Domain Web Series

A few weeks ago I decided to start putting together some targeted screencasts from the standpoint of building a website from scratch using Reclaim Hosting. It’s one thing to have lots of written documentation (and we’ve got that in spades at http://docs.reclaimhosting.com/) but another to sit back and watch someone work through all the various aspects of building out a web presence. What I love most is that even I learn a thing or two in the process!

Below is a quick recap of the first 4 episodes that are already out. Each on is attached to an ongoing playlist and you can subscribe to our YouTube channel to see them when they come out as there will definitely be more!

Read more