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"， "用户名"，"密码");

警告:数组到字符串的转换

注意:数组到字符串的转换

(PHP 7.4之前的一个通知，PHP 8.0之后的一个警告)

如果你试图将数组视为字符串，就会发生这种情况:

$arr = array('foo', 'bar');

echo $arr;  // Notice: Array to string conversion
$str = 'Something, ' . $arr;  // Notice: Array to string conversion

数组不能简单地与字符串回显或连接，因为结果没有很好地定义。PHP将使用字符串“Array”来代替数组，并触发通知，指出这可能不是预期的结果，您应该检查这里的代码。你可能想要这样的东西:

echo $arr[0];  // displays foo
$str = 'Something ' . join(', ', $arr); //displays Something, foo, bar

或者循环数组:

foreach($arr as $key => $value) {
    echo "array $key = $value";
    // displays first: array 0 = foo
    // displays next:  array 1 = bar
}

如果这个通知出现在您意想不到的地方，这意味着您认为是字符串的变量实际上是一个数组。这意味着你的代码中有一个错误，使这个变量成为一个数组，而不是你期望的字符串。

致命错误:允许的内存大小XXX字节已耗尽(已尝试分配XXX字节)

没有足够的内存来运行脚本。PHP已达到内存限制并停止执行。这个错误是致命的，脚本停止。内存限制的值可以在php.ini文件中配置，也可以使用ini_set('memory_limit'， '128 M');在脚本中(将覆盖php.ini中定义的值)。内存限制的目的是防止一个PHP脚本占用所有可用内存，导致整个web服务器瘫痪。

The first thing to do is to minimise the amount of memory your script needs. For instance, if you're reading a large file into a variable or are fetching many records from a database and are storing them all in an array, that may use a lot of memory. Change your code to instead read the file line by line or fetch database records one at a time without storing them all in memory. This does require a bit of a conceptual awareness of what's going on behind the scenes and when data is stored in memory vs. elsewhere.

如果在脚本没有执行内存密集型工作时发生此错误，则需要检查代码以查看是否存在内存泄漏。memory_get_usage函数是您的朋友。

相关问题:

所有“Fatal error: Allowed memory size of XXX bytes exhausted”问题

代码不运行/我的PHP代码的某些部分被输出

如果你的PHP代码没有任何结果，或者你在网页中看到你的PHP源代码输出的部分文字，你可以很确定你的PHP实际上没有被执行。如果在浏览器中使用“查看源代码”，则可能会看到完整的PHP源代码文件。因为PHP代码嵌入在<?php ?>标记时，浏览器将尝试将它们解释为HTML标记，结果可能看起来有些混乱。

要真正运行PHP脚本，您需要:

执行脚本的web服务器 将文件扩展名设置为.php，否则web服务器不会将其解释为* 通过web服务器访问你的。php文件

*除非你重新配置，否则一切都可以配置。

最后一点尤其重要。只需双击该文件，就可以在浏览器中使用如下地址打开它:

file://C:/path/to/my/file.php

这完全绕过了您可能正在运行的任何web服务器，并且文件没有得到解释。你需要在你的web服务器上访问文件的URL，可能是这样的:

http://localhost/my/file.php

您可能还想检查是否使用了短的打开标记<?而不是<?php和您的php配置已关闭短打开标记。

还可以看到PHP代码没有被执行，而是代码显示在页面上

警告:mysql_fetch_array()期望参数1是resource, boolean给定

首先，也是最重要的:

请不要在新代码中使用mysql_*函数。它们不再被维护，并且已被正式弃用。看到红框了吗?转而学习准备语句，并使用PDO或MySQLi——本文将帮助您选择哪一种。如果您选择PDO，这里有一个很好的教程。

当您试图从mysql_query的结果中获取数据但查询失败时，就会发生这种情况。

这是一个警告，不会停止脚本，但会使您的程序出错。

您需要检查mysql_query返回的结果by

$res = mysql_query($sql);
if (!$res) {
   trigger_error(mysql_error(),E_USER_ERROR);
}
// after checking, do the fetch

相关问题:

Mysql_fetch_array()期望参数1是resource，在select中给出的布尔值 所有“mysql_fetch_array()期望参数1是资源，布尔给定”的问题

相关的错误:

警告:[function]期望参数1是给定的布尔值

其他mysql*函数也期望mysql结果资源作为参数将出于同样的原因产生相同的错误。

警告:open_basedir限制生效

此警告可以与与文件和目录访问相关的各种函数一起出现。它警告一个配置问题。

当它出现时，这意味着已禁止访问某些文件。

警告本身不会破坏任何东西，但如果文件访问被阻止，脚本通常无法正常工作。

修复方法通常是更改PHP配置，相关设置称为open_basedir。

有时使用了错误的文件或目录名称，解决方法是使用正确的名称。

相关问题:

Open_basedir限制生效。文件(/)不在允许路径内: 所有PHP的“警告:open_basedir限制在有效”的查询在Stackoverflow