Nexus repository 3 pro HTTPS fail

Sonatype Nexus Repository
1

Hello. Regarding the https setting, please contact us as follows.

[Infrastructure configuration]

  • VIP(Virtual IP) → LB(sticky session) → node1,2,3 jetty 8080, 443 (hacluster) → blob(nfs)
  • 80 to 8080
  • 443 to 443

[trial1]

  • VIP(80) to jetty(8080) Proceed after setting
  • Library download and deployment confirmed normally
  • Ajax cross domain error occurs when accessing web administrator
  • restoration

[trial2]

  • reference url : Configuring SSL
    * Refer to Serving SSL Directly in the document
  • /opt/nexus/etc/nexus.properties change
    ${jetty.etc}/jetty-https.xml addition
    application-port-ssl=443 addition
    ssl.etc=#{karaf}/etc/ssl addition
  • jetty-https.xml change
    change path
  • After the above failed, /opt/nexusdata/nexus/etc/nexus.properties was changed, but the same result
  • Result: Failed 443 Process Disabled

No error log occurs when accessing the browser https.
The problem is confirmed that the 443 process does not come up.
Is there any other setting method other than the above method?Hello. Regarding the https setting, please contact us as follows.

[Infrastructure configuration]

  • VIP(Virtual IP) → LB(sticky session) → node1,2,3 jetty 8080, 443 (hacluster) → blob(nfs)
  • 80 to 8080
  • 443 to 443

[trial1]

  • VIP(80) to jetty(8080) Proceed after setting
  • Library download and deployment confirmed normally
  • Ajax cross domain error occurs when accessing web administrator
  • restoration

[trial2]

  • reference url : Configuring SSL
    * Refer to Serving SSL Directly in the document
  • /opt/nexus/etc/nexus.properties change
    ${jetty.etc}/jetty-https.xml addition
    application-port-ssl=443 addition
    ssl.etc=#{karaf}/etc/ssl addition
  • jetty-https.xml change
    change path
  • After the above failed, /opt/nexusdata/nexus/etc/nexus.properties was changed, but the same result
  • Result: Failed 443 Process Disabled

No error log occurs when accessing the browser https.
The problem is confirmed that the 443 process does not come up.
Is there any other setting method other than the above method?

2

On Linux/Unix access to port 443 is blocked by default.

Probably you would need to consult documentation for your OS around CAP_NET_BIND_SERVICE

3

We are using centos.
When issuing a server within the company, the default ports (80, 8080, 443, etc…) are in the open state of the firewall.
Are there any other areas to check?

4

The firewall isn’t going to be the problem here, as it only blocks incoming traffic. The problem is that you are on a linux OS which by default doesn’t allow processes to use the 443 port. Here’s an article that shows some ways to open the port How to open PORT : 443 | DigitalOcean.