Apache Friends Support Forum

I have installed xampp-windows-x64-8.2.12-0-VS16 today because my old one which is xampp-windows-x64-8.1.10-0-VS16 has some problems.

Today I installed XAMPP seveal times today because Something wrong, I think, in my changing password.

http://127.0.0.1/phpmyadmin/ is well open before I change the password of mySQL through phpMyAdmin.
As I have changed the password using Change password button in phpMyAdmin. it says like the following(blue color font is translation from my mother language to English).

오류 error
MySQL 메시지message : 문서documents

연결할 수 없습니다Can't connect: 잘못된 설정wrong configuration.

mysqli::real_connect(): (HY000/1045): Access denied for user 'root'@'localhost' (using password: NO)

phpMyAdmin이 MySQL 서버에 접속하려 했으나 실패했습니다phpMyAdmin tried to connect MySQL server, but failed.
서버가 연결을 거부했습니다Server rejected the connection. 당신의 설정의 호스트, ID, 패스워드가 맞게 입력됐는지, 또는 MySQL 서버의 관리자가 제공해 준 정보를 맞게 입력했는지 확인하세요Confirm the host, ID, password are all correct with your config or server manager given.

when I open http://127.0.0.1/phpmyadmin/, I like to see the login page instead of the error message in the quote above.

How can I see the login page?

I can install XAMPP again, then how can I change mySQL Password correctly?

Hi,
I installed XAMPP on macOS Sonoma 14.2.1. At this stage I can access on the web /localhost/myphpadmin showing the root user has blank password. Using command line, I created a database, piwigo. Then I used /localhost/myphpadmin to change the password to the database. Then, I loaded mysql database from my backup. I placed the piwigo server on htdocs (server and database has the same name). After some write permission corrections, my piwigo server (with all my photo albums) is working. Now I want to go in /localhost/myphpadmin but it gives me error

Code: Select all

Error
MySQL said: Documentation

Cannot connect: invalid settings.
 mysqli::real_connect(): (HY000/1045): Access denied for user 'pma'@'localhost' (using password: NO)
 Connection for controluser as defined in your configuration failed.
 mysqli::real_connect(): (HY000/1045): Access denied for user 'root'@'localhost' (using password: NO)
 phpMyAdmin tried to connect to the MySQL server, and the server rejected the connection. You should check the host, username and password in your configuration and make sure that they correspond to the information given by the administrator of the MySQL server.

Since the macOS manager-osx does not have features of the windows control panel, I do not know how to correct this.

Your help is much appreciated.

Edit, If I can change the password back to blank, maybe I can access /localhost/myphpadmin. But I searched and the methods used is on the control panel which manager-osx does not have. I cannot find any command line to change XAMMP mysql password.

edit2. I found the command and use this to alter the root password

Code: Select all

/Applications/XAMPP/bin/mysql --user=root --password -e "Alter User 'root'@'localhost' IDENTIFIED BY '""'"

Now I cannot access my database, since I have changed the password to "". What can I do in phpmyadmin to change the password back but also allow me to access /localhost/phpmyadmin?

KonradZ wrote:hab mir mal XAMPP auf meinen Win10-Rechner installiert und dazu noch den APACHE-Server

Das ist eine ganz schlechte Idee. Xampp bringt schon den Apache Server mit und man kann nur einen davon laufen lassen. Da ist also schon einmal zu fragen, welcher Apache läuft letztendlich, denn beide zusammen geht nicht. Wieso nochmal Apache, wenn Du schon Xampp hast?

"Internal Error: SQLSTATE[HY000] [1045] Access denied for user 'kanboard_rw'@'localhost' (using password: YES)"

Das bedeutet, dass der User kanboard_rw nicht in der SQL Datenbank gefunden wird. Jetzt wissen wir natürlich nicht, ob es diesen User überhaupt gibt (bei Xampp ist er jedenfalls nicht dabei) und wir wissen nicht einmal, in welcher Infrastruktur diese "KANBOARD" installiert wurde. KANBOARD ist auch hier bekannt, das ist kein Xampp Produkt.

Am besten schaust Du erst einmal, dass Du nur ein blitzsauberes Xampp installierst und darauf dieses KANBOARD. Dann kann man wenigstens auschließen, dass dieses zusätzliche Apache dazwischen funkt.

Hallo und guten Tag Zusammen,

hab mir mal XAMPP auf meinen Win10-Rechner installiert und dazu noch den APACHE-Server und das KANBOARD. Das funktioniert auch alles nach der Installation.
Aber immer wenn ich einen Neustart des Rechners gemacht hab, kommt statt der KANBOARD-Seite die folgende Fehlermeldung im Browser:

"Internal Error: SQLSTATE[HY000] [1045] Access denied for user 'kanboard_rw'@'localhost' (using password: YES)"

Das wiederholt sich nach einer nochmaligen Installation.
Woran kann das denn liegen ?

Viele Grüße
KonradZ

Hello
in phpmyadmin I wanted to change the password BD and I got an error and now impossible to connect to phpMyAdmin
I use XAMPP 3.3.0

error
MySQL replied: Documentation
Unable to connect: incorrect settings.
mysqli::real_connect(): (HY000/1045): Access denied for user 'root'@'localhost' (using password: YES)
phpMyAdmin attempted to connect to the MySQL server, and the server rejected the connection. Please check the values of host, username and password in the configuration and ensure that they match the information provided by the MySQL server administrator.

thank you for help

Hi. I tried to logon to phpmyadmin and got this error

mysqli_real_connect(): (HY000/1045): Access denied for user 'root'@'localhost' (using password: NO)

I have it setup as user='root' and no password.
Upon checking my config.inc.php file this is whats there

/* Authentication type and info */
$cfg['Servers'][$i]['auth_type'] = 'config';
$cfg['Servers'][$i]['user'] = 'root';
$cfg['Servers'][$i]['password'] = '';
$cfg['Servers'][$i]['extension'] = 'mysqli';
$cfg['Servers'][$i]['AllowNoPassword'] = true;
$cfg['Lang'] = '';

and at the start of my.ini is

[client]
#password = my-password
port = 3306
socket = "C:/xampp/mysql/mysql.sock"

I am assuming that both are correct. (from what I have read)
I also read the you can put cookie in

$cfg['Servers'][$i]['auth_type'] = 'cookie';

and myphpadmin will ignore the values of "user" and" password". So I changed my config.inc.php file to

/* Authentication type and info */
$cfg['Servers'][$i]['auth_type'] = 'cookie';
$cfg['Servers'][$i]['user'] = 'root';
$cfg['Servers'][$i]['password'] = 'thepassword';
$cfg['Servers'][$i]['extension'] = 'mysqli';
$cfg['Servers'][$i]['AllowNoPassword'] = false;
$cfg['Lang'] = '';

and got error code

mysqli_real_connect(): (HY000/1045): Access denied for user 'root'@'localhost' (using password: YES)

I have now changed it back to the settings as it was.

What else can I try. thanks

You are right. Maria DB had already been started. But it is still not working: Since the crash I get a database connection error which hadn't been there before. And I don't have it in my live system either.

I entered your command again after stopping Maria DB. Maybe the response is more helpful for you now.

# mysqld --defaults-file=mysql\bin\my.ini --standalone --console
2022-05-24 11:50:52 0 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
2022-05-24 11:50:52 0 [Note] mysqld (mysqld 10.4.17-MariaDB) starting as process 2376 ...
InnoDB: using atomic writes.
2022-05-24 11:50:52 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2022-05-24 11:50:52 0 [Note] InnoDB: Uses event mutexes
2022-05-24 11:50:52 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-05-24 11:50:52 0 [Note] InnoDB: Number of pools: 1
2022-05-24 11:50:52 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-05-24 11:50:52 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2022-05-24 11:50:52 0 [Note] InnoDB: Completed initialization of buffer pool
2022-05-24 11:50:52 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=141277
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=136, page number=2] with future log sequence number 487402904
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1071] with future log sequence number 487549839
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=286] with future log sequence number 495731927
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=943] with future log sequence number 495731927
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=285] with future log sequence number 495731883
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=906] with future log sequence number 495731883
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=282] with future log sequence number 495731839
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1078] with future log sequence number 495731839
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=281] with future log sequence number 495731795
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=331] with future log sequence number 495731795
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=280] with future log sequence number 495731751
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=330] with future log sequence number 495731751
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=279] with future log sequence number 495731691
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=329] with future log sequence number 495731691
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=277] with future log sequence number 495731647
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1077] with future log sequence number 495731647
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=276] with future log sequence number 495731603
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=327] with future log sequence number 495731603
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=275] with future log sequence number 495731559
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=326] with future log sequence number 495731559
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=274] with future log sequence number 495731515
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=325] with future log sequence number 495731515
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=271] with future log sequence number 495731471
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1070] with future log sequence number 495731471
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=270] with future log sequence number 495731427
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=901] with future log sequence number 495731427
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=269] with future log sequence number 495731383
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=942] with future log sequence number 495731383
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=268] with future log sequence number 495731339
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=941] with future log sequence number 495731339
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=266] with future log sequence number 495731295
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=324] with future log sequence number 495731295
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=265] with future log sequence number 495731251
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1064] with future log sequence number 495731251
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=264] with future log sequence number 495731191
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=323] with future log sequence number 495731191
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=263] with future log sequence number 495731147
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=900] with future log sequence number 495731147
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=261] with future log sequence number 495731103
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=320] with future log sequence number 495731103
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=260] with future log sequence number 495731059
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1087] with future log sequence number 495731059
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=259] with future log sequence number 495731015
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1086] with future log sequence number 495731015
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=258] with future log sequence number 495730971
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1085] with future log sequence number 495730971
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=256] with future log sequence number 495730927
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1084] with future log sequence number 495730927
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=255] with future log sequence number 495730883
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1061] with future log sequence number 495730883
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=254] with future log sequence number 495730839
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1083] with future log sequence number 495730839
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=253] with future log sequence number 495730795
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1072] with future log sequence number 495730795
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=252] with future log sequence number 495730751
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=898] with future log sequence number 495730751
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=251] with future log sequence number 495730707
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=897] with future log sequence number 495730707
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=249] with future log sequence number 495730647
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1069] with future log sequence number 495730647
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=248] with future log sequence number 495730603
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1068] with future log sequence number 495730603
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=247] with future log sequence number 495730559
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=896] with future log sequence number 495730559
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=246] with future log sequence number 495730515
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1067] with future log sequence number 495730515
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=244] with future log sequence number 495730471
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=934] with future log sequence number 495730471
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=242] with future log sequence number 495730427
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1058] with future log sequence number 495730427
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=241] with future log sequence number 495730383
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=933] with future log sequence number 495730383
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=240] with future log sequence number 495730339
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1057] with future log sequence number 495730339
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=239] with future log sequence number 495730295
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1046] with future log sequence number 495730295
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=238] with future log sequence number 495730251
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=1045] with future log sequence number 495730251
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=236] with future log sequence number 495729524
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=912] with future log sequence number 495729524
2022-05-24 11:50:52 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=322] with future log sequence number 495730251
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=7] log sequence number 495719698 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=3] log sequence number 341467173 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=2] log sequence number 492271661 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=4] log sequence number 491831728 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=11] log sequence number 385228232 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=1047] log sequence number 385228232 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=1] log sequence number 341467173 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=6] log sequence number 493353934 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=45] log sequence number 493354051 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=46] log sequence number 493354090 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=1082] log sequence number 493354090 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=47] log sequence number 493354129 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=347] log sequence number 493354129 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=48] log sequence number 493354168 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=348] log sequence number 493354168 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=49] log sequence number 487426155 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=383] log sequence number 487426155 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=50] log sequence number 487426194 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=349] log sequence number 487426194 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=51] log sequence number 487426233 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=474] log sequence number 487426233 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=52] log sequence number 431022990 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=350] log sequence number 431022990 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=53] log sequence number 487426432 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=54] log sequence number 487426471 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=351] log sequence number 487426471 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=55] log sequence number 487426527 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=352] log sequence number 487426527 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=56] log sequence number 487426582 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=353] log sequence number 487426582 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=57] log sequence number 487426688 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=384] log sequence number 487426688 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=58] log sequence number 487426727 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=354] log sequence number 487426727 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=59] log sequence number 431023201 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=355] log sequence number 431023201 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=60] log sequence number 487428004 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=356] log sequence number 487428004 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=61] log sequence number 487428658 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=385] log sequence number 487428658 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=62] log sequence number 487429241 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=357] log sequence number 487429241 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=63] log sequence number 487429512 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=358] log sequence number 487429512 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=192] log sequence number 487430096 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=359] log sequence number 487430096 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=193] log sequence number 493357522 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=194] log sequence number 493358096 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=195] log sequence number 493358140 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=923] log sequence number 493358140 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=196] log sequence number 493358184 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=362] log sequence number 493358184 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=197] log sequence number 493358228 is in the future! Current system log sequence number 141295.
2022-05-24 11:50:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
.... abbreviated rf1234
2022-05-24 11:50:52 0 [Note] Reading of all Master_info entries succeeded
2022-05-24 11:50:52 0 [Note] Added new Master_info '' to hash table
2022-05-24 11:50:52 0 [Note] mysqld: ready for connections.
Version: '10.4.17-MariaDB' socket: '' port: 3306 mariadb.org binary distribution

Hallo an alle. Ein frohes 2022.
Ich habe einen Fehler auf meinem MariaDB-10-4 gemacht, als ich versuchte, phpmyadmin zu sichern.
Auf der Registerkarte phpmyadmin Privileges, habe ich die Sicherheit auf SSL geändert, jedoch ohne die Zertifikate zuvor zu erstellen.
Ich habe jetzt nur mit einem readonly Benutzer Zugriff auf mysql.
Aber ausser root@localhost, habe ich auch root@127.0.0.1 als Benutzer zu verfügung, und mit dem vorteil
Das Problem ist dass ich mit

Code: Select all

mysql -u root -h 127.0.0.1 --protocol=tcp

immer den Fehler

Code: Select all

ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)

bekomme.
Ich habe viel recherchiert, ohne dass eine Lösung funktioniert.
Frage: Wie erzwinge ich den mysql-Befehl, sich mit root@127.0.0.1 anzumelden?
MfG
carliedu

Ok, ich habe jetzt wieder die User gelöscht.


https://ibb.co/4sFZ9pL

Das ist der Aktuelle Fehler aus dem Error-Log-File:

Code: Select all

[01-Nov-2021 22:29:45 Europe/Berlin] PHP Warning:  mysqli::__construct(): (HY000/1045): Access denied for user ''@'localhost' (using password: NO) in C:\xampp\htdocs\quickTest\mobileConnect\connect.php on line 15
[01-Nov-2021 22:29:45 Europe/Berlin] PHP Fatal error:  Uncaught Error: mysqli object is already closed in C:\xampp\htdocs\quickTest\mobileConnect\connect.php:17
Stack trace:
#0 C:\xampp\htdocs\quickTest\mobileConnect\connect.php(17): mysqli->set_charset('utf8')
#1 C:\xampp\htdocs\quickTest\mobileConnect\index.php(3): require('C:\\xampp\\htdocs...')
#2 {main}
  thrown in C:\xampp\htdocs\quickTest\mobileConnect\connect.php on line 17


Wenn noch irgendwelche Informationen fehlen die weiterhelfen könnten, würde ich sie raussuchen. Vielleicht könntest du diese Abfrage nachstellen, wenn du ein Windows-PC und ein Android-Phone da hättest. Wäre vielleicht interessant, ob es bei dir einfach funktioniert.

Are you serious?

mickeymouse wrote:Warning: mysqli::__construct(): (HY000/1045): Access denied for user 'homeaccdbnm'@'localhost' (using password: NO) in C:\xampp\htdocs\HA_LogInCheck.php on line 59

This is far more information than you ever gave us. Obviously there is a problem with the database user. Please dounle check in phpmyadmin that the user homeaccdbnm exists and has no password.

I've tried to go according to the manual but can't get anywhere. I've tried several of the examples and always the same results.

One of my attempts is the following - just like the example - but doesn't work or at least, doesn't give me more info. It in fact tells me I have errors in the code (which is the same as the example so how can I have errors?)

if ($mysqli->connect_errno) {
printf("Connect failed: %s\n", $mysqli->connect_error);
exit();
}


Warning: mysqli::__construct(): (HY000/1045): Access denied for user 'homeaccdbnm'@'localhost' (using password: NO) in C:\xampp\htdocs\HA_LogInCheck.php on line 59

Warning: Undefined variable $mysqli in C:\xampp\htdocs\HA_LogInCheck.php on line 61

Warning: Attempt to read property "connect_errno" on null in C:\xampp\htdocs\HA_LogInCheck.php on line 61

lavalamp213 wrote:To answer your question, there is/was a database with that name.

There was. Currently there isn't. And we cannot solve a problem from a past. Now the problem is that the database is not existent and this needs to get solved first.

lavalamp213 wrote:When I try importing the data backup from my board, only half the tables will import (45 out of 90)

There are multiple reasons why this can happen. Most commonly timeout issues.

lavalamp213 wrote:I was advised to get my data backup directly from my host server via phpmyadmin.

I tried that, still didn't work.

What exactly didn't work? A phpmyadmin backup is a valid way to do a full database backup.
This backup needs to be complete for sure.

lavalamp213 wrote:I have been following instructions (and advice) I got from the phpbb Support forum. A lot of it was conflicting and contridictory advice.

Well, it would have been helpful if you show us the specific thread in the phpbb support board. Maybe there are information which can help us identifying the error or helping you better.
If you tell us what is conflicting and contridictory from your point of view maybe we can help to give you some explaination.

lavalamp213 wrote:I wonder if you have a set of install/set up instructions I could follow. Just try another clean set up and see what happens.
Is that something you could help me with?

There is not much to tell. Do a phpmyadmin backup, create your database user and database database locally and import your backup to the new database.
If the import runs in timeout issue, perform the import with help of the Commandline Interface (CLI)

I'm all over the place with this.

To answer your question, there is/was a database with that name.

When I try importing the data backup from my board, only half the tables will import (45 out of 90)

I was advised to get my data backup directly from my host server via phpmyadmin.

I tried that, still didn't work.

I have been following instructions (and advice) I got from the phpbb Support forum. A lot of it was conflicting and contridictory advice.

I wonder if you have a set of install/set up instructions I could follow. Just try another clean set up and see what happens.
Is that something you could help me with?

Wait!

"Unknown database" (error 1049) is a completely different error than your initial error "Access denied for user" (error 1045)

That error means the database cultofta_ss_dbn does not exist.
So check that the database is created having the correct name

Altrea wrote:Then lets simplyfy the environment.
What happens if you change the phpbb database user in your phpbb configuration from cultofta_ss_d8d1 to root
and the password to empty password?

I changed it in the config.php

restarted xampp, same message.

General Error
SQL ERROR [ mysqli ]

Unknown database 'cultofta_ss_dbn' [1049]

An sql error occurred while fetching this page. Please contact an administrator if this problem persists.

$dbname = 'cultofta_ss_dbn';
$dbuser = 'root';
$dbpasswd = '';