Johnb81

The problem is server side. If you use a web debugger you will find out in the server response there is an HTTP Protocol violation, thus the page is broken.

In fact the server does not respond with a 404 error but with an internal server error (500).

Definitely this is not a WordPress issue.

Hi Jimmy,

Yes it is time to contact your hosting provider support.

Good luck.

Very strange indeed. ARe you using phpmyadmin provider by your hosting provider? If that is the case simply click on the table and it should expand the table with the list of usernames.

Or else, can you explain step by step what you are doing before receiving such error?

It is strange that the uploaded file does not have the correct permissions considering the file was created using the IIS anonymous user. Just to confirm, did you check the file owner and all?

Also IIS is indeed running under the IUSR account ay?

What you need to do is a little bit more complicated than that. You have to check the User-Agent string of a browser and match that.

More information about User-Agent string: https://en.wikipedia.org/wiki/User_agent

There are many scripts available out there to help you retreive a User-Agent string. Then use it’s output.

Alternatively you can make a backup of your website, install it on your local computer to test what Esmi suggested. Like this you won’t interrupt the live site.

Make sure that the setting to propogate directory NTFS permissions to all files in it is on for the /upload/ directory

There is no need to edit php files. When editing the page in the WordPress dashboard, simply:

1. Click on Screen Options in the top right corner
2. tick discussions
3. Scroll down the page to the discussions section
4. Untick: Allow comments
5. Untick: Allow trackbacks and pingbacks on this page

That should be it.

Welcome. As long as it is working, it’s fine ??

If you are using Permalinks the .htaccess file from the old hosting should be moved to the new installation.

I agree with Michael here. Just to test this out, using an FTP client upload a file to the root of your website with just <h1>hello World!</h1>.

After uploading the file, try to access the website. If you can see the Hello World, then it is what Michael is saying, i.e. web hosting provider configuration issue.

You can read more about it here: https://codex.www.ads-software.com/FTP_Clients

So I would recommend you to download a free ftp client, such as filezilla; https://filezilla-project.org/

In the host section enter the URL of your website, in this case https://www.nandawp1.co.cc

the username and password you should have got them in the hosting provider introductory email. Alternatively most probably you can retrieve them from the Hosting provider cpanel.

Once you connect via ftp, then you can delete remote files and upload new files to your website.

Hope this helps and let me know if you need further assistance.

No problem. So basically at this stage, since it is still a new WordPress installation I would recommend you to simply delete what you have and re-install it from scratch. In this case you should:

Delete the current installation by:

1. Using the file manager from your hosting provider’s cpanel, delete the WordPress directory. Alternatively use FTP to login to your website and delete the files using ftp.

2. From your hosting provider cpanel, delete the database and username you created.

Install a new WordPress by:

1. Download the latest version of WordPress from: https://www.ads-software.com/download/

2. Extract it and upload all the files in the root of the website using FTP.

3. Create a new database and username from your hosting cpanel.

4. Access the website URL to proceed with the install.

That should be it.

Hi Lay,

You have to move all WordPress as explained in this document; https://codex.www.ads-software.com/Moving_WordPress

Since it is a new WordPress most probably it is easier to simply delete all the files form the /wordpress sub directory and re-install it in the root.

mmm.. that’s very strange then. Offhand do not know what could be it, but if you have time I would propose an experiment.

Install a copy of your blog on a local pc.

Get a backup of ALL the files and export the database to an sql file.

Try to post a page on the local blog installation. If you get the 404 error, get another backup of ALL the files and export the database to sql file again.

Compare all the files using compare tool and see what is the outcome. Would be interesting to know the result.