Julian Fox (greataussiepie)

I have two WordPress sites, one on a Litespeed server with netregistery.com.au and this server gets those errors. Another WordPress site on a cPanel regular hosting server with melbourneit.com.au and that does not get the errors. strange.

FYI: either way Litespeed and netregistry are still heaps faster than melbourneit.

I just looked at my WordPress and i never actually noticed by i get the same group of errors. However despite the errors being there i can still search and apply feature filters to those searches, everything seems to work fine. haven’t done much testing tho.

No sorry I can’t really help you from here, hopefully your host has a clue or maybe someone else around here will.

Good luck ??

Also do you have any security plugins installed that may be blocking individual computer IP addresses that are sending too many requests?

try limiting yourself to 2 tabs and see if that helps.

How long ago did you setup your domain name and server? This sort of sounds like a issue with a new website and DNS propagation taking time.

Depending on the setup your host has, you may have to manually create the database using phpmyadmin or your hosts database manager. And then during the WordPress setup enter the same database name as you give your database when manually creating it using phpmyadmin.

I have run into this issue from time to time and it was because i was trying to connect to a database that wasn’t there. and by Database i mean the database not the database host.

This may or may not be your problem.

Hope this helps ??

Hi Kyte,

Could you share some details like the name of your host? what server are is your website on, apache, IIS? what version of PHP is your server running? these things will help more experienced WordPress’ers help you, cause this sounds like a server configuration problem.

that sounds curious, this does sound like a problem your host might have to solve. its a good idea to send them an email about it.

It sounds like php display errors is turned off which would explain why you don’t get any other info, this is a server side setting that your host controls.

It could be possible that your host needs to upgrade its version of PHP or that perhaps it recently did upgrade and has to change a few settings to make all the features in WordPress work properly.

??

Thanks bp-help ??

happy WordPressing

oh great that sounds good, keep posting here if you have anymore snags with the reinstall.

let us know how it goes and dont forget to mark the topic as resolved ??

happy to help ??

In regards to the .htaccess file, i should have asked first if you website is running on an Apache server or a Microsoft IIS server, Apache uses .htaccess and IIS uses a file called Web.config, i am unfamiliar with IIS servers so you may have to start a new topic with error 401.1 in the title to prompt someone with the necessary knowledge to help you.

Deleting the Web.config file on a IIS server environment may or may not be a good idea, i do not know sorry.

If you are on Apache Using an FTP client like FileZilla or your cPanel file manager you can find the .htaccess file in the the wwwroot directory, the same directory that wp-config.php can be found.

If you start another topic saying something like ‘401.1 error – my site disappeared what do i do?’ and then explain careful what server you are running WordPress and any WordPress or server settings that you changed recently before the site stopped working. If i can help i will reply to that topic ASAP otherwise im sure someone who can help will notice it soon.

Hope that helps ?? Good luck

Sorry i could have been more helpful on explaining what a prefix is. a prefix is just simply some letters or numbers that are pre fixed on to the front of everything. this allows WordPress to identify data in the database, so that it knows what data it owns and what data to leave alone.

Sorry i realised my link didn’t have a closing a href tag. the link in my previous comment should be there now.

First, i just want to double check you have made a backup of your Database and of your files before you do anything? ?? if you havent do this.

Yes, if you just use the same old information everything should be ok, however since you are trying to troubleshoot a problem that caused your website to disappear it may be a good idea to try some other troubleshooting tricks first,
for instance back up a copy of your .htaccess file and then delete it from the server and see if your website starts working again. I get server 500 internal error and deleting .htaccess usually restores the website allowing me to further investigate.

If the problem is not with the .htaccess file, there is a chance the problem may be inside the database itself, in which case using the same default settings probably won’t fix the problem.

Prefix explanation:

check out the image i linked below, it shows the WordPress setup screen. Here it asks for a Table Prefix, by default it is set to wp_

the second link is an image of phpMyAdmin and you can see all of the tables that WordPress uses to store data, they all start with the prefix wp_.

If you are unsure, it is best to first make a backup of your database from phpMyAdmin, and a backup of your WordPress files from FTP.

WordPress setup screen

phpMyAdmin WordPress tables

Hi, in the past when iv been playing with some settings and i get a server 500 internal error, i just delete the .htaccess file and everything seems to work again. I then reverse the settings and then get WordPress to re-write a new .htacess file with the new settings.

to get WordPress to re-write a .htaccess file: go to WordPress permalinks settings page and change it to the default setting and click save and then change it back to your desired setting, doing this prompts WordPress to re-write the .htaccess file.

Creating and editing .htaccess file – WordPress codex

Hi Technobimbo,

If you use the same table prefix it will use the data it finds, it will not overwrite.

It is possible to install a fresh WordPress and use your current database, during the installation, give your WordPress install a different prefix from the one currently in your database.

After the installation is complete, if you look at your database using phpmyadmin you will notice there is 2 sets of tables for everything. updated: One set of tables with your old prefix and one set of tables with your new and different prefix. you can switch between both by editing the wp-config.php file.

When you are ready you can edit the wp-config file to use the prefix of your old database and this will tell WordPress to start using your old WordPress data.

Hope this helps ??