Hello there,
I am currently testing the upgrade of our nexus from 3.77.2 to 3.78.2 on a preprod environment and after the upgrade, the URL of our nexus gives a “404 not found” and in the apache log I found the error “failed to make connexion to backend”.
The nexus is installed on a debian 12 lxc container, I’ve used the nexus-unix-x86-64 package and had to follow this discussion to make the nexus start :
Shell Compatibility Issue in Nexus Repository 3.78.2-04 Startup Script (I’ve replaced the first line of the nexus bin file with “#!/bin/bash”)
Nexus sonatype start and doesn’t have any error in its log files, only our apache proxy has some logs. Any of you encountered this problem ? I don’t see anything unusual in our apache conf file that has always worked and I have the same error if I try to upgrade to nexus 3.82.0 with the linux x86_64 package. There is no issue with the database connection.
Here is our apache configuration file with anonymisation :
<VirtualHost *:443>
ServerName <DNS hostname>
ServerSignature Off
RewriteEngine on
RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK)
RewriteRule .* - [F]
ProxyRequests Off
ProxyPreserveHost On
ProxyTimeout 300
ProxyPass /nexus http://localhost:8081/nexus nocanon
ProxyPassReverse /nexus http://localhost:8081/nexus
Header edit Location ^http://(.*)$ https://$1
RequestHeader set X-Forwarded-Proto "https"
RequestHeader set X-Forwarded-Port "443"
<Location />
Order deny,allow
Allow from all
</Location>
AllowEncodedSlashes NoDecode
SSLEngine On
RequestHeader set X_FORWARDED_PROTO 'https'
SSLCertificateFile <path/to/file>
SSLCertificateKeyFile <path/to/file>
SSLCertificateChainFile <path/to/file>
# HSTS (mod_headers is required) (15768000 seconds = 6 months)
Header always set Strict-Transport-Security "max-age=15768000"
ErrorLog /var/log/apache2/<filename>.log
LogLevel warn
CustomLog /var/log/apache2/<filename>.log combined
</VirtualHost>
Thanks,