Hey guys, Someone have an link on how to setup the phpmyadmin for the multiserver setup? Looking around i found this post: http://www.howtoforge.com/forums/showthread.php?t=55811 After try i get my db.server.com isnt accepting connections from my web.server.com. Should i add 2 users like ISPConfig setup does? I mean root@IP and [email protected] Since this user need have full access on db.server.com, i would set to use the ispconfig login instead make a new one?
Ypu can do that. Or try to add the one with the Ip first, if it does not work, change it to the hostname. Dont forget to reload mysql or flush priveliges after you changed a user. That depends on your setup. If the db server is not the amster server, then you can reuse it. If the master server is not the db server, then create a new user as the one created for the ispconfig setup allows only access from a slave to the master and not from one slave to another.
I tried adding only the IP. Worked only for root. But when i try log as user i get acces denied, example: [email protected] > OK [email protected] > Access Denied [email protected] > Access Denied On my setup like i did with root i will need add the users one by one?
Someone have the phpmyadmin working in multiserver enviroment and would share how to get this working please? I have tried on web.server.com: dpkg-reconfigure phpmyadmin Then i set to connect directly on the other server: db.server.com But when i try log seems the phpmyadmin send the login as: [email protected] And so, pop error about access denied. There someway to rewrite the domain name inside of phpmyadmin? I mean for try log as: [email protected] (already exists since ISPConfig created by the pannel) instead [email protected] (dont exists)
Then you might have missed to enable remote access for the user.Login to ispconfig, go to the database settings and enable remote access.
Yeah is it. I have checked now to enable remote access and worked pretty nice. Since i dindt oppened the port 3306 on my firewall, i dindt worry about someone try bruteforce attacks on my db.server.com right?
Yes. And even without that you wont have to worry as you can restrict the access by ip address to allow access from the web server only.
Today i got sometime to back on play on my server and notice an problem with this setup. I`m able to log as user, see database / tables, but, when i try run any SQL query i get an error: ERROR 403 - Forbidden! When i click to check the documentation, i get same error. Looking on /var/log/apache2/error.log and access.log, i dindt find anything about this error. I`m missing an include somewhere? I mean, I need add something else on path inside of ISPConfig? Btw, my phpmyadmin is using ssl, would be this?
Just updating my tests, i have tried use: # Order Deny,Allow # Deny from All Allow from LAN IP Dindt worked, then: # Order Deny,Allow # Deny from All Allow from All Samething, so: # Order Deny,Allow # Deny from All Allow from All Require all granted No luck too, my question now would be, there an way to specific the detail for log on apache? My guess for there no info on apache logs would be because something would have be set for minimun details.
After some reasearch i found where are the real logs of apache, seems they still on this place: /var/log/ispconfig/httpd/mydomain.com/error.log On the log i noticed this: So the * certificate is useless then? I mean, i will need do an new certificate specific for web.server.com, for db.server.com, etc... ???
Hey guys, Seems i fixed almost all problems till here. Now, when i try use the SQL tab for restore an backup i`m getting this error: Doing some researchs i found this is an bug of phpmyadmin, but other pannels like plesk have an fix for it, plesk say for they users download this: And replace the session.inc.php. My question now is: There any similar fix to ISPConfig?
The phpmyadmin package is instaled from the linux distribution that you use on your server, its not from ispconfig. So if you search for a patch for this issue you will have to look for a patch for your linux distribution and not a patch for ispconfig as every linux distribution uses a different version of phpmyadmin. The linux distributions have bug tracking systems, so its a good idea to look there for a patch. You can also try if the patched file from plesk works on your server, just ensure that you backup the original file first.
