Hello
I found a solution - Pax Web tries to validate whether
etc/org.ops4j.pax.web.cfg matches the runtime-specific configuration
In PID config you have:
org.osgi.service.http.secure.enabled = true
org.osgi.service.http.port.secure = 8443
org.ops4j.pax.web.listening.addresses=127.0.0.1
So Pax W
Hi Grzegorz,
Thank you so much for looking into this.
Here is entire information for etc/org.ops4j.pax.web.cfg, etc/jetty.xml and
logs.
Entire org.ops4j.pax.web.cfg File :
org.osgi.service.http.port=8181
org.osgi.service.http.secure.enabled=true
org.osgi.service.http.port.secure=8443
org.ops4j.
Hello
Please show me your entire:
- etc/org.ops4j.pax.web.cfg
- etc/jetty.xml
- logs
I've just checked with Karaf 4.4.1 and this SSL configuration works fine:
org.osgi.service.http.secure.enabled = true
org.osgi.service.http.port.secure = 8443
org.ops4j.pax.web.ssl.truststore = ${karaf
