VestaCP PHP Selector for Centos add php 7, 5.6 and 5.5.

[kaavain]

Hi all

The question is: having CentOS 7 is it a chance to get PHP 5.3.3 using this selector or no way and wasted time? I'm really need 5.3.3

[pashali]

hello

i got error after install VestaCP PHP Selector.

phpMyAdmin - Error

Error during session start; please check your PHP and/or webserver log file and configure your PHP installation properly. Also ensure that cookies are enabled in your browser.

session_start(): open(SESSION_FILE, O_RDWR) failed: Permission denied (13)

i try everything but not fix. please help me with it.

im using centos 6.10

and install this
https://github.com/001101/Vesta-CP-PHP- ... .6-and-5.5

now unable to open phpMyAdmin

[kaavain]

Found a great solution. I’m really happy and it works perfectly. And even has much, much better functionality, easy of use and UI. The name is FastPanel. It is completely free and works fantastic.

[addyjo]

Hi Guys! today i will tell you that how you can get rid of dont have permission to accesss phpmyadmin once you downgrade from php 8.1 to any version of php,

Please note - i tried this on vestacp fresh install- PHP version installed 8.1(so do it at your own risk , i am not a coder or linux admin but i spent almost 3 days to find out the solution of this issue...it may help you, dont forget to say thanks :)

so lets get started


#First downgrade php by this tuotorial


#downgrade from 7.3 to 5.6 or any other version
first remove php .....

yum remove "php-*" -y

then disable & enable the version you want..

yum --disablerepo=remi-php73 --enablerepo=remi-php56 install php php-gd php-mbstring php-mysql php-curl php-mcrypt

https://www.linuxhelp.com/how-to-upgrad ... centos-7-6

#Checkyour php Version Now

php -v


#Then disabled all variant - one by one

yum-config-manager --disable remi-php55
yum-config-manager --disable remi-php56
yum-config-manager --disable remi-php70
yum-config-manager --disable remi-php71
yum-config-manager --disable remi-php72
yum-config-manager --disable remi-php73

https://www.mysterydata.com/how-to-inst ... s-vestacp/

#Then enable the main PHP repo (Check your php version first by php -v command

yum-config-manager --enable remi-php73


#now remove phpmyadmin

yum remove phpmyadmin

#Re-install phpmyadmin

yum install phpmyadmin


#open your phpmyadmin.conf file by this command

vi /etc/httpd/conf.d/phpMyAdmin.conf

#now under user share change this

<Directory /usr/share/phpMyAdmin/>
AddDefaultCharset UTF-8

<IfModule mod_authz_core.c>
# Apache 2.4
<RequireAny>
#Require ip 127.0.0.1
#Require ip ::1
Require all granted
</RequireAny>
</IfModule>
<IfModule !mod_authz_core.c>
# Apache 2.2
Order Deny,Allow
Deny from All
Allow from 127.0.0.1
Allow from ::1
</IfModule>
</Directory>
<Directory /usr/share/phpMyAdmin/setup/>
<IfModule mod_authz_core.c>
# Apache 2.4
<RequireAny>
#Require ip 127.0.0.1
#Require ip ::1
Require all granted
</RequireAny>
</IfModule>
<IfModule !mod_authz_core.c>
# Apache 2.2
Order Deny,Allow
Deny from All
Allow from 127.0.0.1
Allow from ::1
</IfModule>
</Directory>

#save and exit the file by this command

:wq


#then restart the server

service httpd restart


check the phpmyadmin ...enjoy:)

[shonir]

Hi,

I installed PHP Selector on my production server. Now on SSH when i command php -v its showing php version 7.4.23 and when i used php script <?php phpinfo() ?> to check then its showing 5.6.40 version. how i can set 7.4.23 as default?? even when i try to change version then nothing happened.

[skamasle]

Hi,

I installed PHP Selector on my production server. Now on SSH when i command php -v its showing php version 7.4.23 and when i used php script <?php phpinfo() ?> to check then its showing 5.6.40 version. how i can set 7.4.23 as default?? even when i try to change version then nothing happened.

I need check it, maybe you have some issues with remi repo version and this overwrite some thing

I supose you had 7.4 version because you upgrade it manually ? or your vestacp installer install it by default ?

[jesussuarez]

after installing the script i see a 500 error

In the error_log I see the following:

Code: Select all

[Mon May 09 22:39:45.905293 2022] [fcgid:warn] [pid 27706:tid 139955812632320] (104)Connection reset by peer: [client 190.158.204.148:17776] mod_fcgid: error reading data from FastCGI server

[Mon May 09 22:39:45.905353 2022] [core:error] [pid 27706:tid 139955812632320] [client 190.158.204.148:17776] End of script output before headers: index.php

any ideas?...

[sandro]

Have you tried doing this: viewtopic.php?f=19&t=10854#p40742

[jesussuarez]

Have you tried doing this: viewtopic.php?f=19&t=10854#p40742

hello

I did what you said and the result is as follows:

Code: Select all

[root@server root]# apachectl configtest
[Wed May 11 13:19:47.693242 2022] [so:warn] [pid 11236:tid 139884554270912] AH01574: module ruid2_module is already loaded, skipping
Syntax OK

also try to replace IncludeOptional for Include, after applying the changes, apache does not start again for sites that have sk template

[mikeman]

To troubleshoot the 500 error in VestaCP with the SK template and resolve the "Connection reset by peer" and "End of script output before headers" errors, please follow these detailed steps:

1. Check PHP-FPM Configuration:

Log in to your server via SSH.
Navigate to the PHP-FPM pool configuration directory. The path may vary depending on your operating system and PHP version. For example, it could be /etc/php-fpm.d/ or /etc/php/7.4/fpm/pool.d/.
Look for the configuration file associated with the domain or script causing the error (e.g., mydomain.com.conf).
Open the configuration file using a text editor.
Verify and adjust the following directives as necessary:
listen: Ensure it is set to the correct address and port, usually 127.0.0.1:9000.
listen.owner and listen.group: Confirm that the user and group ownership match those used by your web server (e.g., apache, www-data).
user and group: Ensure the correct user and group are specified.
Save the changes to the configuration file.

2. Restart PHP-FPM and Apache:

After modifying the PHP-FPM configuration, you need to restart both PHP-FPM and Apache for the changes to take effect.
Execute the following commands to restart PHP-FPM and Apache:

Code: Select all

sudo service php-fpm restart
sudo service apache2 restart

Note: The commands may vary depending on your operating system. For example, on CentOS, you can use sudo systemctl restart php-fpm and sudo systemctl restart httpd.

3. Verify the SK Template Configuration:

Log in to your VestaCP control panel.
Go to the "Web" section and click on the affected domain.
Under the "Web Template" section, make sure the correct PHP version and SK template are selected.
If you have made changes to the template, click on the "Rebuild Web" button to apply the changes.
Save the changes if any modifications were made.

4. Check Error Logs:

Examine the error logs for the domain to gather additional information about the issue. The error logs are usually located in the following directory: /home/<username>/log/<domain>/error.log.
Look for any new error messages that may help identify the root cause of the problem.

5. Verify Apache Configuration with SK Template:

If Apache fails to start after replacing IncludeOptional with Include in the Apache configuration, it might be due to incorrect configuration in the SK template.
To fix this, navigate to the directory where your SK template files are located. It is typically located in /usr/local/vesta/data/templates/web/sk.
Open the template file named web.conf or web.stpl using a text editor.
Search for the line that includes IncludeOptional and replace it with Include.
Save the changes to the template file.

6. Rebuild Web Configuration:

Log in to your VestaCP control panel.
Go to the "Web" section and click on the affected domain.
Under the "Web Template" section, click on the "Rebuild Web" button.
This will regenerate the Apache configuration files based on the modified SK template.

7. Restart Apache:

After rebuilding the web configuration, restart Apache using the following command:

Code: Select all

sudo service apache2 restart

By following these steps, you should be able to resolve the 500 error and the "Connection reset by peer" and "End of script output before headers" errors in VestaCP with the SK template. If the issue persists or you encounter any new error messages, please provide the relevant details, including the error logs, for further assistance.