NODE-RED MYSQL NODE connection refused

Hi there please help

I have node-red running on a locally networked PI3. I want to connect MYSQL on an external ubuntu server running MYSQL.
When i configure a MYSQL node with the MYSQL login details of the ubuntu server i get the message CONNECTION REFUSED
The settings of the node are
Host 160...*
Port 3306
User useronpi3
Password ••••••••

Can you access the server using the mysql command line client on the pi to connect to the server?

Have you configured the server to allow access remotely? You have to set bind-address in the mysql conf file if I remember correctly.

Once again @Colin, thank you for pointing me in the right direction!


Step one: Allowing access

Out of the box, MySQL will only allow access from the localhost address To change this, you need to open the /etc/mysql/mysql.conf.d/mysqld.cnf file and change the line:

bind-address =


bind-address =

Save and close that file. Restart the MySQL server with the command:

systemctl restart mysql.service

Step two: Allowing login (eg pi3 user as below)

  1. create a user on the pi3

example useronpi3 with password 'useronpi3password'

  1. do the following on ubuntu mysql server

CREATE USER 'useronpi3'@'%' IDENTIFIED BY 'useronpi3password';

GRANT ALL PRIVILEGES ON . TO 'useronpi3'@'%'


You don't need to create a specific user on the pi, if that is what you meant. The user name you pass to mysql to logon does not need to be a user on the pi. Perhaps that is not what you meant though.

I have worked with the database and the node red locally, but now I want to make the change and work with a database locally in Windows, but with node red in a virtual machine ubuntu; I have problems in the connection of the database; could someone help me please.


you haven’t said what problems you are having.

By default mysql is configured to only listen on local connections, so you may need to enable remote connections.

Thanks for answering, I have the following message in node red: in the mysql node connection refused.
I have tried to modify the file my.ini but I can not solve the problem. Can you help me please


I think this is the answer:

He tried to make the saying, but I do not have the line of bind-address =
in which part of the file should I place the respective line bind-address= please


You don't have a /etc/mysql/mysql.conf.d/mysqd.cnf file?

What is in:

Seems weird if it should be in the install.

I have the file, but the command line bind-adress = I do not have it


Beyond me skill set.

But: What is in the file you have?
Is it big?

Maybe paste it here and someone else could help.

Thanks for answering, but I do not know in which part of the file I should add the line bind-address=

Honestly, me neither.

But just stick it at the end.

It won't blow up if you get it wrong.

If it works: great. If not, nothing really lost.

(Via edit)

I see there are 3 sections to the file.




It MAY need to go in one of those...... Sorry.

All you can do is try.

Alas that means you now need to try 3 rather than 1 times. but.....

(Ah! You pasted a picture. You could have just "cut/paste" the lines.)


Re-reading it:

The following options will be read by the MySQL server.
Make sure you have installed the server correctly.....

Maybe try that part.
So: after the "default-character-set=latin1" line.

It should be in the [mysqld] section, so at the end, assuming you have posted the complete file. You will need to restart the server after changing it. If you don't know how to do that then reboot.
For the future it is generally better to paste text here rather than post an image. You can copy from a terminal window using Ctrl-Shift-C

The above was done, but the problem still exists; I attached the file my.ini:

# Other default tuning values
# MySQL Server Instance Configuration File
# ----------------------------------------------------------------------
# Generated by the MySQL Server Instance Configuration Wizard
# Installation Instructions
# ----------------------------------------------------------------------
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
# On Windows you should keep this file in the installation directory 
# of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
# make sure the server reads the config file use the startup option 
# "--defaults-file". 
# To run the server from the command line, execute this in a 
# command line shell, e.g.
# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
# To install the server as a Windows service manually, execute this in a 
# command line shell, e.g.
# mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
# And then execute this in a command line shell to start the server, e.g.
# net start MySQLXY
# Guidelines for editing this file
# ----------------------------------------------------------------------
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
# More detailed information about the individual options can also be
# found in the manual.
# For advice on how to change settings please see
# ----------------------------------------------------------------------
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.

# pipe=




# default-character-set=

# ----------------------------------------------------------------------
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this 
# file.
# server_type=3

# The next three options are mutually exclusive to SERVER_PORT below.
# skip-networking


# The Pipe the MySQL Server will use

# The TCP/IP Port the MySQL Server will listen on



# Path to installation directory. All paths are usually resolved relative to this.
# basedir="C:/Program Files/MySQL/MySQL Server 5.7/"

# Path to the database root
datadir=C:/ProgramData/MySQL/MySQL Server 5.7/Data

# The default character set that will be used when a new schema or table is
# created and no character set is defined
# character-set-server=

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

# Set the SQL mode to strict

# General and Slow logging.






# Binary Logging.
# log-bin

# Error Logging.

# Server Id.

# Specifies the on how table names are stored in the metadata.
# If set to 0, will throw an error on case-insensitive operative systems
# If set to 1, table names are stored in lowercase on disk and comparisons are not case sensitive.
# If set to 2, table names are stored as given but compared in lowercase.
# This option also applies to database names and table aliases.

# Secure File Priv.
secure-file-priv="C:/ProgramData/MySQL/MySQL Server 5.7/Uploads"

# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.

# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]

# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.

# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before.  This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)

#*** MyISAM Specific options
# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method.  This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.

# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.

# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.


#*** INNODB Specific options ***
# innodb_data_home_dir=

# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
# skip-innodb

# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.

# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).

# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system.  Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.

# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.

# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.

# The increment size (in MB) for extending the size of an auto-extend InnoDB system tablespace file when it becomes full.

# The number of regions that the InnoDB buffer pool is divided into.
# For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency,
# by reducing contention as different threads read and write to cached pages.

# Determines the number of threads that can enter InnoDB concurrently.

# Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before
# it can be moved to the new sublist.

# It specifies the maximum number of .ibd files that MySQL can keep open at one time. The minimum value is 10.

# When this variable is enabled, InnoDB updates statistics during metadata statements.

# When innodb_file_per_table is enabled (the default in 5.6.6 and higher), InnoDB stores the data and indexes for each newly created table
# in a separate .ibd file, rather than in the system tablespace.

# Use the following list of values: 0 for crc32, 1 for strict_crc32, 2 for innodb, 3 for strict_innodb, 4 for none, 5 for strict_none.

# The number of outstanding connection requests MySQL can have.
# This option is useful when the main MySQL thread gets many connection requests in a very short time.
# It then takes some time (although very little) for the main thread to check the connection and start a new thread.
# The back_log value indicates how many requests can be stacked during this short time before MySQL momentarily
# stops answering new requests.
# You need to increase this only if you expect a large number of connections in a short period of time.

# If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and
# synchronize unflushed data to disk.
# This option is best used only on systems with minimal resources.

# The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use
# indexes and thus perform full table scans.

# The maximum size of one packet or any generated or intermediate string, or any parameter sent by the
# mysql_stmt_send_long_data() C API function.

# If more than this many successive connection requests from a host are interrupted without a successful connection,
# the server blocks that host from performing further connections.

# Changes the number of file descriptors available to mysqld.
# You should try increasing the value of this option if mysqld gives you the error "Too many open files".

# If you see many sort_merge_passes per second in SHOW GLOBAL STATUS output, you can consider increasing the
# sort_buffer_size value to speed up ORDER BY or GROUP BY operations that cannot be improved with query optimization
# or improved indexing.

# The number of table definitions (from .frm files) that can be stored in the definition cache.
# If you use a large number of tables, you can create a large table definition cache to speed up opening of tables.
# The table definition cache takes less space and does not use file descriptors, unlike the normal table cache.
# The minimum and default values are both 400.

# Specify the maximum size of a row-based binary log event, in bytes.
# Rows are grouped into events smaller than this size if possible. The value should be a multiple of 256.

# If the value of this variable is greater than 0, a replication slave synchronizes its file to disk.
# (using fdatasync()) after every sync_master_info events.

# If the value of this variable is greater than 0, the MySQL server synchronizes its relay log to disk.
# (using fdatasync()) after every sync_relay_log writes to the relay log.

# If the value of this variable is greater than 0, a replication slave synchronizes its file to disk.
# (using fdatasync()) after every sync_relay_log_info transactions.

# Load mysql plugins at start."plugin_x ; plugin_y".
# plugin_load

# The TCP/IP Port the MySQL Server X Protocol will listen on.
# loose_mysqlx_port=33060

In node mysql I still have the problem, in the host attribute I have placed an ip of the network segment in which my computer is connected:


Check using the mysql command line client that you can access the server from the machine running node red. Once that works then try it in node red.

Greetings Colin, in my case the node network is in a virtual machine in the cloud with address 159.65.xx, while the MySQL database is located locally on my computer with the ip 192.168.xx, ie they are in different network segments.

In node network the mysql node explicitly asks to indicate the host.

Regarding your response, I am not very clear about what I should do. Thanks for the help