# Nexus repository 3 pro HTTPS fail

**URL:** <https://community.sonatype.com/t/nexus-repository-3-pro-https-fail/7214>\
**Category:** Sonatype Nexus Repository\
**Tags:** nexus-repository\
**Created:** [August 31, 2021, 3:29am UTC](https://community.sonatype.com/t/nexus-repository-3-pro-https-fail/7214 "2021-08-31T03:29:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![netmarble](https://avatars.discourse-cdn.com/v4/letter/n/46a35a/32.png) [@netmarble](https://community.sonatype.com/u/netmarble)\
**Post date:** [August 31, 2021, 3:29am UTC](https://community.sonatype.com/t/nexus-repository-3-pro-https-fail/7214/1 "2021-08-31T03:29:14Z")

</div>

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](https://help.sonatype.com/repomanager3/system-configuration/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](https://help.sonatype.com/repomanager3/system-configuration/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?

---

<div class="post-metadata">

**Author:** ![mpiggott](https://avatars.discourse-cdn.com/v4/letter/m/f0a364/32.png) [@mpiggott](https://community.sonatype.com/u/mpiggott)\
**Post date:** [September 1, 2021, 5:01pm UTC](https://community.sonatype.com/t/nexus-repository-3-pro-https-fail/7214/2 "2021-09-01T17:01:23Z")

</div>

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**

---

<div class="post-metadata">

**Author:** ![netmarble](https://avatars.discourse-cdn.com/v4/letter/n/46a35a/32.png) [@netmarble](https://community.sonatype.com/u/netmarble)\
**Post date:** [September 2, 2021, 2:50am UTC](https://community.sonatype.com/t/nexus-repository-3-pro-https-fail/7214/3 "2021-09-02T02:50:31Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![mmartz](https://avatars.discourse-cdn.com/v4/letter/m/e9bcb4/32.png) [@mmartz](https://community.sonatype.com/u/mmartz)\
**Post date:** [September 2, 2021, 1:05pm UTC](https://community.sonatype.com/t/nexus-repository-3-pro-https-fail/7214/4 "2021-09-02T13:05:50Z")

</div>

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](https://www.digitalocean.com/community/questions/how-to-open-port-443).