You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How can I specify the location of valid certificates for enterprise manager and ords?
On the command line within the newly running docker image, I get:
bash-4.2# curl -ISs https://localhost:5500/em
curl: (60) Issuer certificate is invalid.
bash-4.2# curl -ISs https://localhost:8080/ords
curl: (35) SSL received a record that exceeded the maximum permissible length.
Outside the container, I get:
curl -ISs https://localhost:55500/em
curl: (35) Encountered end of file
curl -ISs https://localhost:50080/ords
curl: (35) SSL received a record that exceeded the maximum permissible length.
I can use Firefox to browse to http://localhost:50080/ords and put in an exception to run insecure but I can't get Firefox to bring up enterprise manager at all.
I need to find a way to get valid certificates for both Enterprise Manager and ORDS.
Thanks
Raymond Cordoni
The text was updated successfully, but these errors were encountered:
How can I specify the location of valid certificates for enterprise manager and ords?
On the command line within the newly running docker image, I get:
bash-4.2# curl -ISs https://localhost:5500/em
curl: (60) Issuer certificate is invalid.
bash-4.2# curl -ISs https://localhost:8080/ords
curl: (35) SSL received a record that exceeded the maximum permissible length.
Outside the container, I get:
curl -ISs https://localhost:55500/em
curl: (35) Encountered end of file
curl -ISs https://localhost:50080/ords
curl: (35) SSL received a record that exceeded the maximum permissible length.
I can use Firefox to browse to http://localhost:50080/ords and put in an exception to run insecure but I can't get Firefox to bring up enterprise manager at all.
I need to find a way to get valid certificates for both Enterprise Manager and ORDS.
Thanks
Raymond Cordoni
The text was updated successfully, but these errors were encountered: