Venting On . . .
On December 8th, the Blatha an Oir website went down. After looking under the hood, I determined it was a server issue on the ISP side. I contacted the ISP and was informed that, Yes, they did perform a server "Upgrade" and that part of the security upgrade interfered with our site.
When I became involved with the website, I installed an Enterprise Level Content Management System to the site. This allows multiple people to work on the site from different locations and eases the burden of maintaining the site. I can even make changes from my wife's iPhone if I need to. Well, this system has been around for a while, is pretty well respected, and I haven't had an issue with other ISP's I've installed it on. This ISP is unwilling to adjust the security settings and their only suggestion is to move the site to a different server. Oh, and the rest of the servers will eventually be getting this "upgrade." After researching this ISP a bit, I found that other Customer's have found that Service is an unknown concept to this company. Well, our hosting agreement is coming due in February, so I decided to go ahead and have the ISP move the site and we'll deal with what happens next later.
The ISP moved the site, but I didn't realize that the Domain is not registered through this ISP, so we would be responsible to contact Network Solutions to have the Domain pointed to the new servers. No problem . . . so I thought. When I contacted NS, they informed me that the Primary Contact that they have on file needs to contact them to have the change made. This is understandable. Unfortunately after several days, this person, although still semi-active in the Barony, has not responded to my request to contact me and to contact Network Solutions to have this simple change made.
Grrr. . . I can't do anything else at this point. I got the information from Network Solutions on how to change the Primary Contact Person and discussed it with our Seneschal. If he doesn't follow through by the end of the day, I'll start the paperwork to transfer the Primary Contact to me.
The site has been down for five days and three of them because this member of our Barony hasn't responded.
Venting Off . . .
When I became involved with the website, I installed an Enterprise Level Content Management System to the site. This allows multiple people to work on the site from different locations and eases the burden of maintaining the site. I can even make changes from my wife's iPhone if I need to. Well, this system has been around for a while, is pretty well respected, and I haven't had an issue with other ISP's I've installed it on. This ISP is unwilling to adjust the security settings and their only suggestion is to move the site to a different server. Oh, and the rest of the servers will eventually be getting this "upgrade." After researching this ISP a bit, I found that other Customer's have found that Service is an unknown concept to this company. Well, our hosting agreement is coming due in February, so I decided to go ahead and have the ISP move the site and we'll deal with what happens next later.
The ISP moved the site, but I didn't realize that the Domain is not registered through this ISP, so we would be responsible to contact Network Solutions to have the Domain pointed to the new servers. No problem . . . so I thought. When I contacted NS, they informed me that the Primary Contact that they have on file needs to contact them to have the change made. This is understandable. Unfortunately after several days, this person, although still semi-active in the Barony, has not responded to my request to contact me and to contact Network Solutions to have this simple change made.
Grrr. . . I can't do anything else at this point. I got the information from Network Solutions on how to change the Primary Contact Person and discussed it with our Seneschal. If he doesn't follow through by the end of the day, I'll start the paperwork to transfer the Primary Contact to me.
The site has been down for five days and three of them because this member of our Barony hasn't responded.
Venting Off . . .