Some problems after the website is uploaded to the Godaddy space

At present, the company's. cn website is subject to record filing uncertainty in China, so it has not resolved the. com domain name to the. cn space of the new domestic network. As a transitional solution, I purchased a three-month space at godaddy to deploy my website abroad.

At present, the company's. cn website is subject to record filing uncertainty in China, so it has not resolved the. com domain name to the. cn space of the new domestic network. As a transitional solution, I purchased a three-month space at godaddy to move my company's website abroad. This removes the hassle of filing procedures, second, overseas space is generally lower than domestic space.

I have little access to HOSTING space outside China. my blog is in linode VPS. I originally planned to put my website in VPS, however, since there were too many technical problems that could not be solved at half past one, I gave up this idea.

At present, there are the following problems:

1. asp websites are based on windows operating systems, while VPS is mostly open-source and free linux operating systems. there is uncertainty in portability.

2. in windows, the web server is IIS, and the web server I currently use in VPS is nginx, which has poor compatibility.

3. the company's website is Microsoft's asp framework, and VPS currently uses a free and powerful php Framework. if it does not use third-party plug-ins, it cannot be compatible.

4. the database used by the asp website is also Microsoft's access database, and VPS is based on the LNMP architecture. that is to say, the free open source mysql database cannot be transplanted at all.

Based on the above considerations, we finally decided to find the most reliable emergency solution before these problems could not be solved perfectly. this emergency solution is to use the relatively cheap hosting space provided by godaddy, the monthly cost is less than $5, which is acceptable as an experimental solution.

Next we will talk about the problems encountered during the uploading of the company's website to the godaddy space and the solutions to these problems.

Question 1: All Chinese pages on the website become garbled characters

 

 

In fact, the reason for this problem is not difficult to explain. although the space of Xinnet in China and the space purchased in godaddy are both windows operating systems, there are still differences between the two. The windows operating system purchased by Xinnet is in simplified Chinese version, while the space purchased by godaddy is in pure English version. The difference in encoding is the main cause of garbled characters on Chinese webpages.

Solution: add

This solution is widely used on the Internet to solve Chinese garbled characters in the godaddy space. Although useful, this method is not clever for webmasters who have a large number of Web files-however, after all, the transfer of websites has always been a tough task, taking time and effort. At the end of last year, when the blogger transferred VPS to the customer service for private access, he had to spend about a week. Although the principle is simple, there are too many uncertain things, and the problem is not simply put in front of you all at once. it may happen today, but tomorrow, therefore, it is essential to make a weekly discount. At this time, theoretical knowledge is not the most important, and practical operation experience is king.

Problem 2: "500 (internal server) error" exists in some web pages.

 

 

Of course, there are too many reasons for this error, such as the webpage does not exist, the database cannot be accessed, and the path is wrong. it is a great deal to find out the cause behind this error. The initial method is to guess the cause of the error based on previous experience. This is because I have encountered a similar situation during "micro-user private access" and another forum, so I think the cause of this error is probably the same as that of the previous one because of the webpage file permissions.

Searching for this error on the internet is often said that the root read/write permission of godaddy has not been granted. However, only by entering the FTP File Manager of godaddy can we find that the root folder of godaddy cannot be authorized by the permissions user. At that time, my heart gave me a giggle.-do you just stop here? The problem lies in the root permission, and the dead godaddy does not delegate permissions to the root user. However, I immediately rejected my idea, because I think that there are so many people in the world who use godaddy space, and there will certainly be many people who encounter similar problems. if they do not have such solutions, it's not long before godaddy closes the door?

Fortunately, when I was helpless, I found an article on the Internet about the web. config file. the web. config file actually only has the following lines of small code:

After this file is written, it is placed in the root directory of the website. its function is to switch the 500 (internal server) Error page displayed when an Error occurs on the webpage to a page that displays the cause of the problem, although godaddy's 500 page is black and humorous, it has no reference value for solving the problem. although the error page displayed after config is not as "vivid" as the 500 page, it can actually display the problems encountered and provide a crucial reference for solving the problem.

The following is the page content that replaces page 500 after I upload the web. config page:

Microsoft JET Database Engine error '80040e09'

Cannot update. Database or object is read-only.

D: \ HOSTING \ 9418427 \ HTML \ CN \ ../inc/news2_inc.asp, line 13

This is very intuitive. the error is caused by the failure to update the database or the object attribute is "read-only ". This error indicates that we probably have nothing to do with root permissions, at least not directly. What if I set the attribute of the database file to read and write?

It turns out that what I think is correct. after setting the folder attribute of the database to "write and read", the error page disappears and the webpage can be opened normally! The following are the steps for godaddy to set the read and write permissions for folders other than the root folder:

 

 

Note: The above two problems have been solved, but there are still many new problems. -- I once said in my previous blog that a problem is not a bad thing but a good thing. Only by constantly encountering problems, one person will make progress, knowledge can be consolidated and accumulated only by constantly solving problems!