Skip to main content


Problems installing friendica 20.21 04 on shared host


@Friendica Support

Hi there!
Installing a new friendica site.
Last time I installed 2019.12 and didn't have mayor problems in the initial step browsing to the domain for the first time.
https://forum.friendi.ca/display/39bbe52a-385e-6dad-3cdc-6c6128916067

This time I ran into two required problems.
After adding the "Command line PHP" path i get this:

PHP cli binary Requirement not satisfied Required

PHP executable is not a php cli binary; it could possibly be a cgi-fgci version.
Found PHP version:

The other problem:

Program execution functions Requirement not satisfied Required

Error: Program execution functions required but not enabled.

What to do?
(couldn't find help in the wiki and websearch)
--------------------
On the cronjob for worker.php
Should the path point just to the domain name or additionally to:
/htdocs/bin/worker.php
??
#friendica

This entry was edited (3 years ago)
What command-line PHP executable path did you provide?
@Hypolite Petovan
/var/www/virtual/maincontractdomainname/domain.com/sudomain/htdocs
@Michael Vogel
My provider let's me schedule cron jobs from a panel.
I provided the subdomain address:
https://sudomain.domain.com
@Steffen K9 🐰 @Hypolite Petovan
How do I reverse/change the actual setting, the page doesn't offer me that possiility?
I guess directly some file via ftp?
@Steffen K9 🐰@Hypolite Petovan
Please note, that some shared hosters provide multiple versions of PHP. You need to use the path to the right version of PHP (if there are multiple versions installed).
When setting up the domain/sudomain I can choose the version.
I selected 7.4

Right now I'm trying to find conclusive help here, if there are issues I will have to solve with the hoster, that would be the next step.
@Steffen K9 🐰@Hypolite Petovan
Umm. that's not a path to a PHP binary/executable file.
I took a look at the previous installation that worked without problems.
In local.config.php there is no entry.
Assuming that tere haven't been changes on the side of the provider, does this inormation help?
'php_path' => '',
@Steffen K9 🐰@Hypolite Petovan
How do I reverse/change the actual setting, the page doesn't offer me that possiility?
I guess directly some file via ftp?
I tried to find file changes via ftp but couldn't find any.
Is this entry to be found in the DB?
Deleting the complete DB content would be suffice I guess?
@Steffen K9 🐰@Hypolite Petovan
hmm ..
looks like that file doesn't exist for now.
there is only:
config/local-sample.config.php
I downloaded it but there is no entry for now for:

I checked the respective file in the working 2019.12 config folder:
'php_path' => '',
'urlpath' => '',
'url' => 'https://sudomain.domain.com',
'basepath' => '
/var/www/virtual/maincontractdomainname/domain.com/subdomain/htdocs
Some additional Info on the hosting with respect to the DB installed:
Server: Localhost via UNIX socket
Server type: MariaDB
Server version: 10.3.23-MariaDB-0+deb10u1-log - Debian 10
Protocol version: 10
..
Apache
Database client version: libmysql - mysqlnd 7.4.11
PHP extension: mysqli Documentation curl Documentation mbstring Documentation
PHP version: 7.4.11
@Steffen K9 🐰@Hypolite Petovan
hmm ..
looks like that file doesn't exist for now.
there is only:

config/local-sample.config.php

I guess the answer is somewhere here?:
http://subdomain.domain.com/index.php?pagename=install
@Steffen K9 🐰@Hypolite Petovan
I found a work around for resetting the install screen and the php Path problem. I did an ftp upload with the restriction to only upload files that are newer or different size.

The php path problem vanished. In other words, the install checking page doesn't ask me anymore to provide that path.

What is left is the program execution requirement:
Program execution functions Requirement not satisfied Required

Error: Program execution functions required but not enabled.

What is that?
What is this about?
What do I have to ask my hoster for?

btw
If I remember well, the last time I tried I got exactly the same in the first place.
The php path issue came up after clicking the "check again" button.
@Steffen K9 🐰 @Hypolite Petovan
btw
If I remember well, the last time I tried I got exactly the same in the first place.
The php path issue came up after clicking the "check again" button.


I tried to retest this " #bug ? " and it happened again.
The first time I called the (sub)domain page no "command line PHP" problem.
I pressed the "check again" button and the problem appeared.
The problem is marked with a yellow dot.
If you have a look at the screen I posted before, after adding the command line php path, it is marked with a green dot.
@Michael Vogel@Steffen K9 🐰@Hypolite Petovan

The term proc_open sounds familiar to me.
What do we need it for?
Was it necessary for 2019.12?
Did 2019.12 checked for it's status?
If not, how can I skip the proc_open check?

I'm going to ask the provider about proc_open.

What was the file that that the ftp opload reset?
@Michael Vogel@Steffen K9 🐰
In the past we tried to work around this. But we realized that it just wasn't reliable.

Does this mean that 2019.12 used it or not?
@Michael Vogel@Steffen K9 🐰

What file do I have to modify to skip this check?

I guess my provider still refuses to enable it for security reasons for the shared hosting in general.

What was the file(s) that that the ftp upload reset so I got rid of the php path I entered?
@Michael Vogel@Steffen K9 🐰@Hypolite Petovan

Just tried to skip the whole install page process by uploading a respective local.config.php to /htdocs/config but that didn't do the job.
:(
@Steffen K9 🐰@Hypolite Petovan
I tried to retest this " #bug ? " and it happened again.
The first time I called the (sub)domain page no "command line PHP" problem.
I pressed the "check again" button and the problem appeared.

Aparently Just the difference between:
https://subdomain.domain.com/
and
https://subdomain.domain.com/index.php?pagename=install
@Michael Vogel@Steffen K9 🐰@Hypolite Petovan
Didn't get a notification of your comment Micha.

I guess that was because I had this page open.
(using firefox)
@hans_w

No clue what you are talking about.

I'm on a shared host and trying to install "just another" friendica site.
I installed my first friendica site like a decade ago and since then installed every once in a while a domain or subdomain.

At this stage I left behind kinda cemetery of broken friendica sites because of unsuccessful updates to a newer version, instead of leaving them just as they were.
(no rant or accusation at all, this is because of "incapatibilities" of mine)

Actually I'm wondering about how to recover them by reversing the update or finishing the respective update, if I could get a grip of the respective version to create a kind of "museum of the evolution of friendica".

Did you contact the hosting party about this?

me in this thread wrote:

I'm going to ask the provider about proc_open.
I guess my provider still refuses to enable it for security reasons for the shared hosting in general.
@Michael Vogel@Steffen K9 🐰
I guess my provider still refuses to enable it for security reasons for the shared hosting in general.

provider wrote:

Hi,

I am sorry, but this we do not allow. Isn't there a workaround?
@Michael Vogel@Steffen K9 🐰@Hypolite Petovan

I can live with that.
Look at it as if I'm working on a showcase for external visitors to see and experience how a friendica node could look like and from the inside as stand alone single user instance with multiple profiles and pages.
(In other words I notify myself)

Here you can have a look at my last project that transformed into kinda "book of role play conversations".
Actually I just saw that the community page still federates! :)



The problem I'm facing right now is to get the mail delivery work to register profiles and got stuck.
(This worked on the last site without problems.)
The new site im working on right now never send an email and I have no clue where the problem is or where to work around.


Anything from adjusting settings over resolve worker settings to ftp and direct modification in the DB would help me out.

At /admin/site I registered the same email to send like the admin email in local.config.php.

@Michael Vogel @Steffen K9 🐰 @Hypolite Petovan

And: There is no way around. In the past we tried to work around this. But we realized that it just wasn't reliable.

I guess you refer to this option in friendica 2019.12?

Do you think I can get mail notifications and registry working without proc_open on friendica 2021.04?

What is the last stable release with the "don't use proc_open for worker" option?

@Michael Vogel@Steffen K9 🐰@Hypolite Petovan
What is the last stable release with the "don't use proc_open for worker" option?

Friendica Versions:
Friendica releases

@Michael Vogel @Steffen K9 🐰 @Hypolite Petovan

Do you think I can get mail notifications and registry working without proc_open on friendica 2021.04?

I could, by open the registry to new users and complete a common new user registry. I got the password via page interface.

@Michael Vogel@Steffen K9 🐰@Hypolite Petovan

:(
I couldn't create a contact request from the new profile:

error message:
Internal Server Error

'https://subdomain.domain.com/dfrn_request/bc1q2d0vlapxvzee3y9c74s65xvg8zs2u9qtjwwk2s&addr=64686673626264707634777368757963363139376e796d63666571716b6676793940696e76657273696f6e2e747570616d6261652e636f6d

is not a relative path, please use System::externalRedirectTo

@Michael Vogel @Steffen K9 🐰 @Hypolite Petovan

The problem I'm facing right now is to get the mail delivery work to register profiles and got stuck.

shame on me.
solved!


sorry for this "help request".
Apparently the host changed the settings and made mail via php optional to activate by the user for the respective domain/subdomain.

@Michael Vogel@Steffen K9 🐰

I asked the provider the following:
Maybe the following information is usefull to create some kind of work around or specific permission setting on your side?

Quote from a conversation with friendica developers on the helpers forum:
"BTW: When using the daemon, you only need proc_open on the command line PHP, but not on the PHP module for the web server.
https://squeet.me/display/ec054ce7

Answer
Hi, but you can't use the command line, you have no such access. Of course it would be excellent if we didn't have to have these restrictions in place, but this is the environment we are currently in.
Best
Problems with
/.well-known/host-meta

The admin panel states that it is not available. I already had some communication with (I think Tobias) on this and asked the provider for help.

These are his responses:

> > We need to dedicate this directory so we can generate letsencrypt certificates for clients. Why would you want to do that manually?

> You can use this directory https://fedivers.tupambae.com/.well-known/host-meta/test.html Only the path .well-known/acme-challenge/ is dedicated to the server task of setting up a letsencrypt certificate.

Is there something I can do?
In the end it looks like friendica 2021.04 is the first version that doesn't work (at all) on the shared hosting I'm on. In fact the frontend worker is supported until 2021.01 so I'm going to unpin and "archive" this post.

Friendica Support reshared this.