Articles in Category: Website Management
An “Internal Server Error” happens within the web server attempting to show you a web page. It’s usually a server-side problem out of your control.
There are many reasons pictures don’t show on websites. Some you can control, but others are problems with the websites themselves.
Setting up an https-secure website is both simple and complex. The HTML doesn’t change, but you’ll need different hosting for the secure layer, as well as a certificate, to provide the security of https.
You’ve probably seen CAPTCHAs and not even realized it. CAPTCHAs are used to make sure systems aren’t gamed or spammed by machines.
HTTPS provides validation and encryption, two important pieces of security. Using it for everything is possible but costly, and issues would remain.
https uses certificates to validate the site you’re connecting to, as well as encrypt the data. Certificate errors are often benign, but are worth paying attention to.
If you run a website and have someone administering it for you – a system administrator or “sysadmin” – they may have much more power than you realize. And with great power … comes great risk.
It’s generally not possible to recover an older version of a web page, but we’ll look at a couple of straws to grasp at.
If clicking on a link causes a request to open a file on your machine, chances are the web page author made a simple, and common, mistake.
It appears that the look and feel of msn.com is changing yet again. To many that have msn.com as their home page, this change may or may not be welcome.
A secure website means the site owner has jumped through the technical hoops necessary to qualify for https. Safety is another thing all together.
Spam, spammers, and hackers. They make website management quite difficult, and you may be experiencing this with your web form.
If your webmaster leaves unexpectedly, you can have a lot of trouble getting access to your own website. I’ll review some of the things that you need to do to prepare – just in case.
If you can turn http into https and it works, that means that the site has a security certificate. So why aren’t they using it?
Ultimately, a problem with a security certificate belongs to the owner of the website. There may be a way to get around it, but you probably need to contact them.
When you operate a site on the internet, you’re putting yourself in harm’s way. Hackers would love to compromise your site for their own purposes. I’ll look at common problems and what to do about them.
The 500 series indicate errors on the server, the remote computer that is “serving” that website to the internet. There are only a few things you can do to try to resolve it.
This sounds like an advertisement coming from the website. Advertising funds websites that deliver otherwise free information. If you don’t want to look at it, you have only a few options.
Websites that automatically play sound are evil, pure and simple. And there is only one way to quickly get rid of the intrusive sounds.
The site you’re used to visiting has simply gone away. Tracking down the owner might not be easy to do.
Where to host your website depends on what kind of a website it is. Options range from free to expensive based on your needs.
No, not correct. As it turns out, this is something I do regularly with ssh, as well as both sftp and rsync, as part of my backup and load balancing approaches for Ask Leo! Let me walk you through what I’ve done.
The “www” in website addresses is now typically optional, and even redundant, but there was once a reason as to why it was required in URLs.