but how to define that this user is dedicated to working with database x and not y I mean if I have two databases on the same domain and I want each user to function with a single database
As far as I know all databases use the same username, maybe Iâm wrong,
You will need to add that username and password to the configs of the app.
Search the forum. Create usename and give it permission to that database as previous screenshot.
i have the license pro
what I donât understand why I donât have mysql I have another thing called mariaDB do you have any idea on that?
Virtualmin installs mariaDB not mysqld
The forum has ways to install mysqld instead. 99% of the time your apps should work with mariadb.
âMariaDB is designed to be backward compatible with MySQLâ
so thereâs no need to change it
No, not to go backwards in time.
Coming back to this after a day away from it, we seem to have changed topic to something else. Something which, to me, looks like a problem really unrelated to phpmyadmin and more of (yet another) WP problem. Or some other app that has been installed on the web site that uses external code that is out-of-date.
Virtualmin/Webmin just cannot be held responsible for all the garbage code that is out there which remains poorly maintained and much of which is not fit for purpose.
MariaDB is superior to MySQL (which IMO had fallen into a rut in terms of development).
I am all in favour of suggesting improvements to Virtualmin/Webmin, especially those that can bee seen as an improvement, but not negative ones.
hello Mr please if you can help me
my problem is I had a website based on php on Cpanel which I always installed php 7.4 database creation import of data from then phpmyadmin and after file hosting with the modification of the config.php file DB name USER name PATH localhost
but with webmin itâs all completely deferent I installed the php I called out the database I imported the data from then phpmyadmin when I launch nothing is displayed except the message on the photo even the phpmyadmin link displays it same message: No input file specified.
The problem here is that you are moving an app that works on cPanel and assuming it will work on Virtualmin. The app programmers will have made assumptions (configurations, presence of variables/data structures etc that are different and possibly not available on Virtualmin. You are expecting Virtualmin to know what the programmers of your app are thinking. Systems do not work like that. The whole point of Virtualmin is that it starts with a clean slate on which you can add things like WP or other apps but there integration remains the responsibility of the app programmers.
You are starting from Ubuntu 20.04 with cPanel, MySQL, PHPMyAdmin and some app that is a chain of diverse problems all of which can cause issues when trying to move them.
In nearly all of those choices I would start from the latest best version and not go backwards Ubuntu is now 22.04 and you will get the php 8.x and the latest phpMyAdmin as for your app (which I am convinced is causing the problems) that is not something that can be resolved here.
I have a box still using Ubuntu 20.04 with php7.x and phpMyAdmin and no problems.
I also have boxes with Ubuntu 22.04 php8.x but they have no need for phpMyAdmin as in general I ditched php years ago, so they only use it for Roundcube (webmail)
It is very difficult to understand exactly what the problem is. I also think folk on here tire of topics that wander from the subject title. We are now up to post #30 when it seemed resolve by #7
jump Mr thank you for your reply for information purposes the site is a basic site with php it is already functional on wampserver and on cpanel and also on aapanel I think it must function on any hosting system because of what it is base on two things PHP and html which confirms that your hypothesis is ILLOGICAL
This is the same problem as your other thread (this one: WORDPRESS virtual server - #23 by Joe). Also has nothing to do with databases or even phpmyadmin.
PHP scripts arenât running. Thatâs what we need to figure out.
That is not the problem. That may be a problem in the future, but right now, PHP scripts arenât running at all, has nothing to do with cPanel.
OP tried installing phpmyadmin (and also WordPress in another thread) and neither works. cPanel has nothing to do with that, as far as I can tell. (Though maybe if these domains were migrated from cPanel backups there would be some additional junk in the config thatâs breaking things.).
@Alaaeddine.benabid did you create this virtual server using the Create Virtual Server form, or did you import it from a cPanel backup using the Add Servers->Migrate Virtual Server page?
Either should work, but it determines where we should expect to find problems.
nn not that I saved the origin files with Winrar and I extracted the database with phpmyadmin and itâs the same thing that I always do and of course I modify the config.php file on the information of each hosting
Thatâs not relevant yet. PHP isnât even running, so it doesnât matter whatâs in it.
So, if PHP is being stopped. and that has nothing to do with Virtualmin and we know it is not the version of PHP or the version phpMMyAdmin. â it must be something in the code. yes? (something else running php that is conflicting. Something not obvious in the php logs, perhaps. But no other php is running on this VS right?
I agree it has nothing to do with cPanel I was not suggesting it was, I was just saying you cannot just assume that something that works on one system structure will automatically work on another quite different one. Again this is not a Virtualmin problem. The only reason I remain interested is I would like to know what is killing php (it is quite a robust language but can be abused quite easily â but killing it completely?)
It was from a custom config in .user.ini
that OP was uploading to the server that was setting open_basedir
to a nonsensical value (pointing at a location that does not exist on a Virtualmin system). PHP is now functioning for them. Weâre tackling some other issues in a PM, now.
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.