mysql_connect(): user 'name'@'host'拒绝访问

当您连接到无效或缺少凭据(用户名/密码)的MySQL/MariaDB服务器时，会出现此警告。所以这通常不是代码问题，而是服务器配置问题。

See the manual page on mysql_connect("localhost", "user", "pw") for examples. Check that you actually used a $username and $password. It's uncommon that you gain access using no password - which is what happened when the Warning: said (using password: NO). Only the local test server usually allows to connect with username root, no password, and the test database name. You can test if they're really correct using the command line client: mysql --user="username" --password="password" testdb Username and password are case-sensitive and whitespace is not ignored. If your password contains meta characters like $, escape them, or put the password in single quotes. Most shared hosting providers predeclare mysql accounts in relation to the unix user account (sometimes just prefixes or extra numeric suffixes). See the docs for a pattern or documentation, and CPanel or whatever interface for setting a password. See the MySQL manual on Adding user accounts using the command line. When connected as admin user you can issue a query like: CREATE USER 'username'@'localhost' IDENTIFIED BY 'newpassword'; Or use Adminer or WorkBench or any other graphical tool to create, check or correct account details. If you can't fix your credentials, then asking the internet to "please help" will have no effect. Only you and your hosting provider have permissions and sufficient access to diagnose and fix things. Verify that you could reach the database server, using the host name given by your provider: ping dbserver.hoster.example.net Check this from a SSH console directly on your webserver. Testing from your local development client to your shared hosting server is rarely meaningful. Often you just want the server name to be "localhost", which normally utilizes a local named socket when available. Othertimes you can try "127.0.0.1" as fallback. Should your MySQL/MariaDB server listen on a different port, then use "servername:3306". If that fails, then there's a perhaps a firewall issue. (Off-topic, not a programming question. No remote guess-helping possible.) When using constants like e.g. DB_USER or DB_PASSWORD, check that they're actually defined. If you get a "Warning: Access defined for 'DB_USER'@'host'" and a "Notice: use of undefined constant 'DB_PASS'", then that's your problem. Verify that your e.g. xy/db-config.php was actually included and whatelse. Check for correctly set GRANT permissions. It's not sufficient to have a username+password pair. Each MySQL/MariaDB account can have an attached set of permissions. Those can restrict which databases you are allowed to connect to, from which client/server the connection may originate from, and which queries are permitted. The "Access denied" warning thus may as well show up for mysql_query calls, if you don't have permissions to SELECT from a specific table, or INSERT/UPDATE, and more commonly DELETE anything. You can adapt account permissions when connected per command line client using the admin account with a query like: GRANT ALL ON yourdb.* TO 'username'@'localhost'; If the warning shows up first with Warning: mysql_query(): Access denied for user ''@'localhost' then you may have a php.ini-preconfigured account/password pair. Check that mysql.default_user= and mysql.default_password= have meaningful values. Oftentimes this is a provider-configuration. So contact their support for mismatches. Find the documentation of your shared hosting provider: e.g. HostGator, GoDaddy, 1and1, DigitalOcean, BlueHost, DreamHost, MediaTemple, ixWebhosting, lunarhosting, or just google yours´. Else consult your webhosting provider through their support channels. Note that you may also have depleted the available connection pool. You'll get access denied warnings for too many concurrent connections. (You have to investigate the setup. That's an off-topic server configuration issue, not a programming question.) Your libmysql client version may not be compatible with the database server. Normally MySQL and MariaDB servers can be reached with PHPs compiled in driver. If you have a custom setup, or an outdated PHP version, and a much newer database server, or significantly outdated one - then the version mismatch may prevent connections. (No, you have to investigate yourself. Nobody can guess your setup).

更多的引用:

mysql服务器错误:mysql用户无法访问root用户 mysql_connect():拒绝访问 mysql_select_db()拒绝访问用户" @'localhost'(使用密码:NO) PHPMyAdmin拒绝用户“root”@“localhost”的访问

顺便说一句，你可能不想再使用mysql_*函数了。新来者经常迁移到mysqli，然而这也一样乏味。相反，阅读PDO和准备好的语句。 $db =新PDO("mysql:主机=localhost;dbname=testdb"， "用户名"，"密码");

致命错误:调用未定义的函数XXX

在尝试调用尚未定义的函数时发生。常见的原因包括缺少扩展和包含，有条件的函数声明，函数声明中的函数或简单的拼写错误。

例1 -条件函数声明

$someCondition = false;
if ($someCondition === true) {
    function fn() {
        return 1;
    }
}
echo fn(); // triggers error

在这种情况下，fn()将永远不会被声明，因为$someCondition不为真。

例2 -函数声明中的函数

function createFn() 
{
    function fn() {
        return 1;
    }
}
echo fn(); // triggers error

在这种情况下，只有在调用createFn()时才声明fn。注意，后续调用createFn()将触发一个关于重新声明现有函数的错误。

在PHP内置函数中也可以看到这种情况。尝试在官方手册中搜索该函数，并检查它属于哪个“扩展”(PHP模块)，以及哪些版本的PHP支持它。

如果缺少扩展，请安装该扩展并在php.ini中启用它。请参阅PHP手册中的安装说明，以了解函数在扩展中的显示。你也可以使用你的包管理器(例如Debian或Ubuntu中的apt, Red Hat或CentOS中的yum)，或共享托管环境中的控制面板来启用或安装扩展。

如果该函数是在您正在使用的PHP的新版本中引入的，那么您可以在手册或评论部分中找到替代实现的链接。如果它已从PHP中删除，请查找有关原因的信息，因为可能不再需要它了。

如果缺少include，请确保在调用函数之前包含声明该函数的文件。

如果出现错别字，请改正错别字。

相关问题:

https://stackoverflow.com/search?q=Fatal+error%3A+Call+to+undefined+function

解析错误:语法错误，意外的T_PAAMAYIM_NEKUDOTAYIM

范围解析操作符也被称为“Paamayim Nekudotayim”，源自希伯来语פייםנקדיים”。意思是“双冒号”。

如果您无意中在代码中放入::，则通常会发生此错误。

相关问题:

参考:PHP语法错误;以及如何解决这些问题? PHP中两个冒号是什么意思? 在PHP中::(双冒号)和->(箭头)之间的区别是什么? 意外T_PAAMAYIM_NEKUDOTAYIM，期望T_NS_Separator

文档:

范围解析运算符(::)

解析错误:语法错误，意外的T_XXX

当你在意想不到的地方有T_XXX令牌，不平衡的(多余的)括号，在php.ini中使用短标记而没有激活它，以及更多情况时发生。

相关问题:

参考:PHP语法错误;以及如何解决这些问题? 解析错误:语法错误:意外的“{” 解析错误:语法错误，在我的PHP代码文件意外结束 解析错误:语法错误，意外的“<”-修复? 解析错误:语法错误，意外的'?'

如需进一步帮助，请参阅:

http://phpcodechecker.com/ -它确实为你的语法问题提供了一些更有用的解释。

HTTP错误500 -内部服务器错误

HTTP状态代码500和典型的Apache或浏览器警告是一个非常广泛的消息。这不是实际的错误。要弄清楚是web服务器配置错误(.htaccess)还是PHP致命错误，你必须查看error.log。

你通常可以在下面找到webservers日志:

/var/log/apache2 on Linux servers, often used for local and virtual hosts. /var/www/_user12345_/logs or similar on shared hosting plans. Usually there's a logs/ directory alongside each htdocs/ folder. C:\xampp\apache\logs\error.log for WAMP/XAMPP distributions of Apache+PHP. Alternatively just use a file search feature to locate anything called "error.log". Or look into your Apache httpd.conf and its ErrorLog directive. /var/log/nginx/nginx_error.log for NGINX. C:\inetpub\logs\LogFiles for IIS. Luckily this is uncommon still, but journalctl -r -u apache2.service could also hold parts of the log on Linux setups.

它是一个文本文件。搜索与错误时间最接近的条目，并使用错误消息的重要部分(从“PHP error:…”到“in line…”)进行进一步的google搜索。

[Mon 22:10] [:error] [pid 12345] [client 127.0.0.1] FastCGI: server "/fcgi/p73" stderr: PHP message:PHP error: Unfiltered inputvariable $_JSON['pokestop_lng'] in filyfile.php on line 845

对于FPM设置，你经常会看到致命的PHP错误。而旧的mod_php(共享主机)配置经常混合警告和通知(通常也值得检查)。

如果没有配置为使用系统或Apache日志机制，您可能还需要查看PHP的error.log。一般来说，保留默认值并启用error_display + error_reporting来显示具体的错误会更简单。HTTP 500全捕获页面不过是PHP死机白屏幕的一个变种。

参见:

500内部服务器错误的php文件，而不是html 我怎么能让PHP显示错误，而不是给我500内部服务器错误 如何在IIS7上显示和记录PHP错误? 如何修复WordPress内部服务器的500个错误

警告:除以零

警告信息“除零”是新PHP开发人员最常被问到的问题之一。此错误不会导致异常，因此，一些开发人员偶尔会通过在表达式之前添加错误抑制操作符@来抑制警告。例如:

$value = @(2 / 0);

但是，就像任何警告一样，最好的方法是追踪警告的原因并解决它。警告的原因将来自任何实例，其中你试图除以0，一个变量等于0，或一个变量没有被分配(因为NULL == 0)，因为结果将是'undefined'。

要纠正此警告，您应该重写表达式以检查值是否为0，如果为0，则执行其他操作。如果值为0，要么不除法，要么将值改为1，然后再除法，这样除法的结果相当于只除以额外的变量。

if ( $var1 == 0 ) { // check if var1 equals zero
    $var1 = 1; // var1 equaled zero so change var1 to equal one instead
    $var3 = ($var2 / $var1); // divide var1/var2 ie. 1/1
} else {
    $var3 = ($var2 / $var1); // if var1 does not equal zero, divide
}

相关问题:

警告:除以零 使用PHP和MySQL 在WordPress主题中除以零错误 如何抑制“除零”错误 如何用0求除法?