Jordan Ramstad's questions

Seems simple, but I have been unable to install any version other then php 7.4 reliably on fedora 33 (32 seems to have the same issue according to remi).

PHP 7.4 is the default install, but the project I need to work is locked to 7.3 atm due to dependencies that don't work in 7.4 yet.

Remi repositories cannot install below 7.4 either, only multiple versions can get 7.3, however if you do that, it also installs 7.4 and although you can tell nginx to use 7.3, cli is locked to 7.4 (I bet you can do something about that, just not sure how, basically gotta use php73 rather then php for cli commands).

Using the wizard for Fedora 33 can show the versions available and how. https://rpms.remirepo.net/wizard/

Is there a way to reliably get php 7.3 working on Fedora 33? I don't mind multi version as long as both cli and fpm can be using the same version.

I have setup a reverse proxy, sending requests from nginx (openresty) to apache, using this is only to allow more control through openresty to check the requests, but essentially the server is running on apache.

The problem is that apache is on port 8080, and nginx on 80, so whenever apache does a redirect it redirects to port 8080 and I have not found any conclusive way to prevent this and instead have it go to port 80.

My server config for nginx is the following

server {
  listen 80 default_server;
  server_name localhost;
  client_max_body_size 1024m;
  client_body_timeout 300s;

  location / {
    proxy_pass http://127.0.0.1:8080;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
  }
}

No lua added yet though.

As for Apache:

<VirtualHost *:8080>
  UseCanonicalName Off
  ServerName domain.com
  ServerAdmin [email protected]
  DocumentRoot /home/user1/environments/production
</VirtualHost>

<VirtualHost *:8080>
  ServerAlias *.*.domain.com
  VirtualDocumentRoot /home/%2/environments/%1
</VirtualHost>

<VirtualHost *:8080>
  ServerAlias *.domain.com
  VirtualDocumentRoot /home/%1/environments/production
</VirtualHost>

This works but if apache does any sort of redirect it redirects though port 8080. I effectively want to close off port 8080 from being accessed through anything other then nginx, but through nginx apache should be running as if it were also on port 80.

Similar questions have been asked about this but none have seemed to shed any light on this issue.

I am using PHP 5.6.18 on Ubuntu 14.04. The server its on is an in-office server with an 8 core CPU (not sure exact model) and 8 gb of RAM. This server has run without so much as a peep for about 2.5 years, I have done maintenance on it and it was originally on Ubuntu 12.04 with an older version of php, but upgraded it as time went on. The last time I did any updating was around 6 months ago and no issues.

The general setup is nginx passing requests to apache for cms development, and we have various work applications running directly off of nginx.

However in the last few days, PHP-FPM (CLI/APACHE PHP works fine) seems to crash every 5 or so minutes, sometimes it lasts for longer, even typically fine overnight. There is no load on the server itself, Logs only show that php timed out on the request, and then will not process any further requests until restarted.

The weird thing is nothing has been done to the server recently, this just started up randomly about 3 days ago with no noticeable cause. Every effort (resintalling php/mysql, restarting whole server, ect) has ended in failure.

Here is part of my main nginx config (I have changed these values many times now trying various things, right now most is disabled).

   #client_header_timeout 600;
   #client_body_timeout 600;
   #fastcgi_read_timeout 600;
   client_max_body_size 2048m;
   #fastcgi_buffers 8 4k|8k;
   #fastcgi_buffers 8 128k;
   #fastcgi_buffer_size 128k;
   #client_max_body_size 2048M;
   send_timeout 900;
   #fastcgi_read_timeout 3000;
   sendfile on;
   tcp_nopush on;
   tcp_nodelay on;
   keepalive_timeout 65;
   types_hash_max_size 2048;
   # server_tokens off;

   # server_names_hash_bucket_size 64;
   # server_name_in_redirect off;

Here is an error

upstream timed out (110: Connection timed out) while reading response header from upstream

I used to have the timeout at about 10 mins and that worked well considering it was a dev only server, brought it down to 60 seconds to get the errors to come in quicker now.

Anyone else run into this? or know of something it could be that I am just failing to see?