search

froxlor / Froxlor

The server administration software for your needs - The official Froxlor development Git repository
http://www.froxlor.org
GNU General Public License v2.0
1.63k stars 453 forks source link

Wrong host address for the froxlor DB user #1194

Closed Pacerino closed 10 months ago

Pacerino commented 10 months ago

Describe the bug Installation uses wrong ip address for the unprivileged user.

System information

To Reproduce Steps to reproduce the behavior:

  1. Install Froxlor
  2. Open the Setup
  3. Input Different IP into the MySql Host
  4. Go forward
  5. Getting error that the user "froxlor" dont have access to the DB

Expected behavior That the installation completes

Additional context I've created a new froxroot user. I can see that Froxlor is crearting the froxlor DB user with the IP Address of the DB as the "Host". IP from Froxlor: 192.168.40.103 IP from DB: 192.168.40.102 Froxlor User allowed from: 192.168.40.102 <- There should be the .103 address grafik

d00p commented 10 months ago

Well can you tell me where the ip 192.168.1.12 comes from if 103 is your froxlor and 102 your database? The installation process uses all given mysql-host values, localhost, 127.0.0.1 and the specified server ipv4 and ipv6 addresses to create the unprivileged database user. So there should definetly be more than one entry for the 'froxlor' user

Pacerino commented 10 months ago

I’m sorry, of course there should be the 192.168.40.102 which froxlor used as the host address.

Am 30.10.2023 um 16:56 schrieb Michael Kaufmann @.***>:



Well can you tell me where the ip 192.168.1.12 comes from if 103 is your froxlor and 102 your database? The installation process uses all given mysql-host values, localhost, 127.0.0.1 and the specified server ipv4 and ipv6 addresses to create the unprivileged database user. So there should definetly be more than one entry for the 'froxlor' user

— Reply to this email directly, view it on GitHubhttps://github.com/Froxlor/Froxlor/issues/1194#issuecomment-1785523224, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFJKPD5VPKCHWIECWRES6GLYB7E2RAVCNFSM6AAAAAA6WFF5D2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBVGUZDGMRSGQ. You are receiving this because you authored the thread.Message ID: @.***>

discordier commented 10 months ago

Now it is 192.168.40.102? We now have:

I also fail to see why this should be two different IPs, as the IP is the remote IP (aka Server IP connecting to) and in MySQL it is the source IP (aka client connecting from).

@Pacerino please elaborate on your setup.

Pacerino commented 10 months ago

Jesus... It was a long day yesterday. I'm sorry for the confusion. I've edited the Issue with the correct IP Addresses.

192.168.40.102 is the DB 192.168.40.103 is the Froxlor Installation froxroot has 192.168.40.103 as the allowed host froxlor gets 192.168.40.102 from froxlor installation setup.

d00p commented 10 months ago

192.168.40.102 is the DB 192.168.40.103 is the Froxlor Installation froxroot has 192.168.40.103 as the allowed host froxlor gets 192.168.40.102 from froxlor installation setup.

Please check your mysql-Database, the installer should create the following user@host combinations for the froxlor user:

Pacerino commented 10 months ago

Checked again and only the froxlor@192.168.40.102 is getting created. I'm running a freshly installed MariaDB on the 102 Server and a freshly created server for froxlor on 103.

Meanwhile we switched to HestiaCP. I dont know if you still want to investigate this issue or close it?

d00p commented 10 months ago

as we've successfully tested using external database-servers, I do not know what is wrong in your case; and as you've already switched to another panel, I'll close this.