My Oracle Support Banner

OHS Is Listening On 443 But Clients Can't Connect (Doc ID 2212881.1)

Last updated on NOVEMBER 09, 2020

Applies to:

Java Cloud Service - Version 14.1 to 14.1
Information in this document applies to any platform.


OHS is listening on 443 but clients can't connect

When running OHS in a JCS instance, clients (chrome/firefox/curl) are unable to reach OHS on port 443 though 443 is open and server is listening on 443.

However, when we use 8002 port, clients are able to reach OHS.

To OHS be listened on 443 for https we followed the steps described here:
(special configuration is required to allow Oracle HTTP Server to bind to privileged ports.)

OHS is able to start successfully when listened on 443. Success entry from OHS logs:

[2016-12-10T08:11:39.0485+00:00] [OHS] [NOTIFICATION:16] [OHS-9999] [core.c] [host_id: xxxx-wls-1] [host_addr:] [pid: <pid>] [tid: <thread_id>] [user: <user>] [VirtualHost: main] Oracle-Application-Server-12c/ Oracle-HTTP-Server (Unix) mod_ssl/ OtherSSL/0.0.0 mod_plsql/ configured -- resuming normal operations

Directive used in ssl.conf of apache:
Listen *:443

443 port is open in Access Rules.

Other information before doing configuration:
We earlier faced following issue before doing special configuration to allow Oracle HTTP Server to bind to privileged ports.
[2016-12-09T20:12:50.5621+00:00] [OHS] [INCIDENT_ERROR:32] [OHS-9999] [worker.c] [host_id: xxxx-wls-1] [host_addr:] [pid: <pid>] [tid: <thread_id>] [user: <user>] [VirtualHost: main] (13)Permission denied: make_sock: could not bind to address




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.