New answers tagged

0

In the config (whether that be the main apache config or vhosts block) Add: RewriteEngine on RewriteRule "^/test/*" "/testhandler/" [PT] respectively. See: https://httpd.apache.org/docs/2.4/rewrite/ https://httpd.apache.org/docs/2.4/rewrite/remapping.html https://httpd.apache.org/docs/2.4/rewrite/flags.html


0

The issue turned out to be with the MX records as @anx pointed out. Additionally the SSL Certificate on the domain was not fully configured so that was also causing issues. Otherwise my local server configurations were set up correctly.


1

The Original Issue sounded like an Repository issue. And it was so. To fix that: Install automatically the Repository wget -O - http://rpms.litespeedtech.com/debian/enable_lst_debian_repo.sh | bash Fix Manually You may find outdated lines with grep -Ri litespeedtech /etc/apt/* Install the GPG Keys and Sources wget -qO - https://rpms.litespeedtech.com/...


0

Try running varnishlog -g request -q "ReqUrl eq '/'" to see what's going on when requesting the homepage. If you perform this command when the cache is empty, we should see an attempt by Varnish to connect with the backend. Please share the VSL output here and I'll assist. UPDATE I noticed in your docker-compose.yml file that your http container is ...


1

So, you're trying to funnel a particular virtualhost, through a pipe, that goes to a proxy module to access the host on loopback??? But only for PHP files? That sounds unnecessarily complicated. Why not run a second virtual host, on a secondary port, and use mod_proxy to handle the entire virtual host. (ie. generally "the way" to do an upgrade, and ...


0

I think not its the IIS server there have problems here, every thing you are search you request a new call in your code, and its look like something inside your PHP script its taking long time. Every time you sending a new request you just blocking a new PHP instants, and when PHP is running out of instants its crash. Its hard to know what you are doing ...


0

The solution was so simple I couldn't even think about it. I restarted php7.0-fpm and it solved the problem.


0

There are two main methods to install a new PHP version and tell Apache to use it: mod_php and php-fpm. Note: The preffered method is php-fpm, and many new distributions (including Fedora) are using it by default. Install PHP as Apache SAPI module Here is the guide around this for Unix systems, from the official documentation. It has some missing points (at ...


2

This may not be very helpful, but I was able to install php7.4-fpm on Ubuntu 18.04LTS with no errors. I originally needed php7.4 for use with Matomo. I used this writeup Update to PHP 7.4 on Ubuntu 18.04 on Digital Ocean for WordPress as applicable to my setup. I didn't technically need the php7.4-fpm, but decided to test it after seeing this post. Installed ...


0

Just I have change fastcgi_pass to the right source fastcgi_pass unix:/var/php-nginx/163014821416069.sock/socket; To fastcgi_pass unix:/run/php-fpm/www.sock;


1

This issue comes from nginx, in your nginx.conf set the following value: client_max_body_size 100M; Obviously if you want a bigger file size then 100MB, make this value higher You can read more about client_max_body_size in the nginx documentation: http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size


0

Similar, if not the same issue: PHP Warning: PHP Startup: Unable to load dynamic library 'mysql' (tried: /usr/lib64/php/modules/mysql (/usr/lib64/php/modules/mysql: cannot open shared object file: No such file or directory), /usr/lib64/php/modules/mysql.so (/usr/lib64/php/modules/mysql.so: undefined symbol: mysqlnd_get_client_info)) in Unknown on line 0 ...


2

It is a known bug on PECL mailparse since 2015, see #71813 Mailparse pecl install fails with php 7 #71181 Install failed : required mbstring then is enable (sic) If your distro doesn't provide mailparse on its repo, try downloading mailparse source from PECL and compiling it yourself. This is an good guide on doing that, and this is Zend's official guide ...


-1

You should be able to use the OPcache code within php itself to make sure you are not compiling php with each visitor hit to your site. Please be aware this will require a system memory allocation to hold cached compiled php. It can be much faster if your hit rate is high enough. If you have the memory to do it, you can even configure your MySQL query cache ...


Top 50 recent answers are included