.
Understanding Nexus Repository Product Version Format
Nexus Repository product versions use this format:
{semantic product version}-{build number}
Semantic product version format style:
{major version}.{minor version}.{patch version}
How to find the Nexus Repository version using a web browser
From a desktop web browser, visit the url where Sonatype Nexus Repository is running.
Locate the product version in the page header.
Nexus Repository 3 has the full product version and edition on the left top.
Nexus Repository Manager 2 has the full product version on the right top.
How to find the Nexus Repository version using System Information
- From a desktop web browser, visit the url where Sonatype Nexus Repository is running.
- Login as a user with the admin role
-
Nexus Repository 3
Click the administration cog icon, then navigate to Administration -> Support -> System Information:
Nexus Repository Manager 2
Navigate to Administration > Support Tools -> System Information tab:
How to find the Nexus Repository Version Using HTTP Response Server Header
HTTP responses from Nexus Repository include a "Server" header that contains the full product version.
Nexus Repository 3
Using an HTTP client such as curl, make the following type of request from the command line:
curl -sSkI http://localhost:8081/
- replace http://localhost:8070 with your own base URL, including any custom context path
- by default there is no custom context path. Your deployment may have customized the context path to the application and that should be appended to the request ending with slash
The Server header value has this format:
{product http name}/{major version}.{minor version}.{patch version}-{build number} {edition}
If the Server header contains "Jetty", then that is usually a sign you have not constructed the correct base url to the application.
Example response:
HTTP/1.1 200 OK
Date: Thu, 04 Jan 2024 18:44:41 GMT
Server: Nexus/3.63.0-01 (PRO)
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
Content-Type: text/html
Last-Modified: Thu, 04 Jan 2024 18:44:41 GMT
Pragma: no-cache
Cache-Control: no-cache, no-store, max-age=0, must-revalidate, post-check=0, pre-check=0
Expires: 0
Content-Length: 8166
In this example, the Server header reports these values:
Product HTTP Name: Nexus
Full product version: 3.63.0-01
Semantic product version: 3.63.0
Major version: 3
Major version: 63
Minor version: 0
Build number: 01
Edition: Pro
Nexus Repository Manager 2
Using an HTTP client such as curl, make the following type of request from the command line:
curl -sSkI http://localhost:8081/nexus/
- replace http://localhost:8070/nexus/ with your own base URL, including any custom context path
- /nexus/ in this example is the default custom context path. Your deployment may have removed this path or changed it to some other value.
The Server header value has this format:
{product http name}/{major version}.{minor version}.{micro version}-{build number}
If the Server header contains "Jetty", then that is usually a sign you have not constructed the correct base url to the application.
Example response:
HTTP/1.1 200 OK
Date: Thu, 04 Jan 2024 18:36:42 GMT
Server: Nexus/2.15.1-02
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Content-Type: text/html
Last-Modified: Thu, 04 Jan 2024 18:36:42 GMT
Pragma: no-cache
Cache-Control: post-check=0, pre-check=0
Expires: 0
Content-Length: 9917
In this example, the Server header reports these values:
Product HTTP Name: Nexus
Full product version: 2.15.1-02
Semantic product version: 2.15.1
Major version: 2
Major version: 15
Minor version: 1
Build number: 02