Troubleshoot log in connection after changing server and adding wildcard ssl - php

I've moved hosting companies and a website I built (somehow) and manage has stopped working after trying to log in, it goes to a blank page and loads a 500 error.
I know from some digging the fault lies here: $db = mysql_connect($hostname,$username,$password) or die("Database connection failed");
I have made sure I've changed the database connection details, I've tried changing the password.
I thought it might be linked with adding a wildcard ssl, but even removing it doesn't make any difference - although it still defaults to ssl.
Please can anyone help?
What have I missed please
As I said I've tried changing log in details,
When I try and log in with a correct user name & password, The url in the bar stays as the index page (where the screen is either blank or showing a 500 code), instead of progressing to the welcome page

Related

This site can’t be reached localhost refused to connect

I am getting a very strange error which I have no idea what is going on or how to fix. The strange thing is that I can connect to the /admin on my wordpress site. As soon as I try and view the site it crashes and I get this message - Any Ideas?
I have just downloaded a new copy of wordpress from the website. I go into php my admin create a database and username and password and matching what it is in wp-config file.
I then expect to login to localhost 8887 but as as soon as I hit that route I get to that site the port number disappears and I get this error message.
I have been experimenting with ssh tunneling this week so worried I have may have messed up some config but not really sure where to begin ? I dont think it is a wordpress problem more a networking problem?
In the picture localhost is written with double L-s. Isn't that the problem?
http:// locallhost..

Wordpress Error Establishing Database Connection

I have reinstalled phpAdmin (due to another issue) and updated wp-config with the correct names for DB, user name, password, etc, but now I cannot access the wordpress site (www.enablie.co.uk, www.enablie.co.uk/wp-admin or http://www.enablie.com/phpmyadmin).
I have tried adding the repair code
define('WP_ALLOW_REPAIR', true);
But still cannot access via : http://www.enablie.co.uk/wp-admin/maint/repair.php.
I am also getting this error when trying to access sql -
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
On Chrome is is showing a basic version of the site (broken styles) when not logged in, but get the EEDC as soon as try to log in. On Safari I have the EEDC immediately.
I assume I have just done something stupid, but most errors seem to suggest naming errors in the config file which I know is not the case. I have also checked the db still exists via mysql to ensure that there is not a problem there.
I assume that the re-install removed something from the overall settings that I now need to manually reconfigure, but I can't find any guidance that points me where to look so would appreciate some help on what I need to change. Much appreciated!
I rebooted by instance and that seemed to fix the issue.

Database can't connect on live server and blank page is displayed, all fine on Xampp

I am trying to setup a second instance of a website for testing purposes. I use the exact same files as the original version and all works fine when I test it on Xampp.
However, when I upload the files on the live server, something gets wrong. When the pages are loaded they appear as blank, there is no SQL error displayed, I tried this as well.
The code I use to connect to the DB is this one, if I remove it pages load correct, except that there is no DB connected. The DBHOST,DBUSER,DBPASS,DBNAME are all correct on live server as well:
$db = ADONewConnection('mysql');
$db->Connect(DBHOST,DBUSER,DBPASS,DBNAME) or die("Database not found! please install your application properly");
Also, all files in ADONewConnection library are fine, so it should be some setting on the live server that is different from Xampp and that I cannot think of.
I also tried this on another different hosting server and again no luck.
Any suggestions or ideas will be appreciated.

phpGrid "Error: Could not connect to the database" debugging

I have implemented a phpGrid that works in my dev environment but just keeps saying:
Error: Could not connect to the database
in production
I am logging failed attempts at MySQL connections in the logs on and if I put in a dodgy username and password in the conf.php files username/password it does not show up in the log (I've tested the log is working by attempting to connect with bad credentials via a terminal.
The host is just "localhost" I am using PDO connections elsewhere within my code and the are all connecting using "localhost" so I see now reason why this would be a problem.
In the conf.php I've turned on:
define('DEBUG', true);
And on my grid I have:
$dg -> enable_debug(true);
But I just keep getting this stupid error that tells me nothing about what's really going on...
It happened to me as well. Finally I was able to figure out. The reason is mySQLi was not enabled on the server. I enabled it and it works now.
Sorry, i cannot add a commant and sorry for my english.
If you are using PHP 5.5 try:
error_reporting=E_ALL^E_DEPRECATED
at top of the page for the time being.
For the files on your production machine: proof if they are still in utf-8 encoding

SQL Buddy + https(ssl) + nginx unable to login

I am setting up my very own server for the first time! Following the steps on the Ars Technica guide (http://arstechnica.com/information-technology/2012/12/web-served-part-4-get-your-database-on/).
However, when I try to login to SqlBuddy, I get immediately redirected back to the login page. I know that it can detect an incorrect login because I get an error message.
There are no errors in my php error log. I am also able to successfully see the phpinfo() page, so I know my php is setup properly.
Any ideas? It seems like not many people have problems with SQL buddy, I have tried googling and searching on here for similar problems.
Thanks!
Kevin
I had this same problem. Investigating, I found that the sessions were expiring instantly.
Memcached was not configured properly, the typo in my case was in php-sock.conf.
The correct text shoulds be:
server unix:/var/run/php5-fpm.sock;

Categories