Language:
switch to room list switch to menu My folders
Go to page: First ... 26 27 28 29 [30] 31 32 33 34 ... Last
[#] Sun Jan 17 2021 12:25:04 EST from w1kgk

Subject: Re: login

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

Yes  i changed the citadel to 8080.  apache2 comes up with 192.168.1.50 and also 127.0.01!!

How do i get past the apache2 to citadel....sorry really new to this!!!

 

Kevin



[#] Sun Jan 17 2021 12:48:03 EST from ParanoidDelusions

Subject: Re: login

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

I probably thought of this so quickly because I'm not super good at this, myself. 

Type in http://127.0.0.1:8080

or http://192.168.1.50:8080

Both should open at your Citadel screen. 

 

Sun Jan 17 2021 12:25:04 EST from w1kgk Subject: Re: login

Yes  i changed the citadel to 8080.  apache2 comes up with 192.168.1.50 and also 127.0.01!!

How do i get past the apache2 to citadel....sorry really new to this!!!

 

Kevin



 



[#] Sun Jan 17 2021 13:13:41 EST from ParanoidDelusions

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

Is there a way to send a systemwide page to all logged in users without restarting? 

Also: 

When trying to restart with page all users, I get: 

Message to your Users:

 

didn't find Template [box_serverrestartpage] 21 21


[#] Sun Jan 17 2021 15:52:48 EST from ParanoidDelusions

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

So... 

In order to change my default port for https from 4916 to 443... 

Do I... 

run /etc/webcit ./setup and change it there to 443 

then change the redirects from lobby at /etc/systemd/system/webcit-https.service from p4916 to p443 

I've done this on my test system, and after restarting citadel, rebooting the entire machine, it no longer redirects on connect from lobby the the welcome room. 

I am connecting to https://127.0.0.1 

Is there something I'm missing? 

Warbaby was right - it does fix the broken SSL messages in my logs - and seems to speed up the response time of the Citadel - at least, when connecting to localhost. 

 



[#] Sun Jan 17 2021 16:11:06 EST from ParanoidDelusions

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

Something is definitely wrong.

Jan 17 14:10:49 secure webcit[3500]: Attempting to bind to port 443...
Jan 17 14:10:49 secure webcit[3500]: Can't bind: Address already in use

 

Sun Jan 17 2021 15:52:48 EST from ParanoidDelusions

So... 

In order to change my default port for https from 4916 to 443... 

Do I... 

run /etc/webcit ./setup and change it there to 443 

then change the redirects from lobby at /etc/systemd/system/webcit-https.service from p4916 to p443 

I've done this on my test system, and after restarting citadel, rebooting the entire machine, it no longer redirects on connect from lobby the the welcome room. 

I am connecting to https://127.0.0.1 

Is there something I'm missing? 

Warbaby was right - it does fix the broken SSL messages in my logs - and seems to speed up the response time of the Citadel - at least, when connecting to localhost. 

 



 



[#] Sun Jan 17 2021 19:09:22 EST from ParanoidDelusions

Subject: Change SSL Port in Webcit (Was:PD Forgot a subject again)

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

I'll post my ramblings on it somewhere else - but I got it sorted. 

Sun Jan 17 2021 16:11:06 EST from ParanoidDelusions

Something is definitely wrong.

Jan 17 14:10:49 secure webcit[3500]: Attempting to bind to port 443...
Jan 17 14:10:49 secure webcit[3500]: Can't bind: Address already in use

 

 

 



 



 



[#] Sun Jan 17 2021 20:38:07 EST from warbaby

Subject: Webcit & ports..

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

WEBCIT/EASYINSTALL

root@mail:/etc# ag -i webcit
systemd/system/webcit-https.service
5:ExecStart=/usr/local/webcit/webcit -s -p2001 uds /usr/local/citadel

systemd/system/webcit-http.service
5:ExecStart=/usr/local/webcit/webcit -p8080 uds /usr/local/citadel
root@ellen:/etc#

OR, there are some older init scripts in /etc/init.d/webcit # if you have a package version..

You'll have to hack the files right there.. if it's in systemd, just cp or mv to some safe place, before you mess with them.. 

cp /etc/systemd/system/webcit-http ~/webcit-backup # etc.. or

cp webcit-http webcit-http.dist # something like that..

If you're using NGINX for Proxy pass, webcit is still running on a port somewhere, but NOT 80/443! .. just think your way through it..

use 'netstat -lnp' see what is running on which port..

ParanoidDelusions, remember if you want to do the Start Page, you have to add the URL to the startup line.. [I forget the exact syntax, but you should have it.. You had it setup in the past.]



[#] Sun Jan 17 2021 22:09:14 EST from ParanoidDelusions

Subject: Re: Webcit & ports..

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

Thank you for the response. 

Not really familiar with ack/ag - but it looks like the lines you provided below uses ag to search for "webcit" finds the systemd/system webcit-https.service and then shows you what line the port numbers for webcit are defined on in that config file, right? 

ack/ag are not installed as default tools on either Debian or Raspbian. 

The syntax I have in webcit-https.service is
 
ExecStart=/usr/local/webcit/webcit -s -p443 -g/dotgoto?room=hello uds /usr/local/citadel

Is changing the "-pXXX" in webcit.http(s).service *setting* the port for webcit, or just defining what port webcit is listening on? That may have been my confusion. I may have set up webcit by running ./setup in the webcit directory and then went in and manually edited the file in systemd/system. 

Debian and Raspbian use some new scheme to configure network interfaces, ip address, DNS addresses and related settings. It isn't "if up" and "if down" anymore. I'm not real comfortable with the new scheme - but, netstat is depreciated under the new method - not installed by default, and I ran into some obstacle with installing it along the new tools last time I tried.

I did manage to evidently get it sorted so that it isn't throwing up bind errors and the landing page is working once again. I did it the Windows admin way - shutting down hard then powering back up. Not sure what that would have fixed that a reboot didn't - but it started working right after that.   

Sun Jan 17 2021 20:38:07 EST from warbaby Subject: Webcit & ports..

WEBCIT/EASYINSTALL

root@mail:/etc# ag -i webcit
systemd/system/webcit-https.service
5:ExecStart=/usr/local/webcit/webcit -s -p2001 uds /usr/local/citadel

systemd/system/webcit-http.service
5:ExecStart=/usr/local/webcit/webcit -p8080 uds /usr/local/citadel
root@ellen:/etc#

OR, there are some older init scripts in /etc/init.d/webcit # if you have a package version..

You'll have to hack the files right there.. if it's in systemd, just cp or mv to some safe place, before you mess with them.. 

cp /etc/systemd/system/webcit-http ~/webcit-backup # etc.. or

cp webcit-http webcit-http.dist # something like that..

If you're using NGINX for Proxy pass, webcit is still running on a port somewhere, but NOT 80/443! .. just think your way through it..

use 'netstat -lnp' see what is running on which port..

ParanoidDelusions, remember if you want to do the Start Page, you have to add the URL to the startup line.. [I forget the exact syntax, but you should have it.. You had it setup in the past.]



 



[#] Sun Jan 17 2021 22:46:44 EST from warbaby

Subject: Re: Webcit & ports..

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

For the sake of argument, 'ag' is synonymous with 'grep' .. [But many times faster, and 2 letters shorter, so I highly recommend apt-get install silversearcher-ag]

[Also, I know the stupid thing Debian did about changing the default interfaces from eth0 etc.. to the literal, unpredictable device name, stupid, but probably not the cause of any actual problem with cit/webcit.. also, the nonsense with /run that broke all kinds of programs... ]

> Is changing the "-pXXX" in webcit.http(s).service *setting* the port for webcit, or just defining what port webcit is listening on?

Yes, it runs on the port that you specify when you launch it, it's not in the database or a config file or anything like that.

These are the files that systemd uses to stop, start and restart a service.

webcit-http.service

webcit-https.service

If you want to hack the ports manually by editing the files.. first stop the service..

service webcit-https stop

[make a backup copy, edit webcit-https.service, change ports alter command line, log level, start page, etc.. ]

service webcit-https start

you should be good to go without rebooting...

netstat is an important tool, regardless of their "feelings" about it, just install it from the packages..

Also, thank you for your work and contributions here in the support room.

 

Sun Jan 17 2021 10:09:14 PM EST from ParanoidDelusions Subject: Re: Webcit & ports..

Thank you for the response. 

Not really familiar with ack/ag - but it looks like the lines you provided below uses ag to search for "webcit" finds the systemd/system webcit-https.service and then shows you what line the port numbers for webcit are defined on in that config file, right? 

ack/ag are not installed as default tools on either Debian or Raspbian. 

The syntax I have in webcit-https.service is
 
ExecStart=/usr/local/webcit/webcit -s -p443 -g/dotgoto?room=hello uds /usr/local/citadel

Is changing the "-pXXX" in webcit.http(s).service *setting* the port for webcit, or just defining what port webcit is listening on? That may have been my confusion. I may have set up webcit by running ./setup in the webcit directory and then went in and manually edited the file in systemd/system. 

Debian and Raspbian use some new scheme to configure network interfaces, ip address, DNS addresses and related settings. It isn't "if up" and "if down" anymore. I'm not real comfortable with the new scheme - but, netstat is depreciated under the new method - not installed by default, and I ran into some obstacle with installing it along the new tools last time I tried.

I did manage to evidently get it sorted so that it isn't throwing up bind errors and the landing page is working once again. I did it the Windows admin way - shutting down hard then powering back up. Not sure what that would have fixed that a reboot didn't - but it started working right after that.   

Sun Jan 17 2021 20:38:07 EST from warbaby Subject: Webcit & ports..

WEBCIT/EASYINSTALL

root@mail:/etc# ag -i webcit
systemd/system/webcit-https.service
5:ExecStart=/usr/local/webcit/webcit -s -p2001 uds /usr/local/citadel

systemd/system/webcit-http.service
5:ExecStart=/usr/local/webcit/webcit -p8080 uds /usr/local/citadel
root@ellen:/etc#

OR, there are some older init scripts in /etc/init.d/webcit # if you have a package version..

You'll have to hack the files right there.. if it's in systemd, just cp or mv to some safe place, before you mess with them.. 

cp /etc/systemd/system/webcit-http ~/webcit-backup # etc.. or

cp webcit-http webcit-http.dist # something like that..

If you're using NGINX for Proxy pass, webcit is still running on a port somewhere, but NOT 80/443! .. just think your way through it..

use 'netstat -lnp' see what is running on which port..

ParanoidDelusions, remember if you want to do the Start Page, you have to add the URL to the startup line.. [I forget the exact syntax, but you should have it.. You had it setup in the past.]



 



 



[#] Sun Jan 17 2021 23:36:32 EST from ParanoidDelusions

Subject: Re: Webcit & ports..

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

Thank you, again. This really helps clarify what is going on with this for me. It makes a lot more sense. 

And thanks for your patience with me as I figure out how to behave here. I know I'm sometimes more disruption than I'm worth, but I very rarely realize it when I'm in the middle of spinning around wildly in the middle of the china shop... :) 

I was just reading up on AG and was about to install it - but decided I'll give it a go on my test machine first, tomorrow. I'll do the same for netstat. 

Sun Jan 17 2021 22:46:44 EST from warbaby Subject: Re: Webcit & ports..

For the sake of argument, 'ag' is synonymous with 'grep' .. [But many times faster, and 2 letters shorter, so I highly recommend apt-get install silversearcher-ag]

 

netstat is an important tool, regardless of their "feelings" about it, just install it from the packages..

Also, thank you for your work and contributions here in the support room.

 

 


[#] Tue Jan 19 2021 16:40:30 EST from markus

Subject: How to address citadel server by caldav and carddav clients

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

Hi all,

could somebody tell me how cardav and caldav clients should correctly address a citadel server?

Thanks in advance.



[#] Tue Jan 19 2021 17:01:05 EST from markus

Subject: How to configure citadel leaving the copy of a sent email untouched?

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

Hello all,

 

when ciitadel delivers an email it places a copy of the email in the sent-items-folder. Not an exact copy, because it adds the from-address as second to-address to the copy. How can I configure citadel leaving the header untouched?

I asked the question a couple of days back but I got no answer. So I hope this time somebody has already solved the problem and can kindly tell me how :-)  In case the solution is described in any citadel document I would be glad to know where.

Thanks in advance!

 

Markus



[#] Tue Jan 19 2021 17:47:56 EST from markus

Subject: How to address smart hosts in citadel?

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

Hello all again,

could anybody tell me how smart host should be addressed in citadel (please be as precise as possible)?

Thanks in advance

Markus

 



[#] Wed Jan 20 2021 13:23:34 EST from markus

Subject: Is there a routine anchoring citadel to start on system boot?

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

Dear citadel user,

Is there any setup routine that could anchor citadel as a service that starts on system boot? I'm asking because webcit starts as a service on system boot and webcit on it's own makes no sense. So I would expect that such a routine exist.

Thanks in advance and have nice day,

Markus

 



[#] Wed Jan 20 2021 13:50:37 EST from s3cr3to to Citadel_Support <room_Citadel_Support@uncensored.citadel.org>

Subject: Re: Is there a routine anchoring citadel to start on system boot?

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

I use this two scripts for /etc/init.d in debian (old)

You can use these scripts (maybe not), or someone with more knowledge
knows how to adapt it to your system.

As always, don't trust everything someone sends you, check the code of
these scripts.

Regards

(Kudos to the original author Wilfried Goesgens)


On 1/20/21 11:23 AM, markus wrote:
Dear citadel user,

Is there any setup routine that could anchor citadel as a service that
starts on system boot? I'm asking because webcit starts as a service on
system boot and webcit on it's own makes no sense. So I would expect
that such a routine exist.

Thanks in advance and have nice day,

Markus

webcit (text/plain, 6132 bytes) [View| Download]
citadel (text/plain, 5418 bytes) [View| Download]
[#] Wed Jan 20 2021 14:28:09 EST from omatnet

Subject: Is it possible to increase/bypass Email Aliases limit of 512 chars?

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

Hi,

I’m migrating to Citadel 929 with WebCit 926 from Citadel/Webcit 8.15.

I found out that in WebCit 926 “Internet e-mail aliases” (‘menu options Administration’ | ‘Add, change, delete user accounts’ | <editting user configuration>) is now limited to only 512 characters and actually saves a bit less than that. 

So it seems that we are now limited in the number of alias emails we could use per account and better use short emails... This limitation allows for only about 20 aliases, give or take. However, in previous versions of Citadel (like Citadel/Webcit 8.15 where the aliases were defined in ‘Advance’ | ‘Update Your Contact Information’) there was no such limit: I had well over 70 aliases with no problem. I’m struggling now to finish a successful migration without a majour overahll to the email aliases.

Does anyone know (warbaby?) about that and if possible, how to increase, baypass or eliminate this new limitation on number/length of email aliases?

Thank you so much for your help!



[#] Wed Jan 20 2021 14:58:35 EST from omatnet

Subject: Re: Is it possible to increase/bypass Email Aliases limit of 512 chars?

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

More information - I checked and saw that the same issue is with the latest - Citadel 930 with WebCit 927.

I hoped that it may be only a limitation with webcit CSS and not in the script itself or the database, but even when I edited the webcit CSS file (/usr/local/webcit/static/t/aide/edituser/detailview.html) to increase the limitation from 512 characters to 1024 characters, only about 480 are saved and restored, not even 512. at 480 characters with an average of 30 characters per email, you can fit only 15 email aliases (and separating commas)

I really hope you can suggest a solution!

Thanks again

Wed Jan 20 2021 14:28:09 EST from omatnet Subject: Is it possible to increase/bypass Email Aliases limit of 512 chars?

Hi,

I’m migrating to Citadel 929 with WebCit 926 from Citadel/Webcit 8.15.

I found out that in WebCit 926 “Internet e-mail aliases” (‘menu options Administration’ | ‘Add, change, delete user accounts’ | <editting user configuration>) is now limited to only 512 characters and actually saves a bit less than that. 

So it seems that we are now limited in the number of alias emails we could use per account and better use short emails... This limitation allows for only about 20 aliases, give or take. However, in previous versions of Citadel (like Citadel/Webcit 8.15 where the aliases were defined in ‘Advance’ | ‘Update Your Contact Information’) there was no such limit: I had well over 70 aliases with no problem. I’m struggling now to finish a successful migration without a majour overahll to the email aliases.

Does anyone know (warbaby?) about that and if possible, how to increase, baypass or eliminate this new limitation on number/length of email aliases?

Thank you so much for your help!



 



[#] Thu Jan 21 2021 13:10:41 EST from rgreenly

Subject: What is the webroot for citadel?

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

I am trying to install certbot and I know citadel doesn't use Apache, right? Can anyone tell me the webroot?

 

Thanks in advance.

 

-Rob



[#] Thu Jan 21 2021 13:48:13 EST from warbaby

Subject: Re: What is the webroot for citadel?

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

CItadel doesn't have a webroot, neither technically does webcit.

You need to read the docs for letsencrypt/certbot and figure out how to generate a certificate.. [outside the scope here, although if you look back far enough, I have covered it.]

Take a look at the DNS plugins.. unless you're already running a web server on the same box.

Nginx/apache, unless specifically configured FOR webcit, is only going to cause you problems.. [if you need to do it though, use nginx, and certbot nginx, and run webcit on another port.]

Watch for the next post.

 

Thu Jan 21 2021 01:10:41 PM EST from rgreenly Subject: What is the webroot for citadel?

I am trying to install certbot and I know citadel doesn't use Apache, right? Can anyone tell me the webroot?

 

Thanks in advance.

 

-Rob



 



[#] Thu Jan 21 2021 14:20:48 EST from warbaby

Subject: Automating Let's Encrypt Certs For Citadel & webCit

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

I have written this 3 times in the past 20 minutes. [Note to future webcit.. "use LocalStorage']

Generate certificate with certbot .. [5 methods, plus DNS plugins, you have to figure that out for your situation.]

cert appears in /etc/letsencrypt/live/mydomain.org

download & run the attached script..

It takes 1 argument.. the fqdn matching your cert (or at least, the name of the directory that it's in..]

run as root

./citadel-cert-import.sh mydomain.org

you can also cron it.

crontab -e

# Import certs to citadel & webcit

0 0 1 * * /path/to/citadel-cert-import.sh mydomain.org > /dev/null 2>&1

save and exit..

please note, you will also have to restart to take effect..

service citadel restart && service webcit-https restart

This is not what you do to renew your certificate! 

That might be simple, or complex..

it might only be

certbot renew  # wherever it is, that's what you cron also..

[but it depends on your setup..]

But this will keep

/usr/local/citadel/keys

and

/usr/local/webcit/keys

in sync with /etc/letsencrypt/live/mydomain.org

 



citadel-cert-inport.sh (application/x-shellscript, 947 bytes) [ View | Download ]
Go to page: First ... 26 27 28 29 [30] 31 32 33 34 ... Last