Check Add-On update [Deleted]

  • Thread starter Thread starter Deleted member 232995
  • Start date Start date
I don't know what this addon is doing or trying to connect to though.
It is just calling an API service with a list of the add-ons and the version id. But this is a good hint. Maybe the IP or domain is blacklisted.
 
So after going through the addon code:

Code:
# curl -IL https://XXX -v
* About to connect() to xtest.dev port 443 (#0)
*   Trying 92.50.126.141...
* Connected to xtest.dev (92.50.126.141) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* NSS error -12190 (SSL_ERROR_PROTOCOL_VERSION_ALERT)
* Peer reports incompatible or unsupported protocol version.
* Closing connection 0
curl: (35) Peer reports incompatible or unsupported protocol version.

Code:
# curl -V
curl 7.29.0 (x86_64-redhat-linux-gnu) libcurl/7.29.0 NSS/3.53.1 zlib/1.2.7 libidn/1.28 libssh2/1.8.0
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz unix-sockets
 
Last edited:
Correct, I can't get any CentOS7 server to connect with CURL


Code:
# curl -IL https://XXX -v
* About to connect() to xtest.dev port 443 (#0)
*   Trying 92.50.126.141...
* Connected to xtest.dev (92.50.126.141) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* NSS error -12190 (SSL_ERROR_PROTOCOL_VERSION_ALERT)
* Peer reports incompatible or unsupported protocol version.
* Closing connection 0
curl: (35) Peer reports incompatible or unsupported protocol version.
 
@MattW @Alpha1
Please test it with the new version!
I made a mistake in the last update that caused the wrong host to be included.

I am terribly sorry! Also for your invested time ;(
 
@eva2000 what do you think about this one?
@MattW @Alpha1
Please test it with the new version!
I made a mistake in the last update that caused the wrong host to be included.

I am terribly sorry! Also for your invested time ;(
Ha! I considered to mention this possibility because I had a similar issue with a WordPress plugin last week. But decided not to because it's a different platform and would be very coincidental.

Thank you for addressing this so swiftly. I will test it out as soon as I get computer access.
 
This add-on is fantastic. I also thought all my add-ons were up-to-date, but it spotted quite a few updates.

I noticed one problem with 'ElasticSearch Essentials', it does not detect the update.
Currently installed version = 3.9.6
Latest version = 3.10.2 (link)
 
0815 updated Check Add-On update with a new update entry:

1.0.0 Beta 7


Read the rest of this update entry...


This add-on is fantastic. I also thought all my add-ons were up-to-date, but it spotted quite a few updates.

I noticed one problem with 'ElasticSearch Essentials', it does not detect the update.
Currently installed version = 3.9.6
Latest version = 3.10.2 (link)

screen_1663321020.webp
 
Great addon, but this was a bit disconcerting:

:) yes this may be confusing. XF has for itself and its add-ons own info in XF about new versions.... Hence this...
But I think I need to find ne exception for this as text.
 
The button texts will be more accurate and with explanations so it should be more understandable then. XF add-ons will be fully supported with the next version.



screen_1663332712_cr.png

-

screen_1663332773.png
-

screen_1663332786.png

-

1663332980090.webp


More ideas?
 
When ignoring update reminders - maybe have the ability to ignore update for 90 days or just ignore forever.
 
@eva2000 what do you think about this one?
The error? Wasn't it from coded wrong hostname? Or you mean curl error 35 for unsupported protocol in general? That might be related to CentOS 7's native curl built against OpenSSL 1.0.2 similar to an issue one Wordpress user had at https://community.centminmod.com/th...ot-support-tls1-2-or-tls1-3.23191/#post-94336. That user didn't reply to see if he tried my suggested workarounds but used the workaround the plugin author suggested in above linked thread but similar to https://stackoverflow.com/a/55654778/272648 which maybe this addon can use too?.

But I am building some custom Centmin Mod RPMs for better PHP/curl/openssl 1.1.1 support for CentOS 7. Still testing these RPMs for now.
Code:
curl -V
curl 7.85.0 (x86_64-pc-linux-gnu) libcurl/7.85.0 OpenSSL/1.1.1q zlib/1.2.7 brotli/1.0.9 zstd/1.5.2 libpsl/0.20.2 (+libidn2/2.3.2) libssh2/1.10.0 nghttp2/1.33.0
Release-Date: 2022-08-31
Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTPS-proxy IPv6 Kerberos Largefile libz NTLM NTLM_WB PSL SPNEGO SSL threadsafe TLS-SRP UnixSockets zstd

Output from https://gist.github.com/centminmod/3ede8093ffef827c16aeb7b35951a94f with Centmin Mod PHP 8.1.10 and custom RPM for curl/openssl 1.1.1

Code:
PHP version: 8.1.10
curl version: 7.85.0
SSL version: OpenSSL/1.1.1q
SSL version number: 0
OPENSSL_VERSION_NUMBER: 1010111f

Testing CURL_SSLVERSION_TLSv... (not forced)
Result TLS_Default: TLS 1.3
Result TLS_v1_1: TLS 1.3
Result TLS_v1_2: TLS 1.3
Result TLS_v1_3: Error! errno = 35, msg = error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure

Testing CURL_SSLVERSION_MAX_TLSv...
Result MAX_Default: TLS 1.3
Result TLS_v1_1: TLS 1.1
Result TLS_v1_2: TLS 1.2
Result TLS_v1_3: TLS 1.3
 
Top Bottom