fmiser wrote:
I'm having troubles with configuration, setup, running.
Erik wrote:
By commenting out the line "LISTEN_ADDRESS=localhost" (and restarting the ledgersmb service, i.e. Starman), Starman will bind to all available interfaces,
fmiser wrote:
Well, it did not work.
So then I ran dpkg-reconfigure and told it to NOT setup for Apache as a Web Reverse Proxy (which I had done earlier) Now I cannot even connect using links2.
http://192.168.6.16:5762/login.pl browser error "192.168.6.16 refused to connect."
Hmm. I didn't understand that this worked before. I thought you were logging into the machine using SSH and then using lynx or links2.
I guess I wasn't as clear as I thought I was... I am trying to use a GUI browser from outside, and using links2 when logged in over SSH. So far I have never gotten a connection to work from "outside" the server.
Do you have any idea if there's a firewall in place which may be blocking port 5762? (or maybe all ports except e.g. 22, 80 and/or 443?)
I'm pretty sure there isn't one # iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination
However, if I log in over SSH, links2 works if I use localhost http://localhost:5762/login.pl
but not if I use the IP address. http://192.168.6.16:5762/login.pl
Next I tried using the IP address rather than just commenting out the "listen_address" in /etc/default/ledgersmb
Ok. But did you try the situation with the commented-out
Yup. :(
#####LISTEN_ADDRESS=localhost LISTEN_ADDRESS=192.168.6.16 LISTEN_PORT=5762
Same errors as above
... my main question would be: did you restart the ledgersmb service after you edited /etc/default/ledgersmb ?
Yes.
Also, which version of Debian did you install? I saw above that you said "fresh installation of Debian", but is that Buster or Stretch or Sid or ...? If this is Buster, I think we might be banging on the wrong door:
It is Buster, Debian 10. Sorry, I sure intended to mention that. I could document each step, but in general: From a browser on the LAN http://172.20.6.16/ Works - shows Apache default page http://172.20.6.16/login.pl "not found" error http://172.20.6.16:5762/login.pl "unable to connect" error From a "internal" browser (links2, 'cause X is not installed) http://localhost/ Works - shows apache default page http://localhost/login.pl "not found" error http://localhost:5762/login.pl works - see login http://172.20.6.16/ Works - shows apache default page http://172.20.6.16/login.pl "not found" error http://172.20.6.16:5762/login.pl "connection refused" error
... in that case, we probably should be looking in the "ledgersmb.service" (or something named like it) file to change the starman startup parameters.
Would that be "/etc/init.d/ledgersmb"? I also see /usr/share/ledgersmb/conf/systemd/ledgersmb_starman.service /usr/lib/systemd/system/ledgersmb.service Those appear to be identical ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ # Place this in /etc/systemd/system/ledgersmb_starman.service # systemctl enable ledgersmb_starman # service start ledgersmb_starman [Unit] Description=LedgerSMB Starman After=network.target [Service] WorkingDirectory=/usr/share/ledgersmb # In case you installed dependencies into a 'local::lib' # make sure you set the PERL5LIB environment variable # to the correct location by uncommenting the line below #Environment=PERL5LIB=/path/to/local-lib/lib/perl5 Environment=LSMB_CONFIG_FILE=/etc/ledgersmb/ledgersmb.conf # Be sure to set a user and group below # which don't have write access to the directories # holding the LedgerSMB sources User=ledgersmb Group=ledgersmb ExecStart=/usr/bin/starman \ --listen localhost:5762 \ -I lib \ -I old/lib \ bin/ledgersmb-server.psgi Restart=always [Install] WantedBy=multi-user.target ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Also /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ledgersmb.service which is an empty file.
I don't have a Debian 10 handy right now, so if you let me know which Debian version, I'll spin one up and see what the package looks like in installed form (note that Jaime maintains the package; I just know how to analyse it).
I would sure appreciate any help! I'm still trying to adapt to systemd... -- f