fiducia.de HBCI Endpoint stopped working
AqBanking Version: 5.7.6
HBCI URL setup command: aqhbci-tool4 adduser -s https://hbci11.fiducia.de/cgi-bin/hbciservlet -b 67230000 -u [MY_CUSTOMER_NUMBER] -N [MY_BANK_ACCOUNTNUMBER] -t pintan --hbciversion=300
Second setup command: aqhbci-tool4 adduserflags -f forceSsl3 -c [MY_CUSTOMER_NUMBER]
Now running getsysid with: aqhbci-tool4 -A -P pinfile getsysid -c [MY_CUSTOMER_NUMBER]
this fails since a few weeks with following error:
Locking users Locking user [MY_CUSTOMER_NUMBER] Executing HBCI jobs AqHBCI started There are no tan method descriptions (yet), trying One-Step TAN. Encoding queue Sending queue Connecting to server... Resolving hostname "hbci11.fiducia.de" ... IP address is "22.214.171.124" Connecting to "hbci11.fiducia.de" Connected to "hbci11.fiducia.de" Using GnuTLS default ciphers. TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD 5:2018/03/19 19-47-39:aqbanking(2366):abgui.c: 165: Automatically accepting certificate [D8:CD:2B:25:0B:6E:97:7A:B2:F3:0D:52:1D:25:BF:A9] Connected. Sending message... Message sent. Waiting for response Receiving response... 3:2018/03/19 19-47-39:gwen(2366):syncio_tls.c: 1336: gnutls_record_recv: -110 (The TLS connection was non-properly terminated.) 3:2018/03/19 19-47-39:gwen(2366):syncio_tls.c: 1354: Detected premature disconnect by server (violates specs!) No message received Error receiving response (-110) AqHBCI finished. 3:2018/03/19 19-47-39:aqhbci(2366):provider.c: 1464: Job has no system id and no iTAN results 3:2018/03/19 19-47-39:(null)(2366):getsysid.c: 157: Error getting system id (-1)
For other bank accounts running against other banks it is running fine, but only this bank account it doesn't work. Any idea? I also contacted my bank, even the IT guys over there checked my case, they said, it must be the software, they didn't find any problem on their side.
This suddenly stopped working, i also tried reinstalling everything with latest, no luck.
#1 Updated by martin over 3 years ago
- Status changed from New to In Progress
- Assignee set to martin
it is in fact a problem of the server. It prematurely hangs up a connection without performing the necessary TLS handshake for closing a connection. This is a violation of the specifications, and that's what AqBanking says in the logs.
However, newer versions of AqBanking have a way around this bug. Just execute this:
aqhbci-tool4 adduserflags -b BLZ -f tlsIgnPrematureClose
and after that AqBanking will ignore this violation.
Could you please report back whether that solves your problem?