Trustwave PCI (Payment Card Industry) compliance has just failed with 'The remote host is running a version of nginx that is no longer supported'. I am running the latest LTS version of ubuntu server 18.04 with the latest version of nginx 1.14.2.
I have looked on line, but I cant find a list of which versions of nginx are still supported/unsupported. I would like to find either a way to determine if 1.14.2 is supported, or an authoritative list to dispute the finding.
Thanks to #lex-li, everything listed under "legacy" is unsupported here, though I thought nginx 1.14.2 was the latest because using the ppa for a stable version of nginx, apt install was telling me that it was the latest version. Recently nginx must have changed their install so that if you want to upgrade past 1.14, you need to uninstall nginx, then follow the instructions here
Related
I updated nginx from version 1.14 to 1.18 (Ubuntu) on Ubuntu 18.04.
Doing so appeared to break passenger. So I uninstalled and attempted to reinstall the Open Source Passenger version via the Passenger installation Ubuntu 18.04 instructions.
I got to this line:
sudo apt-get install -y libnginx-mod-http-passenger
Which throws this error
libnginx-mod-http-passenger : Depends: nginx-common (< 1.14.1) but 1.18.0-3ubuntu1+bionic1 is to be installed
Update I also attempted with the enterprise version. Following the enterprise version installation instructions, I received a similar error message:
libnginx-mod-http-passenger-enterprise : Depends: nginx-common (< 1.14.1) but 1.18.0-3ubuntu1+bionic1 is to be installed
I did attempt to research the issue and I found this issue on Phusion's GitHub as well as this more recent issue. It appears that what most people are doing is rolling back their nginx version to 1.14.
It is not deprecated, no. The problem is that the packaged module you are trying to install was made for an older Nginx version that is distributed through the system default repository. This appears in the installation guide that you've mentioned:
At this point we assume that you already have Nginx installed from your system repository.
What this means is that the following instructions assume that you have Nginx specific version (1.14.0 in your case) installed, for which the packaged module was built. This is emphasised in the new passenger documentation:
If you want to use our packaged Nginx module, you must use your distro's provided Nginx package. If for example you have the repo provided by NGINX setup, you will instead need to compile a dynamic module compatible with that Nginx.
The link in the last quote will bring you to the guide on how to compile a dynamic passenger module and enable it in Nginx configuration. I will not repeat the whole process to keep the answer short but the general approach is this:
Get passenger module for Nginx source code.
Get Nginx source code for the version you have installed.
Compile Nginx with the passenger module:
cd /path-to-nginx-source-dir
./configure --prefix=/opt/nginx \
--with-some-configure-flag \
--add-dynamic-module=$(passenger-config --nginx-addon-dir) \
--add-module=/path-to-some-other-nginx-module
make
sudo make install
Make Nginx to load the module by adding this line to nginx.conf:
load_module modules/ngx_http_passenger_module.so;
Personally, I'd rather chosen the 'nginx-behind-nginx' approach than building the module. That is you have Nginx any version you like but it runs as a reverse proxy for another Nginx with passenger enabled (Passenger Standalone). With an unnoticeable penalty to performance this will be much easier to maintain (install, update). See this guide for details.
I am planning to upgrade artifactory-pro from 4.14.2 to 5.7. Has anyone done this so far? We use npm, bower, debian, yum repositories. Any recommendation or insight is appreciated.
As I see it, the upgrade depends on two main factors:
Your installation type(ZIP/RPM/RPM OSS/Debian/Docker). Here you can find detailed instructions for each type:
ZIP installation
RPM installation
RPM OSS installation
Debian installation
Docker installation
In case you use an HA cluster, here are the instructions.
While no special operations are required except those are mentioned in the instructions - please pay attention to updates and other special instructions since there are specific instructions to upgrading from Artifactory 4.x to 5.4.x and above. As can be seen here (for example).
Like in any other upgrade process, make sure you have a full system backup (Artifactory configuration, metadata, and artifacts)
I have deployed graphite with nginx some time ago, with chef, but didn't froze versions to be installed. Thus now, trying to install with the same recipe i get errors because of missing something related to versions.
I need to find what version of Graphite I have installed on my other CentOS machines, to be able to figure out how to repair recipe.
Thank you.
Gabriel
If you have web access to the Graphite installation, you can also see the currently running version under the /version/ path.
I had the same issue. I solved it running a pip list, which displays every package you installed with pip. You can also run pip show graphite-web or pip show whisper to get more specific information.
I have used Valet without problems for nearly a year, though occasionally needed a restart or reinstall to get it going. Yesterday I upgraded to a fresh valet 2.0.3 and as a result and ever since then there is no connection in the browser to any of my *.dev hosts (though there is appropriate ping response in the terminal).
Have executed brew update and tried a full reinstall several times (with preceding brew uninstall dnsmasq / php70 etc). There is no error or warning during installation process. Error logs remain empty even after valet start / restart / park commands. Also, there are apparently no caddyfile and Caddy directory generated neither in ~/.valet nor in ~/.composer/vendor/bin/laravel/valet.
An attempt to download Caddy from github and apply it like hinted here had no effect.
As I need valet badly for my work I have researched night and day for any solution, but not succeeded yet. Any hints welcome.
Valet 2 utilizes no more Caddy, but nginx instead. The solution is to uninstall the present nginx via brew and let nginx get reinstalled during the valet installation procedure. As described here by Switzer: https://laracasts.com/discuss/channels/laravel/valet-2-upgrade-all-sites-refuse-to-connect
I have apache version:
Server version: Apache/2.4.10 (Unix)
Server built: Oct 26 2014 13:31:18
I want to update apache version for http2 support. But simply adding http2 module in httpd.conf give error saying that module not found and sudo apt-get install --only-upgrade apache also doesn't work. Didn't find any solution on internet. How can I upgrade apache?
If you're using a Bitnami WordPress Stack, you have to understand that the Apache installed on the Stack is not installed by apt-get install XXX actions. Therefore, you can't upgrade it that way.
My recommendation install the new WordPress Stack available at https://bitnami.com/stack/wordpress (this way you're installing the latest version of Apache, PHP, MySQL, etc.) and then migrate your WP from the old stack to the new one as explained in the guide below:
https://docs.bitnami.com/google/how-to/migrate-wordpress/
After that, you can remove the old Stack.