Language:
switch to room list switch to menu My folders
Go to page: First ... 28 29 30 31 [32] 33 34 35 36 37
[#] Fri Feb 23 2018 11:54:44 EST from nbewhm4 @ Uncensored

Subject: easy install failed

[Reply] [ReplyQuoted] [Headers] [Print]

I tried this command (running as root):

curl http://easyinstall.citadel.org/install | sh

Eventually I got this error:
* Downloading libcitadel...
* Installing libcitadel...
  Complete.
* Downloading Citadel...
* Installing Citadel...
 
Citadel Easy Install is aborting.
 
A log file has been written to /tmp/citadel-install-log.txt
Reading this file may tell you what went wrong. If you
need to ask for help on the support forum, please post the
last screenful of text from this log.
 
 
At the end of the .txt log file I got:
......
checking libcitadel.h usability... yes
checking libcitadel.h presence... yes
checking for libcitadel.h... yes
checking for libcitadel_version_string in -lcitadel... yes
checking for OpenSSL... (system)
checking for db_create in -ldb... yes
checking ldap.h usability... no
checking ldap.h presence... no
checking for ldap.h... no
configure: error: OpenLDAP development headers were not found and are required.  More info: http://www.citadel.org/doku.php/installation:start
Operating system: Linux Debian 9.3 ( 4.9.59-v7+ armv7l)
 
I'm at a loss as to what to try next.... Any helpful suggestions please?
 


[#] Fri Feb 23 2018 12:01:00 EST from bobdoe @ Uncensored

Subject: Re: easy install failed

[Reply] [ReplyQuoted] [Headers] [Print]

 

Fri Feb 23 2018 11:54:44 AM EST from nbewhm4 @ Uncensored Subject: easy install failed

I tried this command (running as root):

curl http://easyinstall.citadel.org/install | sh

Eventually I got this error:
* Downloading libcitadel...
* Installing libcitadel...
  Complete.
* Downloading Citadel...
* Installing Citadel...
 
Citadel Easy Install is aborting.
 
A log file has been written to /tmp/citadel-install-log.txt
Reading this file may tell you what went wrong. If you
need to ask for help on the support forum, please post the
last screenful of text from this log.
 
 
At the end of the .txt log file I got:
......
checking libcitadel.h usability... yes
checking libcitadel.h presence... yes
checking for libcitadel.h... yes
checking for libcitadel_version_string in -lcitadel... yes
checking for OpenSSL... (system)
checking for db_create in -ldb... yes
checking ldap.h usability... no
checking ldap.h presence... no
checking for ldap.h... no
configure: error: OpenLDAP development headers were not found and are required.  More info: http://www.citadel.org/doku.php/installation:start
Operating system: Linux Debian 9.3 ( 4.9.59-v7+ armv7l)
 
I'm at a loss as to what to try next.... Any helpful suggestions please?
 


apt install libldap2-dev

run easy-install again

 

citadel documentation should be updated, but webmaster most likely doesn't give a damn



[#] Fri Feb 23 2018 12:10:17 EST from bobdoe @ Uncensored

Subject: Irc channel

[Reply] [ReplyQuoted] [Headers] [Print]

What happens to the irc channel at freenode?

Is it no longer used, or was never?



[#] Fri Feb 23 2018 12:12:18 EST from bobdoe @ Uncensored

Subject: Calendar issues

[Reply] [ReplyQuoted] [Headers] [Print]

Using citadel 917 installed through easy-install and using latest firefox browser.



--I tried adding a new event in calendar for a standard level 4 user, but the attendees button never works! The attendees tab also never displays citadel users to include; only current user's contacts.

Does citadel have any shared calendar functions?



--Also, when adding events I notice the event appears "delay" shifted in the day view. Meaning, if I set event from 14:00 to 16:00, the hours are saved correctly but in the day view graphic appears like 13:00 to 15:00.



[#] Fri Feb 23 2018 12:14:07 EST from bobdoe @ Uncensored

Subject: Chat problems

[Reply] [ReplyQuoted] [Headers] [Print]

Using citadel 917 installed from easy-install.

 


--WTH is the "chat" room for in webcit? Even with multiple users currently online if user enters this chat room only sees him/herself! Messages are aimed to nothing. I expected this to be a *real* chat room where users could join and chat.

 


--Configuring pidgin for chat client did not work. I followed the doc "Configuring a jabber client for citadel".

Protocol: xmpp

Username: user's username

Domain: my ip address xx.xx.xx.xx

Resource: left in blank (doesn't make any difference)

Password: user's password; checked "remember password"

In Advanced tab checked "allow plaintext auth..." and left default port 5222, just like configured in citadel server.

But in latest pidgin now it forces to choose one of 3 ssl options. "Ask for certificate" and "use certificate when possible" don't work, pidgin pops error "invalid certificate". Third option, "use old ssl", does not pop the error and lets account to be enabled, but it does nothing! Message options such as send new instant message are usable, but status always gets stuck in "connecting", no users appear at all, neither online nor offline, and sent messages aimed to a user never arrive.



[#] Fri Feb 23 2018 12:51:23 EST from nbewhm4 @ Uncensored

Subject: easy install failed

[Reply] [ReplyQuoted] [Headers] [Print]

I tried this command (running as root):

curl http://easyinstall.citadel.org/install | sh

Eventually I got this error:
* Downloading libcitadel...
* Installing libcitadel...
  Complete.
* Downloading Citadel...
* Installing Citadel...
 
Citadel Easy Install is aborting.
 
A log file has been written to /tmp/citadel-install-log.txt
Reading this file may tell you what went wrong. If you
need to ask for help on the support forum, please post the
last screenful of text from this log.
 
 
At the end of the .txt log file I got:
......
checking libcitadel.h usability... yes
checking libcitadel.h presence... yes
checking for libcitadel.h... yes
checking for libcitadel_version_string in -lcitadel... yes
checking for OpenSSL... (system)
checking for db_create in -ldb... yes
checking ldap.h usability... no
checking ldap.h presence... no
checking for ldap.h... no
configure: error: OpenLDAP development headers were not found and are required.  More info: http://www.citadel.org/doku.php/installation:start
Operating system: Linux Debian 9.3 ( 4.9.59-v7+ armv7l)
 
I'm at a loss as to what to try next.... Any helpful suggestions please?
 


[#] Fri Feb 23 2018 13:50:10 EST from IGnatius T Foobar @ Uncensored

Subject: Re: easy install failed

[Reply] [ReplyQuoted] [Headers] [Print]

 

configure: error: OpenLDAP development headers were not found and are required.  More info: http://www.citadel.org/doku.php/installation:start
Operating system: Linux Debian 9.3 ( 4.9.59-v7+ armv7l)
 
I'm at a loss as to what to try next.... Any helpful suggestions please?

apt-get install libldap2-dev

 



[#] Fri Feb 23 2018 14:33:24 EST from bobdoe @ Uncensored

Subject: Irc channel

[Reply] [ReplyQuoted] [Headers] [Print]

What happens to the irc channel at freenode?
Is it no longer used, or was never?



[#] Fri Feb 23 2018 14:35:15 EST from bobdoe @ Uncensored

Subject: Calendar issues

[Reply] [ReplyQuoted] [Headers] [Print]

Using citadel 917 installed through easy-install and using latest firefox browser.

--I tried adding a new event in calendar for a standard level 4 user, but the attendees button never works! The attendees tab also never displays citadel users to include, only current user's contacts, and global address book in case I use aide user.

And even if adding attendees, they're never ever saved!
Does citadel have any shared calendar functions?


--Also, when adding events I notice the event appears "delay" shifted in the day view. Meaning, if I set event from 14:00 to 16:00, the hours are saved correctly but in the day view graphic appears like 13:00 to 15:00.



[#] Fri Feb 23 2018 14:40:46 EST from bobdoe @ Uncensored

Subject: Chat problems

[Reply] [ReplyQuoted] [Headers] [Print]

Using citadel 917 installed from easy-install.

--WTH is the "chat" room for in webcit? Even with multiple users currently online if user enters this chat room only sees him/herself! Messages are aimed to nothing. I expected this to be a *real* chat room where users could join and chat.


--Configuring pidgin for chat client simply does not work. I followed the doc "Configuring a jabber client for citadel".

Protocol: xmpp
Username: user's username
Domain: server's ip address xx.xx.xx.xx
Resource: left in blank (doesn't make any difference)
Password: user's password; checked "remember password"
In Advanced tab checked "allow plaintext auth..." and left default port 5222, just like configured in citadel server.

But latest pidgin now it forces to choose one of 3 ssl options. "Ask for certificate" and "use certificate when possible" don't work, pidgin pops error "invalid certificate". Third option, "use old ssl", does not pop the error and lets account to be enabled, but it does nothing! Status always gets stuck in "connecting", no users appear at all, neither online nor offline, and sent messages aimed to a user never arrive.

Latest jitsi chat client doesn't work neither, though this one at least pops the error "unable to connect".

I already tried changing citadel's xmpp port from 5222 to 5223. Disabled firewalld in citadel server, which uses Centos 7. Not working neither. Tried pidgin and jitsi on windows, btw.

ANY HELP please?



[#] Fri Feb 23 2018 14:54:21 EST from Haven @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

The chat last time I played with it, allowed mutiple users to go into it in the same room, and have near real time communications, like IRC with each other.   However it does require more than one user to be there, like IRC.  If there is only one user there then it is just like you describe, just like IRC.  



[#] Fri Feb 23 2018 15:43:16 EST from IGnatius T Foobar @ Uncensored

Subject: Re: Chat problems

[Reply] [ReplyQuoted] [Headers] [Print]


bobdoe: please RTFM http://catb.org/~esr/faqs/smart-questions.html before looking for any further assistance, and above all, STOP private messaging anyone who happens to wander in. UNCENSORED! is a general purpose community, and supporting the Citadel software is only a small portion of what we do here.

[#] Fri Feb 23 2018 16:01:05 EST from bobdoe @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Ignatus:

I **already read all the freaking manuals at citadel.org**, and docs have WAY MUCH holes that have never been patched.

Examples: wiki pages creation, easy-install now requiring openldap dev packages, there's little to no documentation regarding whole calendar-ing, and as far as I just tested, chat docs are outdated -chat clients now force ask TLS-



[#] Fri Feb 23 2018 19:16:15 EST from AdeV @ Uncensored

Subject: TDAP killing my Citadel server

[Reply] [ReplyQuoted] [Headers] [Print]

Hi all,

A while back I posted about the TDAP process (at least, I think it's TDAP) on my Citadel server going mental & eating all the disk space on the server over the course of an hour (or less). When everything crashed due to lack of disk space, I could recover the DB back to working order with the berkerly DB recovery tools. The issue appears to be TDAP trying to purge a particularly large number of e-mails which ended up in one account (ahem, an account I didn't even know existed! but that's by the by). I "fixed" it by turning off message expiry on the affected account, and just ignoring the 1.2m e-mails in it (if I ever tried to delete any of them, TDAP crashed the server as described).

Anyway, fast-forward to around Christmas 2017, and as a result of the spectre/meltdown fiasco, I send a bulk e-mail out from one of the forums hosted on the server (which used Citadel as its mail provider), and suddenly TDAP is killing the server again. And this time, I can't stop it. Every time I start Citadel up, it runs for about 15 minutes, then dies having eaten all the disk space (requiring the DB recovery as described above). Restart Citadel. Rinse and repeat until thoroughly disheartened.

As a result of this I've sadly had to move away from the easy-to-administer Citadel, to a more "normal" setup (postfix/dovecot), and now that's all settled down... I really need to get the last 5 years e-mails out of Citadel & onto the replacement server. I'd use an IMAP transfer tool/service - but I can't keep Citadel running long enough to transfer a significant number of emails; and every time it trashes the disk, it takes several websites down with it. My plan is to kick up a new machine (once I've got some hard disks & stuff sorted out), install Citadel again, copy in the broken database, and try again from there (so at least it won't murder the websites on the VM server I use); but last time I tried this using the biggest Linode server money can buy (2TB disk space), Citadel used the whole damn disk up within 24hrs!

 

So - my question is: Is there any way to disable the TDAP process in Citadel? So I can run the server long enough to extract all my e-mails?

 

Cheers!
Ade.



[#] Sat Feb 24 2018 11:43:32 EST from bobdoe @ Uncensored

Subject: Unable to connect pidgin to citadel server

[Reply] [ReplyQuoted] [Headers] [Print]

I'd like to attempt reformulating the question in a more neutral way, if I got chance. Already read the proper questions faq.

I'm trying to connect Pidgin chat client to Citadel server.

Setup:
Citadel 917 installed through easy-install on Centos 7.4. Firewalld disabled.
Pidgin 2.12 running on Windows 10.

So I followed the corresponding documentation: http://www.citadel.org/doku.php/faq:everydayuse:jabber#configuring.a.jabber.client.to.access.citadel
But after that I get the following error: "The certificate for <server> could not be validated. The certificate chain presented is invalid".

Now, I noticed in latest pidgin build that there's seemingly no way to turn off SSL/TLS encryption anymore; at most there's the option "use old style SSL".

What I have tried and what I got:
--Use old style SSL:
   no certificate error, but Pidgin gets stuck in "Connecting..." forever.
--Export Citadel server's certificate with Firefox, name it after server's hostname (ip address), and manually adding it to Pidgin:
   still get the same previous "certificate chain is invalid" error
--Run "openssl s_client -connect <server>:<port> -starttls xmpp" in Centos server, and copying generated cert to Pidgin on Windows:
   still get the same previous "certificate chain is invalid" error
--Change Citadel XMPP port to 5223 as well as in Pidgin, and use old style SSL:
   Pidgin complains about not finding the server.

Finally I tried other XMPP clients such as Jitsi, Gajim and Spark. Long story short (unless I'm required to provide further details), they also expect to connect through SSL/TLS with no option to disable it.

Could anyone assist, please?
Or should I try finding a XMPP client with option to not use SSL/TLS at all?

Thanks.



[#] Sun Feb 25 2018 15:58:04 EST from bgerum @ Uncensored

Subject: Re: citadel refuses to start after OpenSuSE upgrade - now with Easyins

[Reply] [ReplyQuoted] [Headers] [Print]

 

Mon Feb 19 2018 16:48:14 EST from bgerum @ Uncensored Subject: Re: citadel refuses to start after OpenSuSE upgrade - cursor still in prog

 

Sun Feb 04 2018 16:22:10 EST from bgerum @ Uncensored Subject: Re: citadel refuses to start after OpenSuSE upgrade - cursor still in prog

 

Mon Jan 29 2018 18:34:53 EST from bgerum @ Uncensored Subject: Re: citadel refuses to start after OpenSuSE upgrade - cursor still in prog

 

Mon Jan 29 2018 13:35:33 EST from IGnatius T Foobar @ Uncensored Subject: Re: citadel refuses to start after OpenSuSE upgrade - cursor still in prog
thanks for the reply. Unfortunately it seems the last version supplied by
the
homueller SuSE repo which is linked in the citadel.org doku ist 824.


Is there another rpm source?

I'm not aware of another RPM source. You could switch to Easy Install, which works on all distributions, but you'll have to move your data files to another directory first.

I used the Easy Install a long time ago, but the RPM version ist much more integrated in the OpenSuSE environment, not only directory-wise but also regarding startscripts, updating etc.

Do you think you could give Mr. homueller a hint there are new citadel versions out there? 



Ok, I found another OpenSuSE rpm source:

https://download.opensuse.org/repositories/home:/stefjakobs:/citadel-testing

it does provide citadel-9.01-13.19.x86_64, I installed it although it is compiled for the tumbleweed version of OpenSuSE, not leap which is what i use.

however, my database upgrade problem still remains:

citserver[14575]: Checking directory access
citserver[14575]: Opening databases
citserver[14575]: bdb(): open_databases() starting
citserver[14575]: Compiled db: Berkeley DB 4.8.30: (March 31, 2016)
citserver[14575]:   Linked db: Berkeley DB 4.8.30: (October 21, 2013)
citserver[14575]: Calculated dbversion: 4008030
citserver[14575]:   Previous dbversion: 4008030
citserver[14575]: Linked zlib: 1.2.8
citserver[14575]: bdb(): Setting up DB environment
citserver[14575]: dbenv->open(dbenv, /var/lib/citadel/data/, 10899, 0)
citserver[14575]: DB: Finding last valid log LSN: file: 6494 offset 9355549
citserver[14575]: DB: Recovery starting from [6494][9355421]
citserver[14575]: DB: Recovery complete at Sun Feb  4 22:10:24 2018
citserver[14575]: DB: Maximum transaction ID 80000024 Recovery checkpoint [6494][9355549]
citserver[14575]: Starting up DB
citserver[14575]: Checking floor reference counts
citserver[14575]: bdb(): cursor still in progress on cdb 04: can't begin transaction during r/o cursor
citserver[14575]: citserver is stopping in order to prevent data loss. uid=0 gid=0 euid=0 egid=0


 


Hi Ignatius,
 
any help on this? In the meantime I fired up the old server, did a sendcommand "CULL" and retransfered all the data files ... still the same problem!
 
 
As, unfortunately citadel 9.01-13 seems to be regarded as positively ancient, too, I gave EasyInstall a try, still having in mind I will have to reconfigure all the startup scripting, let's encrypt SSL Cert updating, fetchmail with TLS/SSL etc..
But EasyInstall chokes up on libsieve:
 
2nd run:
 
Installation will now begin.
Command output will not be sent to the terminal.
To view progress, see the /tmp/citadel-install-log.txt file.

* libical does not need updating.
* libsieve does not need updating.
* Berkeley DB does not need updating.
* expat does not need updating.
* libcurl does not need updating.
* libcitadel does not need updating.
* Downloading Citadel...
* Installing Citadel...

Citadel Easy Install is aborting.

A log file has been written to /tmp/citadel-install-log.txt
Reading this file may tell you what went wrong. If you
need to ask for help on the support forum, please post the
last screenful of text from this log.

Operating system: Linux 4.4.104-39-default( 4.4.104-39-default x86_64)
 
last lines of the install log:
 
checking for libical/ical.h... yes
checking for icaltimezone_set_tzid_prefix in -lical... yes
checking sieve2.h usability... yes
checking sieve2.h presence... yes
checking for sieve2.h... yes
checking for sieve2_license in -lsieve... no
configure: error: libsieve was not found and is required.  More info: http://www.citadel.org/doku.php/installation:start
Operating system: Linux 4.4.104-39-default( 4.4.104-39-default x86_64)

 



 



[#] Sun Feb 25 2018 20:05:54 EST from paxfettel @ Uncensored

Subject: raspberry pi install

[Reply] [ReplyQuoted] [Headers] [Print]

having trouble getting past login after following instructions here https://pimylifeup.com/raspberry-pi-email-server/ i have to click login multiple times then gets stuck with please wait  many thanks for any help i can get



[#] Sun Feb 25 2018 21:46:41 EST from IGnatius T Foobar @ Uncensored

Subject: Re: citadel refuses to start after OpenSuSE upgrade - now with Easyins

[Reply] [ReplyQuoted] [Headers] [Print]

 

checking for libical/ical.h... yes
checking for icaltimezone_set_tzid_prefix in -lical... yes
checking sieve2.h usability... yes
checking sieve2.h presence... yes
checking for sieve2.h... yes
checking for sieve2_license in -lsieve... no
configure: error: libsieve was not found and is required.  More info: http://www.citadel.org/doku.php/installation:start
Operating system: Linux 4.4.104-39-default( 4.4.104-39-default x86_64)

According to that log, it couldn't link to libsieve, even though libsieve had clearly been installed.  That is quite weird.

Can you attach the full log please?  We need to see what happened during the libsieve build.



[#] Mon Feb 26 2018 09:11:30 EST from Haven @ Uncensored

Subject: Re: Unable to connect pidgin to citadel server

[Reply] [ReplyQuoted] [Headers] [Print]

 

Sat Feb 24 2018 11:43:32 EST from bobdoe @ Uncensored Subject: Unable to connect pidgin to citadel server

I'd like to attempt reformulating the question in a more neutral way, if I got chance. Already read the proper questions faq.

I'm trying to connect Pidgin chat client to Citadel server.

Setup:
Citadel 917 installed through easy-install on Centos 7.4. Firewalld disabled.
Pidgin 2.12 running on Windows 10.

So I followed the corresponding documentation: http://www.citadel.org/doku.php/faq:everydayuse:jabber#configuring.a.jabber.client.to.access.citadel
But after that I get the following error: "The certificate for <server> could not be validated. The certificate chain presented is invalid".

Now, I noticed in latest pidgin build that there's seemingly no way to turn off SSL/TLS encryption anymore; at most there's the option "use old style SSL".

What I have tried and what I got:
--Use old style SSL:
   no certificate error, but Pidgin gets stuck in "Connecting..." forever.
--Export Citadel server's certificate with Firefox, name it after server's hostname (ip address), and manually adding it to Pidgin:
   still get the same previous "certificate chain is invalid" error
--Run "openssl s_client -connect <server>:<port> -starttls xmpp" in Centos server, and copying generated cert to Pidgin on Windows:
   still get the same previous "certificate chain is invalid" error
--Change Citadel XMPP port to 5223 as well as in Pidgin, and use old style SSL:
   Pidgin complains about not finding the server.

Finally I tried other XMPP clients such as Jitsi, Gajim and Spark. Long story short (unless I'm required to provide further details), they also expect to connect through SSL/TLS with no option to disable it.

Could anyone assist, please?
Or should I try finding a XMPP client with option to not use SSL/TLS at all?

Thanks.



 

Again, not a Citadel expert, but when I see the error "The certificate for <server> could not be validated. The certificate chain presented is invalid". this indicates an issue with the certificate chain. 

If this is a self signed certificate, then Pidgin doesn't support those anymore.   If this isn't a self signed certificate, please check the intermediate certificates are in place.    Usually when you buy a certificate you get a bundle, which includes your certificate, plus their certificate chain, just in case, so the cert can be verified by the issuing body.  

 

Link to an article about how SSL works: https://www.entrustdatacard.com/pages/ssl 

 



[#] Mon Feb 26 2018 10:45:59 EST from bobdoe @ Uncensored

Subject: Re: Unable to connect pidgin to citadel server

[Reply] [ReplyQuoted] [Headers] [Print]

 

Mon Feb 26 2018 09:11:30 AM EST from Haven @ Uncensored Subject: Re: Unable to connect pidgin to citadel server

 

Sat Feb 24 2018 11:43:32 EST from bobdoe @ Uncensored Subject: Unable to connect pidgin to citadel server

I'd like to attempt reformulating the question in a more neutral way, if I got chance. Already read the proper questions faq.

I'm trying to connect Pidgin chat client to Citadel server.

Setup:
Citadel 917 installed through easy-install on Centos 7.4. Firewalld disabled.
Pidgin 2.12 running on Windows 10.

So I followed the corresponding documentation: http://www.citadel.org/doku.php/faq:everydayuse:jabber#configuring.a.jabber.client.to.access.citadel
But after that I get the following error: "The certificate for <server> could not be validated. The certificate chain presented is invalid".

Now, I noticed in latest pidgin build that there's seemingly no way to turn off SSL/TLS encryption anymore; at most there's the option "use old style SSL".

What I have tried and what I got:
--Use old style SSL:
   no certificate error, but Pidgin gets stuck in "Connecting..." forever.
--Export Citadel server's certificate with Firefox, name it after server's hostname (ip address), and manually adding it to Pidgin:
   still get the same previous "certificate chain is invalid" error
--Run "openssl s_client -connect <server>:<port> -starttls xmpp" in Centos server, and copying generated cert to Pidgin on Windows:
   still get the same previous "certificate chain is invalid" error
--Change Citadel XMPP port to 5223 as well as in Pidgin, and use old style SSL:
   Pidgin complains about not finding the server.

Finally I tried other XMPP clients such as Jitsi, Gajim and Spark. Long story short (unless I'm required to provide further details), they also expect to connect through SSL/TLS with no option to disable it.

Could anyone assist, please?
Or should I try finding a XMPP client with option to not use SSL/TLS at all?

Thanks.



 

Again, not a Citadel expert, but when I see the error "The certificate for <server> could not be validated. The certificate chain presented is invalid". this indicates an issue with the certificate chain. 

If this is a self signed certificate, then Pidgin doesn't support those anymore.   If this isn't a self signed certificate, please check the intermediate certificates are in place.    Usually when you buy a certificate you get a bundle, which includes your certificate, plus their certificate chain, just in case, so the cert can be verified by the issuing body.  

 

Link to an article about how SSL works: https://www.entrustdatacard.com/pages/ssl 

 



Thanks.

Meanwhile I have already read several articles about general SSL and TLS. I also searched again in all citadel.org documents.
And yes, I already realized Citadel installs self-signed certificates by default (evident when accessing webcit through https).

I also tried with other XMPP clients such as Jitsi and Miranda. Their options regarding SSL are certainly different of Pidgin's, in the sense one can seemingly enable/disable SSL option. Yet, by following similar steps to those described in citadel's pidgin documentation, I still cannot connect to server. Jitsi complains about not finding the server, and Miranda gets stuck at attempting to conenct and not showing any contacts or groups.

Ignatius:
I'd be willing to offer apologies. But also, if you had chance, could you give some advise please? Is it that Citadel still needs further TLS compatibility?

I'm still trying stuff by myself, and searching for more TLS documents, but I'm fearing I'd reach my limit soon, and this feature would be very useful for the place here.

Thanks.



Go to page: First ... 28 29 30 31 [32] 33 34 35 36 37