Jump to content
Froxlor Forum

Question

Posted
I rented a new root-server and currently setting up the basics, including Froxlor, like on my old system. The server came preinstalled with a Debian 12[Bookworm] (netinst, minimal)

I installed Froxlor via APT acc. to the webpage. Now, in the web-interface of the Froxlor installer, I get two messages:

1.) [yellow exclamation mark] Your system is running with PHP 8.2.26
Now the yellow indicates it not a problem, but also not good. There is no indication what the problem is. PHP version to high? to low? my pixel just run out of blue ink and it's in real green? Here it would be nice (for a future version), if it writes, what it warns for (As it internally checks for something to decide the color, that shouldn't be a problem)

2.) The following php extensions could not be found but are recommended
gnupg

So I installed gnupg2 via APT as well as gnupg via pecl, added the "extension=gnupg" line in "php.ini", restarted the whole server via ACPI and checked with "php -m" if the extension is running; and it's listed.
Yet, Froxlor claims the module is still missing.

What comes to mind:
- Do I have to register gnupg somewhere else for froxlor to find?
- Is it, that I installed Froxlor via APT before installing gnupg and the check was done during install time?
- Is the PHP version [warned about] insufficient to work with gnupg and Froxlor?

I know it's not required (it writes it on the install page), but now that I have a clean new system, I don't want to start with holes in the first service I setup

Anyone have a suggestion and run into the same problem?

7 answers to this question

Recommended Posts

  • 0
Posted

Just to inform, uninstalling gnupg2 via APT resolved it and now the extension is being found. so it was a conflict with the system package.

Thanks again and maybe forward my suggestion about the warning indication. See ya.

  • 0
Posted
21 minutes ago, Volatile said:

Now the yellow indicates it not a problem, but also not good. There is no indication what the problem is.

You literally answered that yourself as it is right below:

21 minutes ago, Volatile said:

The following php extensions could not be found but are recommended

 

21 minutes ago, Volatile said:

Yet, Froxlor claims the module is still missing.

Because by default you are running mod_php which is an apache module and in order for it to take effect you have to restart the Webserver...

  • 0
Posted

Thanks so far.

Okay, so I understand, that the yellow indication is not related to the PHP version, but the missing Module. Don't get this wrong or as an offense, but because of the layout (how it is written), it's not obvious for someone who doesn't know this. For an "outsider", duo to perception, the yellow "not okay" is being applied to the PHP version, not the missing module described below it.

31 minutes ago, d00p said:

Because by default you are running mod_php which is an apache module and in order for it to take effect you have to restart the Webserver...

54 minutes ago, Volatile said:

 restarted the whole server via ACPI and checked with "php -m"

If I do a hardware restart, the webserver will forcibly be restarted as well. I'll take a look at some log-files. If it's not a php-version issue, maybe the module isn't started correctly or something like that. Maybe a conflict with the gnupg2. I try to uninstall that and see what happens.

If someone has another suggestion where to look, feel free to post. Thanks!

  • 0
Posted
Just now, Volatile said:

Thanks again and maybe forward my suggestion about the warning indication.

forward to who? :P

  • 0
Posted

Ah, well, I just read now in the signature, you are the lead developer. So I guess, no forwarding required. 😁

Thanks again for the help!

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×
×
  • Create New...