vBulletin 3 is end of life and will not be receiving future development. Warning: vBulletin 3.8.11 is not compatible with PHP 7.2.0 or higher.
Welcome to the vBulletin support forums! In our community forums you can receive professional support and assistance with any issues you might have with your vBulletin Products.
If you are having problems posting in the relevant areas for your software, please see this topic.
Upgrade to vBulletin 5
We're pleased to announce a special promotion for upgrading your vBulletin 3/4 sites to vBulletin 5. From now until December 31st, we are offering vBulletin 5 license upgrades at $169 each. This promotion is available to all vBulletin 3 (owned) and vBulletin 4 license holders, entitling you to the latest version of vBulletin 5.
If you would like to purchase this upgrade, please log into the vBulletin Members Area and use Promo Code: vB5UPGRADE during checkout to apply the discount.
It's giving me the following error during step 2 of the installation:
Step 2) Connect to the database
Attempting to attach to database
Error description: mysql_connect() [function.mysql-connect]: Can't connect to local MySQL server through socket '/usr/local/mysql-5.0/data/mysql.sock' (2) /home/content/d/f/w/dfwcharity/html/forums/includes/class_core.php on line 311 The database has failed to connect because you do not have permission to connect to the server. Please confirm the values entered in the 'includes/config.php' file.
I just spent 45 minutes on the phone with my webhost, and they assure me they are able to access my databases on their end without any issues. I followed directions on editing the config file... What am I missing?
The four items that are the ones that cause connection errors during the installation process are:
MySQL Server Name
Database Name
User Name
Password
Only you and your host know what the correct information for these will be.
I've set up an entirely new database and entered all of the new information into the config file. Still nothing.
I'm convinced at this point that it's something wrong on the server side. The MySQL communication error I'm getting with vB is the same error I was getting with phpBB3 after almost a year of fairly smooth running. Now the difficult part is going to be convincing them to even take it seriously enough to put some effort into fixing it.
It helps to have friends that know what they're doing. I was able to get a friend of mine to help me through the process, so it's up and running well.
I did have some issues while transfering the old phpBB3 users to vB. Instead of moving my "Registered Users" group to vB's RU group, it made a new group for them titled "REGISTERED" where the entire group was permabanned. Thankfully I found that out before I went live with it.
It would be helpful to others if you would inform us what you found and what you changed...
I changed out the least reliable part of any operation; the operator.
I can't really say what was changed as I didn't do it myself, hence the previous comment about having friends that know what they're doing.
I asked him what it was that I had done wrong, and I'm sure he gave me the answer. I either didn't understand it (strong possibility), I forgot it (also a strong possibility), or a combination of the two (most likely what happened). Wish I could be of more help to others with the same issues. Now if it were a question about why someone's BMW is running rough, I can help... This whole database stuff is well outside my area of expertise.
widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Working...
X
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also consent to the transfer of your data to our servers in the United States, where data protection laws may be different from those in your country.
Comment