Database Express Setup: This site can not be reached

Note: These steps are for TEST non-production databases only.

Configuring/enabling EM express on HTTPS should be simple, by running only:


But after configuring it you may still not be able to access the web page and show the error “This site can’t be reached”

The reason for this can be permissions on the wallet files:

[grid@rac1 ~]$ ll /u01/app/oracle/product/19.3.0/dbhome_1/admin/orcl/xdb_wallet
total 8
-rw------- 1 oracle asmadmin 3864 Apr 15 17:40 cwallet.sso
-rw------- 1 oracle asmadmin 3819 Apr 15 17:40 ewallet.p12

The correct permission is 600, but when database is on top of ASM with role separation, then group should also have read permission on these files:

[root@rac1 ~]# chmod 640 /u01/app/oracle/product/19.3.0/dbhome_1/admin/orcl/xdb_wallet/*

After changing it, the web page is displayed.

Configure SSL Connections on Report Server(https)

You must have a server certificate installed on the computer. Ask for the certificate to your sysadmins(windows admins), or request a certificate from a trusted certificate authority.

The following steps do not include instructions for requesting, generating, downloading, or installing a certificate. You must have a certificate installed and available to use.

So let’s start.

1. Run Reporting Services Configuration Manager and connect to the reporting server.

2. In Web Service URL section –> SSL Certificate –> choose your certificate –> click Apply.

3. Report Manager URL section –> Advanced button –> Multiple SSL identities for Report Manager section –>

click Add button –> in Certificate choose your certificate and click OK –> OK.

4. Stop and Start your Reporting service, from the first section of the configuration manager.

5. Check that the URL works by indicating https instead of http.