Hi naresh.chandra@copart.com, are you able to connect to the listener via CLI? .e.g. `mariadb -h 127.0.0.1 -umaxskysql -pskysql -P9999`

Hi Duong,

Yes, we are able to connect from the CLI.

I think the problem might be in the SQL endpoint of the REST API: it probably uses the raw address string instead of checking whether it's the all-interfaces address of either 0.0.0.0 or ::.

Hi Markus,

Thanks for the update. Can we fix this issue in the next release?

naresh.chandra@copart.com can you test if it works correctly when you define the actual IP address of the host (e.g. 192.168.1.100 or whatever ip addr shows)?

Markus, you mean, I should try like this mariadb -h 192.168.1.1 -umaxskysql -pskysql -P9999`

Sorry, I wasn't clear enough: can you add address=192.168.1.1 (I'm assuming this is the IP of the machine) to the listeners and then test if the GUI works?

Getting the below error.

Connection to [192.168.1.1]:9999 failed. Error 1524: Plugin 'mysql_native_password' is not loaded.

[Read_Listener]
type = listener
service = Read_Service
protocol = mariadbclient
port = 9999
address = 192.168.1.1
authenticator = PAMAuth

Are you using version 6.2.1? If so, can you test this with 6.2.3 as well?

Ah, you'll need to include mariadbauth in that authenticators list.

Yes, I am using 6.2.1, let me try 6.2.3 and update you.

Markus, I tried with 6.2.3 but still the issue is same.

did it work with authenticators=PAMAuth,MariaDBAuth?

Both are not working.

What error does it return when you add authenticators=PamAuth,Mariadbauth to the listeners and use the correct IP address?

If we use the authenticators=Mariadbauth then we are getting the below error

ERROR 1045 (28000): Access denied for user

If we use the authenticators=Mariadbauth then we are getting the below error
Connection to [192.168.1.1]:9999 failed. Error 1524: Plugin 'mysql_native_password' is not loaded.

You'll need a user that is allowed to connect from the local host, i.e. user@127.0.0.1. Once you add that and use authenticators=mariadbauth,pamauth I think it should work.

You mean, I have to create an user locally in mariadb then I need to add the parameter in the maxscale config file right?

and can you confirm/check that Maxscale Query editor rest API is same for Server and Listener? I mean if we select in the GUI, source as either server and listener then the API call is same or its different logic in the code?

Internally, the code creates a new connection and the only difference is the address to which the connection is created: for listeners it is a local connection whereas for servers it is a remote one. For this reason you must have a user that has the permission to log in from the "local" server, i.e. from 127.0.0.1.

To create the local user, you can create it similar to this:

CREATE USER 'user'@'127.0.0.1' IDENTIFIED BY 'my-password';

Obviously, change the username and password to what is suitable for you. Please also note that in order for MaxScale to be able to connect to the databases, the same user must also have the grants for direct access. Optionally, you could enable proxy_protocol to avoid creating the second user definition.

Ok Markus,

Are you changing anything to related Server(source) or Listener(Source) API? But keep same settings for Server(source) API code as its working fine.

We could make it so that if the listener uses address=0.0.0.0 or address=::, MaxScale would correctly translate this to address=localhost for the GUI SQL connections. You can confirm whether this would solve your problem by following the instructions I've written to use the actual IP address of the MaxScale host. Based on the fact that you got an access denied error, I would say that this would solve the problem once the correct user permissions are added.

Yeah, I got it Markus, But not sure where i am facing the error. Better keep the same settings for Server (Source) code. So I think we can close this ticket. We will use source as a Server only. But here we are expecting the global or local browser cache if we select source as a server.