We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on Vesta 2.0 and expect to release it by the end of 2024. Read more about it: https://vestacp.com/docs/vesta-2-development
How To Change Local Settings ? Topic is solved
Re: How To Change Local Settings ?
The problem that tpl file has php_admin_value post_max_size 64M and thus the master value is 64M, which is as expected, but - the local value is 8M and i do not know where to change the local value. How else can i explain it ...
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: How To Change Local Settings ?
Just manually Change / Add the directive php_admin_value post_max_size 72M in your Apache Virtual host file
/home/<Vesta-User>/conf/web/<domain-name>.apache2.conf
But this change will be lost if you do Rebuild-Web anytime.
Better edit the tpl file for which you have the pkg selected for the domain. It is a simple thing
/home/<Vesta-User>/conf/web/<domain-name>.apache2.conf
But this change will be lost if you do Rebuild-Web anytime.
Better edit the tpl file for which you have the pkg selected for the domain. It is a simple thing
Re: How To Change Local Settings ?
@xguntis huh? That template has the default value of 8M, example:
https://github.com/serghey-rodin/vesta/ ... ng.tpl#L19
https://github.com/serghey-rodin/vesta/ ... g.stpl#L20
Also, do not manually modify the conf file per @mehargags mention below: "But this change will be lost if you do Rebuild-Web anytime."
Better if you just pick a different template as I've stated before.
https://github.com/serghey-rodin/vesta/ ... ng.tpl#L19
https://github.com/serghey-rodin/vesta/ ... g.stpl#L20
Also, do not manually modify the conf file per @mehargags mention below: "But this change will be lost if you do Rebuild-Web anytime."
Better if you just pick a different template as I've stated before.
Re: How To Change Local Settings ?
Is anybody listening to me? :(
php_admin_value post_max_size changes the master value. Where to change local value?
php_admin_value post_max_size changes the master value. Where to change local value?
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: How To Change Local Settings ?
Are you reading / listening to anyone here posting results and trying to help you ? Are you even trying to define what you really want ?xguntis wrote:Is anybody listening to me? :(
php_admin_value post_max_size changes the master value. Where to change local value?
Re: How To Change Local Settings ?
Yes, I am reading that i need to change php_admin_value post_max_size in the Apache template file and that is what I have already done. This modifies only master value. But this does not help, because the local value is lower and local value prevails. I am trying to say it in every post here.
I am trying to change php_value post_max_size 999M in .htaccess, but it does not change the local value. phpinfo(); still shows the following:
I am trying to change php_value post_max_size 999M in .htaccess, but it does not change the local value. phpinfo(); still shows the following:
Re: How To Change Local Settings ?
Sorry everyone for confusion. After i had some technical support with experienced server guy, i discovered 2 things that i was wrong with:
1) php_admin_value post_max_size changes local value, not master one. Master values are probably set in /etc/php5/apache2/php.ini
2) which is more important - i am using ssl for these domains and therefore i had to modify hosting.stpl (not hosting.tpl). My wrong assumption was - because i use public_html instead of public_shtml directory the template is tpl, not stpl, which is WRONG.
Hope this will help someone not to do the same mistakes.
1) php_admin_value post_max_size changes local value, not master one. Master values are probably set in /etc/php5/apache2/php.ini
2) which is more important - i am using ssl for these domains and therefore i had to modify hosting.stpl (not hosting.tpl). My wrong assumption was - because i use public_html instead of public_shtml directory the template is tpl, not stpl, which is WRONG.
Hope this will help someone not to do the same mistakes.