Language:
switch to room list switch to menu My folders
Go to page: 1 2 3 [4] 5 6 7 8 ... Last
[#] Fri Apr 08 2016 10:10:26 EDT from zooer @ Uncensored

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

Is there a way to tell if a room is networked in the web interface room list or from the header on top of the messages?



[#] Sat Apr 09 2016 08:59:05 EDT from Freakdog @ Dog Pound BBS II

Subject: Re: c_port setting

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

It appears that this could be resolved through running
/var/lib/citadel/setup because it asks for the port to use. Please

The installation documentation states to run "setup" upon installation, right? If so, then following the process in the documentation and paying full attention to the prompts should suffice, should it not?

[#] Sat Apr 09 2016 09:01:31 EDT from Freakdog @ Dog Pound BBS II

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

Is there a way to tell if a room is networked in the web interface
room list or from the header on top of the messages?

I don't believe so...unless the sysop edits the room info to indicate such.

Though, truth be told, it used to be that a room had to be set as a network room, back in the day, and the room's prompt in a text session displayed a ")" (or was it "]") at the end of the room name if it was.

Nowadays, even in the text client, you can't necessarily tell if a room is networked, anymore.

[#] Sun Apr 10 2016 09:10:56 EDT from IGnatius T Foobar @ Uncensored

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

Normal room>

Directory room]

Network room)

Network+directory room}

The thing is, though, these constructs are reflective of 30+ year old data models that don't make sense anymore.  Citadel has a lot of that and I've been doing a lot of thinking about what other assumptions it's time to cut loose.  At its core, Citadel is about the seamless flow of attention from room to room, about the software getting out of your way as you make your way through the various content on the system.  Everything else is bookkeeping.



[#] Sun Apr 10 2016 11:38:29 EDT from zooer @ Uncensored

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

Where do > ,] ,) or } display on the web interface? 



[#] Sun Apr 10 2016 16:15:18 EDT from IGnatius T Foobar @ Uncensored

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

They don't.

[#] Sun Apr 10 2016 18:56:13 EDT from zooer @ Uncensored

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

That was my question, is there a way to tell network rooms using the web interface.



[#] Mon Mar 07 2016 17:19:27 EST from jame @ Rocasa Mail System

Subject: Citadel not listening on port 504?

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

On a Debian 'stretch' system where I am testing v9.01 of Citidel (using  the 9.01-1+b1 package), Cidadel is starting up but I've found that is not listening on port 504.  Found the following in the log:

 

Message from syslogd@mailtst at Mar  7 15:03:55 ...
citserver[26561]: configuration setting c_port_number is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 504

 
 
Using 'sendcommand CONF GET'  I found that it appears to be set to "0".  Tried using other 'sendcommand CONF' commands in order to try setting it (after dpkg-reconfigure had no effect) but it did not appear to work.  
 
 
 
 
Jame
 
 
 
 
 
 


[#] Tue Mar 08 2016 19:09:25 EST from Freakdog @ Dog Pound BBS II

Subject: Re: Citadel not listening on port 504?

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

Did you run "setup' after you installed?

[#] Wed Mar 09 2016 08:45:11 EST from jame @ Rocasa Mail System

Subject: Re: Citadel not listening on port 504?

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

 

Tue Mar 08 2016 19:09:25 EST from Freakdog @ Dog Pound BBS II Subject: Re: Citadel not listening on port 504?
Did you run "setup' after you installed?

Ran it manually and was able to set the port to the standard port number '504', after which, it is listening on the port like it should be.  Thanks!

 

 

 

Jame

 



[#] Tue Apr 05 2016 11:58:36 EDT from Freakdog @ Dog Pound BBS II

Subject: Re: Help port 504 is gone

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

Still trying to fix the port 504 problem. This time from the citadel

client but ran in to a problem there as well


Lobby> . Admin System configuration Network
Segmentation fault



After that I it exits and I find my self at the linux shell prompt.


I'm concerned about the segmentation fault, but port 504 isn't set up by the network config...that's to set up inter-system connection.

It's also not part of the .ASG.

It's set using the commandline tool.


<CITADEL_DIR>/setup

Another thing I noticed in one of your earlier messages was a warning that Citadel shouldn't be set to run as root...I agree.

Set up a "citadel" or "bbs" user, rerun the setup program, specifying that user as the user under which to run Citadel.

When setup is finished, make sure to "chown -R <citadel user> <CITADEL_DIR>"

[#] Mon Apr 11 2016 09:31:56 EDT from Freakdog @ Dog Pound BBS II

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

If you see "@<sysname>" after a poster's name/handle, it's a network room. ;-)OM

Other than that, like I said, if the sysop or aides don't set the room info to mention it, no.

[#] Mon Apr 11 2016 11:37:36 EDT from zooer @ Uncensored

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

You have a little icon for a directory room, you need one for networked room.

 

Then again I need to go back to the text client.  



[#] Tue Apr 12 2016 12:24:20 EDT from destimond @ Uncensored

Subject: Post message issues

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

Hi!

Iam running Citadel 9.01 with WebCit 9.01, server build 9.01 and have some strange issues.

If i create a room and then one of the users post a message to that room, how will that person be able to edit his post or even delete it??

I have tested to set the following setting for that room with no success "All users allowed to post may also delete messages" (if i choose View as: mail folder i am able to delete the post) but when viewing the post in Bulletin Board i am only able to [Reply] [ReplyQuoted] [Move] [Headers] [Print]. (no edit or no delete)

Any one here that can help with this issue??

 


[#] Tue Apr 19 2016 23:55:57 EDT from Starn @ Uncensored

Subject: webcit not working properly.

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

after i setup everything had everything where i could connect via my domain name. and tested everything it all worked fine.

but i rebooted the server and now i get


"

This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator.
Read More...

 

"

 

i've check everything with netstat -lpn 

 

here's it's output

tcp        0      0 0.0.0.0:993             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:995             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:2020            0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:587             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:110             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:143             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      2730/webcit

tcp        0      0 0.0.0.0:465             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:8081            0.0.0.0:*               LISTEN      2733/webcit

tcp        0      0 0.0.0.0:30033           0.0.0.0:*               LISTEN      916/ts3server                                                             

tcp        0      0 0.0.0.0:563             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:119             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN      3264/citserver

 

i am at complete loss as to why i cannot not access my servers webmail 



[#] Wed Apr 20 2016 03:53:26 EDT from Starn @ Uncensored

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

after i setup everything had everything where i could connect via my domain name. and tested everything it all worked fine.

but i rebooted the server and now i get


"

This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator.
Read More...

 

"

 

i've check everything with netstat -lpn 

 

here's it's output

tcp        0      0 0.0.0.0:993             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:995             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:2020            0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:587             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:110             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:143             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      2730/webcit

tcp        0      0 0.0.0.0:465             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:8081            0.0.0.0:*               LISTEN      2733/webcit

tcp        0      0 0.0.0.0:30033           0.0.0.0:*               LISTEN      916/ts3server                                                             

tcp        0      0 0.0.0.0:563             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:119             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN      3264/citserver

 

i am at complete loss as to why i cannot not access my servers webmail 

 


[#] Wed Apr 20 2016 20:14:58 EDT from feri @ Uncensored

Subject: This program was unable to connect or stay connected to the Citadel...

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

Hi!

I found lot of question about this error in the internet. I have installed Citadel following this article: http://www.raspifun.de/viewtopic.php?f=19&p=31 . System is fully new. Raspbian Jessie extended full on 32GB SDXC card. The Raspberry is model B+ V1.2. Have done all that is in the article:

- Raspbian update and upgrade

- Ipv6 enable

- the needed directory created and set up those rights

- all things does in Citadel setup and like recomended, does setup made again, all parameters (except  my own username and password) are the defaults

- set up fixed IP address to Raspi 10.0.0.10, properly give the gateway and nameserver IP's as routers address 10.0.0.5

- rebooted

The Raspi is in a system on routers LAN - no other server is running inside of private network 10.0.0.x.

!!! I does the whole installation 6 till 8 times last night without success (different IP's tested, tested accesss via https, restart Citadel, redo setup and so far, ...) And again tested on again fresh installed Raspbian !!!

May be, you can help me, but i readed tonns of articles about this, but not one was successfull to me.

Thank you,

Feri



[#] Wed Apr 20 2016 15:26:06 EDT from Freakdog @ Dog Pound BBS II

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

 

Wed Apr 20 2016 03:53:26 AM EDT from Starn @ Uncensored

after i setup everything had everything where i could connect via my domain name. and tested everything it all worked fine.

but i rebooted the server and now i get


"

This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator.
Read More...

 

"

 

i've check everything with netstat -lpn 

 

here's it's output

tcp        0      0 0.0.0.0:993             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:995             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:2020            0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:587             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:110             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:143             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      2730/webcit

tcp        0      0 0.0.0.0:465             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:8081            0.0.0.0:*               LISTEN      2733/webcit

tcp        0      0 0.0.0.0:30033           0.0.0.0:*               LISTEN      916/ts3server                                                             

tcp        0      0 0.0.0.0:563             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:119             0.0.0.0:*               LISTEN      3264/citserver

tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN      3264/citserver

 

i am at complete loss as to why i cannot not access my servers webmail 

I don't see port 504 in the mix...port 504 is the Citadel port.

Did you configure it for 504 or for a different port?



[#] Sat Apr 23 2016 10:38:10 EDT from Starn @ Uncensored

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

I used the default settings except for the webcit when it prompted if it i wanted to use port 80. i chose 8080.

that's pretty much the primary change i made. 



[#] Tue Apr 26 2016 08:12:17 EDT from IGnatius T Foobar @ Uncensored

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

There do seem to be a few reports lately of port 504 not coming up.  You can run the setup program and get it started though.

However, for WebCit running on the same host as the Citadel Server, it doesn't use a port number; you merely tell the WebCit setup program what directory Citadel is running in, and it connects to a local socket.



Go to page: 1 2 3 [4] 5 6 7 8 ... Last