MyBB Community Forums

Hi,

I am trying to install myBB, on an EasyPhp Devserver localhost.

It is stuck at the database details page in the installation. There is no reason for it to be so.

I have created a database and user in the phpMyAdmin, both called 'mybb'.









What is the problem? If any other information is needed I can provide. Thanks very much for any help.


I also have a general question: why are these things never trivial? Why, with computing systems, does doing the obvious and following instructions result in dead-ends and brick walls which cannot be smashed through no matter how much logic and trial-and-error you attempt?

Much regards, Hansolo

This happened to me once all i did was changed the localhost to 127.0.0.1 it then worked for me!

Try it, it might work or may not.

Thanks, tried it but no avail.

Try changing % to localhost in phpMyAdmin, then enter localhost during installation.

OK tried that, it created a new row, but no avail:

LOL why is this dead-ended already? Why isn't this trivial?

Hi,

Can you connect to the MySQL server using the given credentials in any other applications? For example, can you connect to the database via the command line? Have you also tried the root user in the setup to see if it can connect to the database correctly?

Can you paste the contents of your my.ini? I believe it is located in bin/mysql in your EasyPHP Installation directory.

(2015-05-12, 06:09 PM)Jack.D Wrote: [ -> ]Can you paste the contents of your my.ini? I believe it is located in bin/mysql in your EasyPHP Installation directory.

As follows:

# IMPORTANT
# C:/Program Files (x86)/EasyPHP-DevServer-14.1VC11 is used to specify EasyPHP installation path
#
# This is for a system with little memory (32M - 64M) where MySQL plays
# an important part, or systems up to 128M where MySQL is used together with
# other programs (such as a web server)
#
# MySQL programs look for option files in a set of
# locations which depend on the deployment platform.
# You can copy this option file to one of those
# locations. For information about these locations, see:
# http://dev.mysql.com/doc/mysql/en/option-files.html
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
#password	= your_password
port		= 3306
socket		= "C:/Program Files (x86)/EasyPHP-DevServer-14.1VC11/binaries/mysql/mysql.sock"

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
# The TCP/IP Port the MySQL Server will listen on
port = 3306

#Path to installation directory. All paths are usually resolved relative to this.
basedir = "C:/Program Files (x86)/EasyPHP-DevServer-14.1VC11/binaries/mysql/"

#Path to the database root
datadir = "C:/Program Files (x86)/EasyPHP-DevServer-14.1VC11/binaries/mysql/data/"

# The default storage engine that will be used when create new tables
default-storage-engine = MYISAM

bind-address	= 127.0.0.1
socket			= "C:/Program Files (x86)/EasyPHP-DevServer-14.1VC11/binaries/mysql/mysql.sock"
log_error 		= "C:/Program Files (x86)/EasyPHP-DevServer-14.1VC11/binaries/mysql/data/mysql_error.log"
skip-external-locking
key_buffer_size = 16M
max_allowed_packet = 1M
table_open_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
# 
#skip-networking

# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin

# binary logging format - mixed recommended
binlog_format=mixed

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id	= 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#
#    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#
#    Example:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
#
# The replication master for this slave - required
#master-host     =   <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin

# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = "C:/Program Files (x86)/EasyPHP-DevServer-14.1VC11/binaries/mysql/data/"
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = "C:/Program Files (x86)/EasyPHP-DevServer-14.1VC11/binaries/mysql/data/"
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer_size = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

(2015-05-12, 10:03 AM)Euan T Wrote: [ -> ]Hi,

Can you connect to the MySQL server using the given credentials in any other applications? For example, can you connect to the database via the command line? Have you also tried the root user in the setup to see if it can connect to the database correctly?

OK I tried connecting with command line to root user, which had no password, and it worked. So I then changed the user 'mybb' to 'no password' and I could then connect with that user. Very strange. Obviously I will need the password to work for when (if I like mybb) I later deploy this...

---

OK tried using a typed password instead of the 'generated password' and it's OK. Bizarre. I was using the same password, copy-pasted, every time before, and I specifically check I hadn't made this mistake about 3 times. No idea what gives, but I'll mark this as "solved"

Weird, definitely sounds like a bizarre issue. I've never used the generated passwords before, so I can't tell if it's perhaps an issue with how it works.