Please wait...
0 files
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.]
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.
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.]
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.
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.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.]
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.
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.