CTRL-C should copy text
CTRL-C no longer works in 1.8.4. Workaround is to right-click and select Copy... but that sucks. This is the biggest issue I have with 1.8.4.
That XEP-0363 is enabled
XEP-0363 is disabled. Again, no changes have been made to the prosody server (other than the TLS cert getting updated) and other clients like conversations.im connect just fine with XEP-0363 enabled. Gajim has worked fine with this server for years with XEP-0363 enabled. It just stopped working for no reason. The only thing I can think of is that letsencrypt certs may play a role?
ok - so when I added the MUC service, on the same hostname as the file uploads, I effectively killed file uploads
my bad! added another hostname into the mix and it is now working
Please first check if another issue has been opened for your problem
That it connects
Get error message
I assume this relates to this more than likely since it worked fine before today: https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/ It expires Sep 30th 2021 (i.e. today).
nevermind - resolved issue - really weird how this only affects some clients and not others - even with identical OSes and versions of gajim
blacklisting the X3 cert on the server and running "update-ca-trust extract" was required (very weird since it seems like a client issue) - not sure why blacklisting that CA was required, but glad that is fixed
It does run on its own hostname that is on the same domain as my account. When I said it was a private server, I just meant that it is firewalled to only allow connections from specific networks (i.e. not available on the open Internet).
That XEP-0363 is enabled
XEP-0363 is disabled. Again, no changes have been made to the prosody server (other than the TLS cert getting updated) and other clients like conversations.im connect just fine with XEP-0363 enabled. Gajim has worked fine with this server for years with XEP-0363 enabled. It just stopped working for no reason. The only thing I can think of is that letsencrypt certs may play a role?
I can see the server responding with information on file upload capabilities (see below). Here is a complete debug log which will expire in 2 weeks or once it has been downloaded more than 20 times: https://deletebin.org/s#W3Mh21vFHNgVf2n3MPCbaj:8KmhXzYTw3HSoMMDkRINmUIj
The only odd thing I am doing here is not utilizing SRV records - in Gajim I enter the hostname manually in the account settings - the server is private - I just use it to chat with family members.
<iq from='brockman.REDACTED' to='mikemc@REDACTED/gajim.5L3IQC7U' type='result' id='e5b1b621-80ee-4150-b0f9-7e4b11c6ea4e'>
<query
xmlns='http://jabber.org/protocol/disco#info'>
<identity category='store' type='file' name='HTTP File Upload'/>
<identity category='conference' type='text' name='Prosody Chatrooms'/>
<feature var='urn:xmpp:http:upload:0'/>
<feature var='urn:xmpp:http:upload'/>
<feature var='http://jabber.org/protocol/disco#info'/>
<feature var='http://jabber.org/protocol/disco#items'/>
<feature var='http://jabber.org/protocol/muc'/>
<feature var='http://jabber.org/protocol/muc#unique'/>
<feature var='http://jabber.org/protocol/commands'/>
<feature var='urn:xmpp:mam:2'/>
<x type='result'
xmlns='jabber:x:data'>
<field var='FORM_TYPE' type='hidden'>
<value>urn:xmpp:http:upload:0</value>
</field>
<field var='max-file-size' type='text-single'>
<value>25000000</value>
</field>
</x>
<x type='result'
xmlns='jabber:x:data'>
<field var='FORM_TYPE' type='hidden'>
<value>urn:xmpp:http:upload</value>
</field>
<field var='max-file-size' type='text-single'>
<value>25000000</value>
</field>
</x>
</query>
</iq>
is there any way to tell gajim to connect to an "expired" cert?
Please first check if another issue has been opened for your problem
That it connects
Get error message
I assume this relates to this more than likely since it worked fine before today: https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/ It expires Sep 30th 2021 (i.e. today).
That XEP-0363 is enabled
XEP-0363 is disabled. Again, no changes have been made to the prosody server (other than the TLS cert getting updated) and other clients like conversations.im connect just fine with XEP-0363 enabled. Gajim has worked fine with this server for years with XEP-0363 enabled. It just stopped working for no reason. The only thing I can think of is that letsencrypt certs may play a role?