sendHttpGetRequest not working under OH 2.4 M7 after Update from 2.3

Hmm, that should be fine :thinking:

Too bad, you could maybe post the output of bundle:list but most likely is was a different problem then the one I solved :cry:

Logging is the same, Trace logging is now on:

2018-12-16 20:16:51.352 [DEBUG] [ntime.internal.engine.RuleEngineImpl] - Executing rule 'Judo'

==> /var/log/openhab2/events.log <==

2018-12-16 20:16:51.366 [vent.ItemStateChangedEvent] - testswitch changed from OFF to ON

==> /var/log/openhab2/openhab.log <==

2018-12-16 20:16:51.383 [INFO ] [.eclipse.smarthome.model.script.Judo] - 1

2018-12-16 20:16:51.398 [DEBUG] [t.http.internal.WebClientFactoryImpl] - shared http client requested

2018-12-16 20:16:51.402 [DEBUG] [lipse.smarthome.io.net.http.HttpUtil] - About to execute https://192.168.178.28:8124?group=register&command=login&msgnumber=2&name=login&user=&password=&role=customer

2018-12-16 20:16:51.985 [TRACE] [http.internal.ExtensibleTrustManager] - Searching trustManager by Subject Alternative Names: []

2018-12-16 20:16:51.988 [TRACE] [http.internal.ExtensibleTrustManager] - No specific trust manager found, falling back to default

2018-12-16 20:16:51.995 [ERROR] [.smarthome.model.script.actions.HTTP] - Fatal transport error: java.util.concurrent.ExecutionException: javax.net.ssl.SSLHandshakeException: General SSLEngine problem

2018-12-16 20:16:51.999 [INFO ] [.eclipse.smarthome.model.script.Judo] - null

2018-12-16 20:16:52.002 [INFO ] [.eclipse.smarthome.model.script.Judo] - 2

2018-12-16 20:16:55.012 [INFO ] [.eclipse.smarthome.model.script.Judo] - 3

2018-12-16 20:16:55.017 [INFO ] [.eclipse.smarthome.model.script.Judo] - null

2018-12-16 20:16:55.034 [DEBUG] [t.http.internal.WebClientFactoryImpl] - shared http client requested

2018-12-16 20:16:55.039 [DEBUG] [lipse.smarthome.io.net.http.HttpUtil] - About to execute https://192.168.178.28:8124?group=register&command=connect&msgnumber=5&token=null&parameter=i-soft%20plus&serial%20number=

2018-12-16 20:16:55.127 [TRACE] [http.internal.ExtensibleTrustManager] - Searching trustManager by Subject Alternative Names: []

2018-12-16 20:16:55.131 [TRACE] [http.internal.ExtensibleTrustManager] - No specific trust manager found, falling back to default

2018-12-16 20:16:55.141 [ERROR] [.smarthome.model.script.actions.HTTP] - Fatal transport error: java.util.concurrent.ExecutionException: javax.net.ssl.SSLHandshakeException: General SSLEngine problem

2018-12-16 20:16:58.150 [INFO ] [.eclipse.smarthome.model.script.Judo] - 4
START LEVEL 100 , List Threshold: 50
 ID │ State    │ Lvl │ Version                │ Name
────┼──────────┼─────┼────────────────────────┼────────────────────────────────
 20 │ Active   │  80 │ 5.3.1.201602281253     │ OSGi JAX-RS Connector
 21 │ Active   │  80 │ 2.7.0.v20170129-0911   │ Gson: Google Json Library for
 22 │ Active   │  80 │ 18.0.0                 │ Guava: Google Core Libraries f
 23 │ Active   │  80 │ 3.0.0.v201312141243    │ Google Guice (No AOP)
 24 │ Active   │  80 │ 3.18.1.GA              │ Javassist
 26 │ Active   │  80 │ 3.5.5                  │ JmDNS
 28 │ Active   │  80 │ 1.0.0                  │ Units of Measurement API
 30 │ Active   │  80 │ 1.1.0.Final            │ Bean Validation API
 31 │ Active   │  80 │ 2.0.1                  │ javax.ws.rs-api
 32 │ Active   │  80 │ 3.2.0.v201101311130    │ ANTLR Runtime
 35 │ Active   │  80 │ 3.2.1                  │ Commons Collections
 36 │ Active   │  80 │ 1.1                    │ Commons Exec
 37 │ Active   │  80 │ 2.2.0                  │ Commons IO
 38 │ Active   │  80 │ 2.6                    │ Commons Lang
 47 │ Active   │  80 │ 4.2.1                  │ Apache Karaf :: OSGi Services
 63 │ Active   │  80 │ 4.6.0                  │ Apache XBean OSGI Bundle Utili
 64 │ Active   │  80 │ 4.6.0                  │ Apache XBean :: Classpath Reso
 65 │ Active   │  80 │ 2.12.0.v20160420-0247  │ EMF Common
 66 │ Active   │  80 │ 2.12.0.v20160420-0247  │ EMF Ecore
 67 │ Active   │  80 │ 2.11.0.v20160420-0247  │ EMF Change Model
 68 │ Active   │  80 │ 2.12.0.v20160420-0247  │ EMF XML/XMI Persistence
 69 │ Active   │  80 │ 3.8.0.v20160509-1230   │ Common Eclipse Runtime
 70 │ Active   │  80 │ 3.6.100.v20160223-2218 │ Extension Registry Support
 80 │ Active   │  80 │ 9.4.11.v20180605       │ Jetty :: Proxy
 94 │ Active   │  80 │ 0.4.1.v20180515-1321   │ org.eclipse.lsp4j
 95 │ Active   │  80 │ 0.4.1.v20180515-1321   │ org.eclipse.lsp4j.jsonrpc
 96 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome OAuth2Client
 97 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Config Core
 98 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Configuratio
 99 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Configuratio
100 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Config Dispa
101 │ Active   │  75 │ 0.10.0.201812160950    │ Eclipse SmartHome Config XML
102 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Core
103 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Core Audio
104 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Core Binding
105 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Core ID
106 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Core Persist
107 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Scheduler Se
108 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Core Semanti
109 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Core Thing
110 │ Active   │  75 │ 0.10.0.201812160950    │ Eclipse SmartHome Core Thing X
111 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Transformati
112 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Core Voice
113 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Console
114 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Console for
115 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome HTTP Interfa
116 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome JavaSound I/
117 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Monitor
118 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Net I/O Bund
119 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome REST Interfa
120 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Core REST API
121 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome REST mDNS An
122 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome REST Interfa
123 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Sitemap REST
124 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome SSE REST API
125 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Voice REST A
126 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Bonjour/MDS
127 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Web Audio Su
128 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Model Core
129 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Item Model
130 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Item Model I
131 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Item Model R
132 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Language Ser
133 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Persistence
134 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Persistence
135 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Persistence
136 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Rule Model
137 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Rule Model I
138 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Rule Runtime
139 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Script
140 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Script Model
141 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Script Runti
142 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Sitemap Model
143 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Sitemap Mode
144 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Sitemap Runt
145 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Thing Model
146 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Thing Model
147 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Thing Model
148 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Json Storage
149 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome UI
150 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome UI Icons
151 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Classic Icon
152 │ Active   │  80 │ 2.14.0.v20180522-1629  │ Xtend Runtime Library
153 │ Active   │  80 │ 2.14.0.v20180522-1629  │ Xtend Macro Interfaces
154 │ Active   │  80 │ 2.14.0.v20180522-1821  │ Xtext
155 │ Active   │  80 │ 2.14.0.v20180522-1833  │ Xtext Common Types
156 │ Active   │  80 │ 2.14.0.v20180522-1821  │ Xtext IDE Core
157 │ Active   │  80 │ 2.14.0.v20180522-1821  │ Xtext Utility
158 │ Active   │  80 │ 2.14.0.v20180522-1833  │ Xbase Model
159 │ Active   │  80 │ 2.14.0.v20180522-1833  │ Xbase Generic IDE Services
160 │ Active   │  80 │ 2.14.0.v20180522-1629  │ Xbase Runtime Library
175 │ Active   │  80 │ 1.9.6                  │ MIME streaming extension
177 │ Active   │  80 │ 6.2.0                  │ org.objectweb.asm
178 │ Active   │  80 │ 6.2.0                  │ org.objectweb.asm.commons
179 │ Active   │  80 │ 6.2.0                  │ org.objectweb.asm.tree
180 │ Active   │  90 │ 2.4.0.201812141755     │ openHAB Core
181 │ Active   │  80 │ 2.4.0.201812141755     │ openHAB Karaf Integration
183 │ Resolved │  80 │ 2.4.0.201812141755     │ openHAB Sound Support, Hosts:
184 │ Active   │  80 │ 2.4.0.201812141755     │ openHAB Dashboard UI
189 │ Active   │  80 │ 1.0.2                  │ Units of Measurement Common Li
190 │ Active   │  80 │ 1.0.8                  │ Units of Measurement Implement
191 │ Active   │  80 │ 2.3.0.201805272207     │ Xiaomi Mi IO Binding
192 │ Active   │  80 │ 2.4.0.201811041600     │ Amazon Echo Control Binding
193 │ Active   │  80 │ 2.1.0                  │ json-path
194 │ Active   │  80 │ 2.2                    │ json-smart
195 │ Active   │  80 │ 1.6.0                  │ Commons Codec
196 │ Active   │  80 │ 3.3.0                  │ Commons Net
197 │ Active   │  80 │ 4.2.3                  │ Apache HttpClient OSGi bundle
198 │ Active   │  80 │ 4.2.3                  │ Apache HttpCore OSGi bundle
199 │ Active   │  80 │ 3.1.0.7                │ Apache ServiceMix :: Bundles :
200 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Astro Binding
201 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Homematic Bi
202 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Configuratio
203 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome IoT Marketpl
204 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome UPnP Transpo
205 │ Active   │  75 │ 0.10.0.201812160950    │ Eclipse SmartHome JSonPath Tra
206 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Basic UI, Fr
207 │ Active   │  80 │ 0.10.0.201812160950    │ Eclipse SmartHome Paper UI, Fr
208 │ Active   │  80 │ 2.5.1                  │ JUPnP Library
209 │ Active   │  80 │ 1.13.0.201812161009    │ openHAB CalDav Command Binding
210 │ Active   │  80 │ 1.13.0.201812161009    │ openHAB CalDav Binding
211 │ Active   │  80 │ 1.13.0.201812161009    │ openHAB HTTP Binding
212 │ Active   │  80 │ 1.13.0.201812161009    │ openHAB MQTT Binding
213 │ Active   │  80 │ 2.4.0.201812151803     │ SomfyTahoma Binding
214 │ Active   │  80 │ 2.4.0.201812141755     │ openHAB 1.x Compatibility Layer
215 │ Active   │  80 │ 1.13.0.201812161009    │ openHAB CalDav Calendar
216 │ Active   │  80 │ 2.4.0.201812141755     │ Hue Emulation Service
217 │ Active   │  80 │ 1.13.0.201812161009    │ openHAB MQTT Transport Bundle
218 │ Active   │  80 │ 1.13.0.201812161009    │ openHAB RRD4j Persistence Bund
219 │ Resolved │  75 │ 2.4.0.201812141755     │ openHAB Basic UI Fragment, Hos
220 │ Active   │  80 │ 2.4.0.201812141755     │ HABPanel User Interface
221 │ Active   │  80 │ 2.4.0.201812141755     │ HomeBuilder User Interface
222 │ Resolved │  75 │ 2.4.0.201812141755     │ openHAB Paper UI Theme Fragmen

I’m though happy with this, it means we are passing control back to native java code. In what keystore did you store the certificate a standard one? Did you override something to provide the keystore?

I used this:
Loaded the crt to /home/openhabian

export JAVA_HOME=/usr/lib/jvm/zulu-embedded-8-armhf

keytool -importcert -file /home/openhabian/PeterBauer.crt -keystore $JAVA_HOME/jre/lib/security/cacerts -alias Judo

Used the Passwort: changeit

This looks all pretty default indeed

Okay what I tried now is:

Import the cert from my unifi controller in the cacerts keystore

Try to make a connection using the rule provide by you: > FAILS

Disabled the part which I feared to cause all of this: > still FAILS

My stacktrace is the following:

javax.net.ssl.SSLHandshakeException: General SSLEngine problem
	at org.eclipse.jetty.client.util.FutureResponseListener.getResult(FutureResponseListener.java:118)
	at org.eclipse.jetty.client.util.FutureResponseListener.get(FutureResponseListener.java:101)
	at org.eclipse.jetty.client.HttpRequest.send(HttpRequest.java:684)
	at org.eclipse.smarthome.io.net.http.HttpUtil.executeUrlAndGetReponse(HttpUtil.java:250)
	at org.eclipse.smarthome.io.net.http.HttpUtil.executeUrl(HttpUtil.java:156)
	at org.eclipse.smarthome.io.net.http.HttpUtil.executeUrl(HttpUtil.java:131)
	at org.eclipse.smarthome.io.net.http.HttpUtil.executeUrl(HttpUtil.java:109)
	at org.eclipse.smarthome.io.net.http.HttpUtil.executeUrl(HttpUtil.java:90)
	at org.eclipse.smarthome.model.script.actions.HTTP.sendHttpGetRequest(HTTP.java:57)
	at org.eclipse.smarthome.model.script.actions.HTTP.sendHttpGetRequest(HTTP.java:44)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
	at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1521)
	at sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:528)
	at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:802)
	at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:766)
	at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
	at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.fill(SslConnection.java:681)
	at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.process(HttpReceiverOverHTTP.java:128)
	at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.receive(HttpReceiverOverHTTP.java:73)
	at org.eclipse.jetty.client.http.HttpChannelOverHTTP.receive(HttpChannelOverHTTP.java:133)
	at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.onFillable(HttpConnectionOverHTTP.java:155)
	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281)
Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
	at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
	at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1709)
	at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:318)
	at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:310)
	at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1639)
	at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:223)
	at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037)
	at sun.security.ssl.Handshaker$1.run(Handshaker.java:970)
	at sun.security.ssl.Handshaker$1.run(Handshaker.java:967)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1459)
Caused by: java.security.cert.CertificateException: No subject alternative names present
	at sun.security.util.HostnameChecker.matchIP(HostnameChecker.java:145)
	at sun.security.util.HostnameChecker.match(HostnameChecker.java:94)
	at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:455)
	at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:436)
	at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:252)
	at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:136)
	at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1626)
	at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:223)
	at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037)
	at sun.security.ssl.Handshaker$1.run(Handshaker.java:970)
	at sun.security.ssl.Handshaker$1.run(Handshaker.java:967)

Edit: even if I configure the truststore and use the code from this fragment it reports an error:

Would it be possible to update things in such a manner that they follow the standards, maybe changes in the underlying Jetty made it such that you now get the warning, but reading more and more I think that it ever working is more likely to be wrong than it failing. Some search queries for more background: https://www.google.com/search?q=SSL+Cerficate+-+No+subject+alternative+names+present

Even with a certificate in your truststore the certificate should have a matching CN or subject alternative name.

The most interesting is that it works with the scripts from Atlassian

But fails using other code like ….

Unless you have an idea why it used to work I cannot help you any further.

Maybe a binding which you had in your 2.3 instance did override some global https configurations like the ones shown in https://stackoverflow.com/questions/19540289/how-to-fix-the-java-security-cert-certificateexception-no-subject-alternative

Edit: this for example fixes it:

HttpsURLConnection.setDefaultHostnameVerifier((hostname, sslSession) -> true);

I’m afraid I have to admit that I don’t fully understand it. I am a lawyer, not a computer scientist, and usually stick to step-by-step instructions ;D

I have understood that it is due to the certificate and that in my case the CN should not be called CN=Peter Bauer but CN=192.168.178.28.

What I didn’t understand is why the certificate is accepted when I retrieve it with the HTTP binding
(String Judotoken "Token of the judo system" { http="<[https://192.168.178.28:8124/?group=register&command=login&msgnumber=1&name=login&user=xx&password=xx&role=customer:600000:JSONPATH($.token)]" } }

but not if I’m use.

var tokenjson = sendHttpGetRequest("https://192.168.178.28:8124?group=register&command=login&msgnumber=2&name=login&user=xx&password=xx&role=customer")

Both a using the same certificate.

Can’t I somehow force sendHttpGetRequest to accept the certificate? Just like here

Or is it perhaps because the SSL connection is established here via port 8124?

The problem is that I can’t change the certificate that is stored on my decalcifying machine, nor the port that is set here.

I think that this is not part of the problem.

The main difference between the http binding and the rule action, is that first one uses the org.apache.commons.httpclient.HttpClient and the other uses the Jetty client org.eclipse.jetty.client.HttpClient, so it’s likely that its somewhere in there.

Currently I’m a little bit feverish so I will go to bed very early, but I’ll try to look into later. I case I did not reply before the new year, feel free to remind me :slight_smile:

To help with finding what may have caused this:

  • If the rule still works with 2.4.0.M3 but doesn’t with 2.4.0.M4, the issue is most likely due to the upgrade to Jetty 9.4.11.v20180605 (which was part of the upgrade to Karaf 4.2.1 (#396)). See also 2.4.0.M4 changes.

  • If the rule still works in 2.4.0.M5 but doesn’t in 2.4.0.M6 it may be due to the ExtensibleTrustManager changes (#6281). See also 2.4.0.M6 changes.

Does it work for you @martinvw with 2.3.0 when you import the unifi controller in the cacerts keystore?

Its not working with M3, also not M1 and M2. Its not working anymore since the change from 2.3 to 2.4.M1

That’s very odd indeed. But I wouldn’t test with M1 and M2 because of hiccups:

In the latest openHAB 2.5.0-SNAPSHOT Build (# 1482) Karaf got upgraded to 4.2.2 which uses Jetty 9.4.12.v20180830. Maybe one of the bugfixes also helps with this issue?

Happy new Year, i tried it with the openHAB 2.5.0-SNAPSHOT Build (# 1482) but getting still an error:

2019-01-01 11:34:19.391 [ERROR] [.smarthome.model.script.actions.HTTP] - Fatal transport error: java.util.concurrent.ExecutionException: javax.net.ssl.SSLHandshakeException: General SSLEngine problem

Hi,
hope you get well again. Did you have another opportunity to think about the problem?

@martinvw I’m getting the same error when im calling that:

val String rawString = sendHttpPutRequest( "https://www.lebensmittelwarnung.de/bvl-lmw-de/opensaga/feed/alle/baden_wuerttemberg.rss" )

1 Like

That is interesting, the url looks fine without any SSL errors, are you sure your JDK is recent?

Also it looks suspicious that you do a PUT? a sendHttpGetRequest looks more sensible to me.

1 Like

I think the most sensible approach would be to allow forcing to ignore certifcate errors, but that should/will never be the default because its unsafe. You could file an issue at https://github.com/openhab/openhab-core and if you manage to convince the people in charge in that repo I can try to make some time to implement it :slight_smile:

But as you might have noticed my availability is not that high currently, sorry for keeping you hanging

  1. You’re right. I did some try and error to find out if I can change the error and forgot to rename the call from put to get.
  2. It’s working now (from 14 o’clock today). Maybe they changed anything on their site.

For me this is solved.