Mon Nov 23 2020 11:53:02 AM EST from hamiltra @ Uncensored Subject: Error with easyinstaller build on Ubuntu 20.10 with fresh install

I did a fresh install of Ubuntu 20.10 (amd64) and tried the citadel-suite without success.  it was a very old version 917 which was throwing a lot of segfault messages into the syslog.  Uninstalled that version and did some cleanup.  Then, I tried the build from scratch using easyinstall shell and to keep the files as was posted in this forum last week, but then I got an error:

Thanks for reporting, and for pointing out the fix.  This has been corrected in 1e99d3eab849c3c41341d2d9b055ea7ee6a058a3 and will appear in the next release.

Ok. I understand that a little better. Webcit launches with a switch -g/dotgoto?room=Welcome%to%uncensored%21 

And that room is a wiki with the welcome window that is displayed. 

The room is hidden, though, right? regular users can't see or post to it. 

Sun Dec 06 2020 13:29:23 EST from IGnatius T Foobar @ Uncensored Subject: Re: Initial Citadel Welcome Screen

You're saying that you've set it up so that when a user connects, it
launches "webcit -g/path" 
And at that path is "Welcome%20to%20uncensored%21" 

More or less. The "-g" option just tells it where to redirect "/" to.

The path "/dotgoto?room=XX" is the WebCit command to goto a room, where XX is the name of the room.

I have a room called "Welcome to UNCENSORED!" which is a wiki room whose home page is a welcome screen. To use its name in a URL we have to escape the spaces to %20 and the exclamation point to %21.

You could send the landing page pretty much anywhere. It would probably work with an external reference but I haven't tried it.

As to where this is configured ... you put it wherever WebCit is started.
For most sites that's going to be /etc/systemd/system/webcit-http.service and /etc/systemd/system/https.service

Actually, this room: 

So, I think that webcit is called in /etc/systemd/system/webcit-http.service and /webcit-https.service - if I understand how systemd works. 

in webcit-https.service, I see this line: 

ExecStart=/usr/local/webcit/webcit -s -p4916 uds /usr/local/citadel

so that would change to something like:

ExecStart=/usr/local/webcit/webcit -g Welcome%20to%20Roomname%21 -p4916 uds /usr/local/citadel 

Where there was a room, as a Wiki, on my Citadel called "Welcome To Roomname!"

And the same edit would be made to webcit-https.service? 

ExecStart=/usr/local/webcit/webcit -g Welcome%20to%20Roomname%21 -p8916 uds /usr/local/citadel

Do I just edit the files webcit-https.service and webcit-http.service with vi or nano to make these changes?

 Do I have this right? 

Sun Dec 06 2020 13:29:23 EST from IGnatius T Foobar @ Uncensored Subject: Re: Initial Citadel Welcome Screen

You're saying that you've set it up so that when a user connects, it
launches "webcit -g/path" 
And at that path is "Welcome%20to%20uncensored%21" 

More or less. The "-g" option just tells it where to redirect "/" to.

The path "/dotgoto?room=XX" is the WebCit command to goto a room, where XX is the name of the room.

I have a room called "Welcome to UNCENSORED!" which is a wiki room whose home page is a welcome screen. To use its name in a URL we have to escape the spaces to %20 and the exclamation point to %21.

You could send the landing page pretty much anywhere. It would probably work with an external reference but I haven't tried it.

As to where this is configured ... you put it wherever WebCit is started.
For most sites that's going to be /etc/systemd/system/webcit-http.service and /etc/systemd/system/https.service

I have a fuzzy memory of documentation on how to set this up, but I can't find it now on the citadel.org documentation pages. 

How do you set up BBS to not require a password and launch the textclient automatically from a SSH session? 

Does it involve making sure that the bbs account has just user permissions, no password, and their startup shell is /usr/local/citadel/citadel 
So that a ssh connection to bbs@ssh.wallofhate.com automatically logs in and starts the citadel text client? 

Sun Dec 06 2020 21:45:55 EST from ParanoidDelusions @ Uncensored Subject: bbs@uncensored.citadel.org

I have a fuzzy memory of documentation on how to set this up, but I can't find it now on the citadel.org documentation pages. 

How do you set up BBS to not require a password and launch the textclient automatically from a SSH session? 

 Do I have this right? 

Sun Dec 06 2020 13:29:23 ESTfrom IGnatius T Foobar @ Uncensored Subject: Re: Initial Citadel Welcome Screen

You're saying that you've set it up so that when a user connects, it
launches "webcit -g/path" 
And at that path is "Welcome%20to%20uncensored%21" 

More or less. The "-g" option just tells it where to redirect "/" to.

The path "/dotgoto?room=XX" is the WebCit command to goto a room, where XX is the name of the room.

I have a room called "Welcome to UNCENSORED!" which is a wiki room whose home page is a welcome screen. To use its name in a URL we have to escape the spaces to %20 and the exclamation point to %21.

You could send the landing page pretty much anywhere. It would probably work with an external reference but I haven't tried it.

As to where this is configured ... you put it wherever WebCit is started.
For most sites that's going to be /etc/systemd/system/webcit-http.service and /etc/systemd/system/https.service

But I have to set up Citadel to let users who are not logged in browse the server, right? I can't just make one room visible, it has to be set globally for the entire BBS? 

Otherwise, I get "You must be logged in to access this page" on the regular login screen. 

Sun Dec 06 2020 22:24:31 EST from ParanoidDelusions @ Uncensored

Subject: Re: Initial Citadel Welcome Screen

Missed this. Yeah, I guess I've got it right. 

 

 

So, I tried putting it in /home/bbs/.ssh/rc

"/usr/local/citadel/citadel"



And that executes citadel when I connect via SSH... but it quits immediately and takes me back to the shell:


bbs@testtsbbs:~$ ssh bbs@127.0.0.1
bbs@127.0.0.1's password:
Linux testtsbbs 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Dec  6 21:42:23 2020 from 127.0.0.1
Attaching to server...
[localhost:504]
Citadel 929            
Citadel Server
(null)
 pause    next    stop
 ctrl-s  ctrl-o  ctrl-c

Cannot open '/usr/local/citadel/messages//hello': No such file or directory

Enter your name: bbs@testtsbbs:~$

Sun Dec 06 2020 21:57:52 EST from ParanoidDelusions @ Uncensored Subject: Re: bbs@uncensored.citadel.org

Does it involve making sure that the bbs account has just user permissions, no password, and their startup shell is /usr/local/citadel/citadel 
So that a ssh connection to bbs@ssh.wallofhate.com automatically logs in and starts the citadel text client? 

Sun Dec 06 2020 21:45:55 EST from ParanoidDelusions @ Uncensored Subject: bbs@uncensored.citadel.org

I have a fuzzy memory of documentation on how to set this up, but I can't find it now on the citadel.org documentation pages. 

How do you set up BBS to not require a password and launch the textclient automatically from a SSH session? 

 

If I immediately execute "/usr/local/citadel/citadel" after it dumps me back out to the shell, the text client loads and works perfectly, and disconnects the SSH session on exit. 

figured it out. 

in .profile

/usr/local/citadel/citadel
exit

Logs in with the account, immediately launches citadel, then when I .tq it exits the SSH session immediately. 

Is this a secure way to do this? 

Mon Dec 07 2020 00:15:30 EST from ParanoidDelusions @ Uncensored Subject: Re: bbs@uncensored.citadel.org

If I immediately execute "/usr/local/citadel/citadel" after it dumps me back out to the shell, the text client loads and works perfectly, and disconnects the SSH session on exit. 

 

There is no error checking or sanity to this, so if usr/local/citadel/citadel fails to launch, will it just proceed to the exit command and dump them right back out, or will it throw up an error and stop the script from processing the exit, leaving them in the system at a bash prompt? 

Mon Dec 07 2020 00:38:09 EST from ParanoidDelusions @ Uncensored Subject: Re: bbs@uncensored.citadel.org

Is this a secure way to do this? 

So, the documentation says: 

To configure a "public" Citadel system, edit your system configuration to disable "require login". If this option is enabled, users can browse the system in "guest mode" without logging in first. This will also permit the search engines to index your site, so be sure this is what you want.

Guest users (not logged in) will not be permitted to post messages or view private rooms.

But I don't see where to do that. 

In site-wide settings in the Administration menu you can set "Allow anonymous guest access" - but I looked in the .rc files and I don't see any flag for "require login" and I couldn't find any other reference to it in the Citadel documentation. 

But I think that is required in order to make this work? 

I feel like I'm pretty close - but it isn't quite working yet. 

Sat Dec 05 2020 13:48:47 EST from IGnatius T Foobar @ Uncensored Subject: Re: Initial Citadel Welcome Screen

I don't know if it's in the documentation, but you use the -g option to webcit to define the start page that appears when a user first lands on the site.
Mine is: -g/dotgoto?room=Welcome%20to%20uncensored%21 So it takes new users to a read-only wiki room whose home page is a welcome screen.

Administration .. Edit site-wide .. Access .. last two options on that tab.

OR do it with sendcommand,

# READ the existing values..

./sendcommand "CONF GETVAL|c_regiscall"

./sendcommand "CONF GETVAL|c_guest_logins"

# SET new values

./sendcommand "CONF PUTVAL|c_guest_logins|1"

./sendcommand "CONF PUTVAL|c_regiscall|0"

Mon Dec 07 2020 09:45:01 AM EST from ParanoidDelusions @ Uncensored Subject: Re: Initial Citadel Welcome Screen

So, the documentation says: 

To configure a "public" Citadel system, edit your system configuration to disable "require login". If this option is enabled, users can browse the system in "guest mode" without logging in first. This will also permit the search engines to index your site, so be sure this is what you want.

Guest users (not logged in) will not be permitted to post messages or view private rooms.

But I don't see where to do that. 

In site-wide settings in the Administration menu you can set "Allow anonymous guest access" - but I looked in the .rc files and I don't see any flag for "require login" and I couldn't find any other reference to it in the Citadel documentation. 

But I think that is required in order to make this work? 

I feel like I'm pretty close - but it isn't quite working yet. 

 

Sat Dec 05 2020 13:48:47 EST from IGnatius T Foobar @ Uncensored Subject: Re: Initial Citadel Welcome Screen

I don't know if it's in the documentation, but you use the -g option to webcit to define the start page that appears when a user first lands on the site.
Mine is: -g/dotgoto?room=Welcome%20to%20uncensored%21 So it takes new users to a read-only wiki room whose home page is a welcome screen.

 

Wups, forgot the descriptions.

c_regiscall   # Flag (0 or 1) - require registration for new users.

c_guest_login # Allow anonymous guest logins. Set to 1 to allow.

Mon Dec 07 2020 12:00:28 PM EST from warbaby @ Uncensored Subject: Re: Initial Citadel Welcome Screen

Administration .. Edit site-wide .. Access .. last two options on that tab.

OR do it with sendcommand,

# READ the existing values..

./sendcommand "CONF GETVAL|c_regiscall"

./sendcommand "CONF GETVAL|c_guest_logins"

# SET new values

./sendcommand "CONF PUTVAL|c_guest_logins|1"

./sendcommand "CONF PUTVAL|c_regiscall|0"

Mon Dec 07 2020 09:45:01 AM EST from ParanoidDelusions @ Uncensored Subject: Re: Initial Citadel Welcome Screen

So, the documentation says: 

To configure a "public" Citadel system, edit your system configuration to disable "require login". If this option is enabled, users can browse the system in "guest mode" without logging in first. This will also permit the search engines to index your site, so be sure this is what you want.

Guest users (not logged in) will not be permitted to post messages or view private rooms.

But I don't see where to do that. 

In site-wide settings in the Administration menu you can set "Allow anonymous guest access" - but I looked in the .rc files and I don't see any flag for "require login" and I couldn't find any other reference to it in the Citadel documentation. 

But I think that is required in order to make this work? 

I feel like I'm pretty close - but it isn't quite working yet. 

 

Sat Dec 05 2020 13:48:47 EST from IGnatius T Foobar @ Uncensored Subject: Re: Initial Citadel Welcome Screen

I don't know if it's in the documentation, but you use the -g option to webcit to define the start page that appears when a user first lands on the site.
Mine is: -g/dotgoto?room=Welcome%20to%20uncensored%21 So it takes new users to a read-only wiki room whose home page is a welcome screen.

 

 

TY. I think this will get me sorted, and shut me up for a while. 

Mon Dec 07 2020 12:00:28 EST from warbaby @ Uncensored Subject: Re: Initial Citadel Welcome Screen

Administration .. Edit site-wide .. Access .. last two options on that tab.

OR do it with sendcommand...

So, I did these, and c_guest_login returns a 1 and c_regiscall returns a 0. 

Which are the values you suggest changing it to in order to make this work? 

I've also verified that I can view Known Rooms without logging in, and view contents/posts in the known rooms. I've tried various combinations of adding the "-g/dotgoto?room=" command, moving it before and after the "-p8916 uds /usr/local/citadel" portion of webcit-http.service. I've tried wrapping the room name in quotes, and I've tried changing the name to simply "welcome" and putting just that in to webcit-http.service. I've ran tail syslog -f and I'm getting various errors - mostly 404 errors. 

The address I'm putting in the browser is:

http://127.0.0.1:8916 and what I expect it to redirect to should be http://127.0.0.1:8916/welcome at this point. 

Is it because I'm using a non-standard port? 

If I just open a page to http://127.0.0.1:8916/welcome - it actually successfully navigates to 127.0.0.1/wiki?page=home 

Which *is* where it should redirect to from the webcit-http.service when it launches webcit. 

I'll post the tail logs separately. 

Mon Dec 07 2020 12:41:31 EST from warbaby @ Uncensored Subject: Re: Initial Citadel Welcome Screen

Wups, forgot the descriptions.

c_regiscall   # Flag (0 or 1) - require registration for new users.

c_guest_login # Allow anonymous guest logins. Set to 1 to allow.

Mon Dec 07 2020 12:00:28 PM EST from warbaby @ Uncensored

root@testtsbbs:/home/bbs# tail /var/log/syslog -f
Dec  7 16:17:09 testtsbbs webcit[548]: GET /wiki?page=home HTTP/1.1
Dec  7 16:17:09 testtsbbs citserver[2309]: citserver[2309]: msgbase: CtdlFetchMessage(0, 1) Failed!
Dec  7 16:17:09 testtsbbs webcit[548]: ConditionalWholistExpanded() returns 0
Dec  7 16:17:09 testtsbbs webcit[548]: webcit[548]: HTTP: 200 [0.000867] GET dotskip?room=welcome
Dec  7 16:17:09 testtsbbs citserver[2309]: msgbase: CtdlFetchMessage(0, 1) Failed!
Dec  7 16:17:09 testtsbbs webcit[548]: HTTP: 200 [0.000867] GET dotskip?room=welcome
Dec  7 16:17:09 testtsbbs webcit[548]: webcit[548]: GET /do_template?template=iconbar_user HTTP/1.1
Dec  7 16:17:09 testtsbbs webcit[548]: webcit[548]: HTTP: 200 [0.001703] GET /do_template?template=iconbar_user
Dec  7 16:17:09 testtsbbs webcit[548]: GET /do_template?template=iconbar_user HTTP/1.1
Dec  7 16:17:09 testtsbbs webcit[548]: HTTP: 200 [0.001703] GET /do_template?template=iconbar_user

After checking "allow anonymous guest access" in the Administrator, Access tab, running some test, and then unchecking it - Citadel could not see any rooms. It was displaying just the text, "room not found" on a white page. 

I did ./sendcommand down after which,  a ./sendcommand up said "socket can't be reached". I did a systemctl reboot and everything came back up - but now the server is responding very slow (it seems like it is having problems with SSL connections failing and retrying) and the rss feeds are not updating. I tried deleting and recreating a room with an rss feed, and it made no difference. Any suggestions? 

Dec  8 11:03:25 tsbbs citserver[5071]: citserver[5071]: rssclient: using libcurl/7.64.0 OpenSSL/1.1.1d zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.36.0 librtmp/2.3

Dec  8 11:03:25 tsbbs citserver[5071]: citserver[5071]: Existing database version on disk is 929

Dec  8 11:03:25 tsbbs citserver[5071]: rssclient: using libcurl/7.64.0 OpenSSL/1.1.1d zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.36.0 librtmp/2.3

Dec  8 11:03:25 tsbbs citserver[5071]: Existing database version on disk is 929

Dec  8 11:03:26 tsbbs citserver[5071]: citserver[5071]: netspool: InspectQueuedRoom(Reddit MiSTer rss)

Dec  8 11:03:26 tsbbs citserver[5071]: netspool: InspectQueuedRoom(Reddit MiSTer rss)

Dec  8 11:03:54 tsbbs citserver[5071]: citserver[5071]: rssclient: failed to load feed: Timeout was reached

Dec  8 11:03:54 tsbbs citserver[5071]: rssclient: failed to load feed: Timeout was reached

Dec  8 11:04:22 tsbbs citserver[5071]: citserver[5071]: rssclient: failed to load feed: Timeout was reached

Dec  8 11:04:22 tsbbs citserver[5071]: rssclient: failed to load feed: Timeout was reached

Dec  8 11:04:50 tsbbs citserver[5071]: citserver[5071]: rssclient: failed to load feed: Timeout was reached

Dec  8 11:04:50 tsbbs citserver[5071]: rssclient: failed to load feed: Timeout was reached

Dec  8 11:05:18 tsbbs citserver[5071]: citserver[5071]: rssclient: failed to load feed: Timeout was reached

Dec  8 11:05:18 tsbbs citserver[5071]: rssclient: failed to load feed: Timeout was reached

Dec  8 11:05:46 tsbbs citserver[5071]: citserver[5071]: rssclient: failed to load feed: Timeout was reached

Dec  8 11:05:46 tsbbs citserver[5071]: rssclient: failed to load feed: Timeout was reached

Dec  8 11:06:14 tsbbs citserver[5071]: citserver[5071]: rssclient: failed to load feed: Timeout was reached

Dec  8 11:06:14 tsbbs citserver[5071]: rssclient: failed to load feed: Timeout was reached

Dec  8 11:06:42 tsbbs citserver[5071]: citserver[5071]: rssclient: failed to load feed: Timeout was reached

Dec  8 11:06:42 tsbbs citserver[5071]: rssclient: failed to load feed: Timeout was reached

root@tsbbs:/home/bbs# Dec  8 11:04:50 tsbbs citserver[5071]: citserver[5071]: rssclient: failed to load feed: Timeout was reached

bash: Dec: command not found

root@tsbbs:/home/bbs# Dec  8 11:04:50 tsbbs citserver[5071]: rssclient: failed to load feed: Timeout was reached

bash: Dec: command not found

Dec  8 11:06:14 tsbbs citserver[5071]: citserver[5071]: rssclient: failed to load feed: Timeout was reached

Dec  8 11:06:14 tsbbs citserver[5071]: rssclient: failed to load feed: Timeout was reached

Dec  8 11:06:42 tsbbs citserver[5071]: citserver[5071]: rssclient: failed to load feed: Timeout was reached

root@tsbbs:/home/bbs# Dec  8 11:05:18 tsbbs citserver[5071]: citserver[5071]: rssclient: failed to load feed: Timeout was reached