On Sun, Mar 24, 2019 at 10:27 AM Gnucash Xboxboy Mageia <xboxboy.mageia+gnucash(a)gmail.com> wrote: I'm not sure which version of Debian you're running? Or which version of LSMB you're testing... (v1.5.x?) Have you already checked that LSMB is running and which IP & port that LSMB is being run on? I usually use 'netstat -tnlp' to verify that (part of the net-tools pkg in Debian/Ubuntu/etc, in case you didn't know...). Trying to access it via the port you mentioned seems to indicate that you're running LSMB 1.5 or LSMB 1.6 but that is defaulted to putting it up on localhost. For instance; I have the v1.5.24 version of the ledgersmb-1.5 pkg (from the apt.ledgersmb.org pkg repo) installed in a Debian v9.6 container (I use LXC) on my laptop, which I used to do a quick test of that pkg version before I made it generally available. There 'starman' (which is running LSMB) is showing like this: root@lsmbtest:~# netstat -tnlp|grep 5762 tcp 0 0 127.0.0.1:5762 0.0.0.0:* LISTEN 99/starman master - tcp6 0 0 ::1:5762 :::* LISTEN 99/starman master - Since I didn't feel like changing it to the network IP in the systemd unit (although that is doable, it gets changed back if the pkg is updated), I just used the varnish proxy (in this case, installed & configured using the ledgersmb-varnish pkg)., which made it available on the network IP up on port 6081. That shows like this: root@lsmbtest:~# netstat -tnlp|grep 6081 tcp 0 0 0.0.0.0:6081 0.0.0.0:* LISTEN 58/varnishd tcp6 0 0 :::6081 :::* LISTEN 58/varnishd -- Robert J. Clay rjclay(a)gmail.com jame(a)rocasa.us

On Sun, Mar 24, 2019 at 8:02 PM Gnucash Xboxboy Mageia <xboxboy.mageia+gnucash(a)gmail.com> wrote: .> I'm not sure which version of Debian you're running? Or which Very good; that indeed indicates that the LSMB application itself is available where it is supposed to be. In our case, we use a reverse proxy, where another web application listens for http requests from a users browser (usually on the standard http ports), sends them to the LSMB application, then sends what LMSB returns back to the users browser. One can use, for instance; apache, nginx, or lighttpd as the web proxy as we support all three; emphasizing https connections for it of course. I understand that you have apache already installed? .Then installing the 'ledgersmb-1.5-apache' pkg would be useful to you; that attempts to auto configure apache to be uses as a web proxy for LSMB. Including to https connections but you'll to update the config specifically for 'ServerName'.apache config item. (In /etc/apache2/sites-available/ledgersmb-1.5-proxy.conf.) -- Robert J. Clay rjclay(a)gmail.com

On Fri, Mar 29, 2019 at 10:53 PM Gnucash Xboxboy Mageia <xboxboy.mageia+gnucash(a)gmail.com> wrote: If you still plan to use Apache as the proxy (for which, access I understand was already working?), then yes. As I noted above ( & allude to in the pkg README.Debian file), yes. And then the config file needs to be enabled so that apache can see it and then apache needs to be restarted in order to use the changes. -- Robert J. Clay rjclay(a)gmail.com

On Fri, Apr 19, 2019 at 1:03 AM Xboxboy Mageia <xboxboy.mageia(a)gmail.com> wrote: Don't worry, it's fairly easy to pick up. Like for all Debian packages, it's in a directory in /usr/share/doc/ named after the package. So in this case, it's in /usr/share/doc/ledgersmb-1.5/. Note also that it's also standard on Debian that if the file is over a certain size, the file is installed as compressed; so the file name to be looked for is 'README.Debian.gz'. (I use the 'mc' app to view such files; it can handle compressed text files with no issue.) Reviewing that README file again in light of explaining it to you, I don't think I go into enough detail, so I'll need to work on that... The example LSMB distribution file 'apache-vhost.conf' is installed by the pkg as 'ledgersmb-1.5-proxy.conf' to the /etc/apache2/sites-available/ directory. Much of that file is already configured by default by the pkg, but the 'ServerName' item is not configured by default (which is why the pkg install does not curently attempt to enable the config file by default). Once that is set, on Debian you can enable it by using something like: a2ensite ledgersmb-1.5-proxy.conf If that doesn't come up with any issues, then: systemctl reload apache2 If no issues come up, you can try accessing the LSMB setup page by going to https://server.name.com/setup.pl (or you could try via the IP...) Then go to the 'DB admin login' dropdown and select "lsmb-dbadmin"; then enter its password (which would have been configured during the main pkg install). Then enter the company name you want to use in the 'Database' field. Then click on the 'Create' button. If there are no issues, the next thing that will come up after a few moments is a 'Country Code' dropdown. Select what you want to use for this company database and then click on 'Next'. The next page that comes up has dropdowns for 'Chart of Accounts' and 'GIFI'. If you want something besides the defaults there, select what you want & then click on 'Next' again. Then you get the page where you can select the Template to load. Selecting the default 'demo_with_images' is fine and you can then click on the 'Load Templates' button. The next page that comes up is for creating a user for within the LSMB application itself. For the first user being added, I'll usually set the 'Assign Permissions' dropdown to "Full Permissions". Then click on the 'Create User' button. If everything is good, you'll get one last page. It'll list the Database Credentials used to create it. And note that the 'Database Operation Complete'. And you'll have the options to 'Return to Setup', or 'Start Using LedgerSMB'. if you go to the LSMB login page, you'll need to enter the LSMB User Name (like what you just created) and its password, the Company datebase name you want to use (like what you just created). Clicking the 'Login' button should take you to the Welcome screen. Note that when you first log in with newly created user to LSMB, you might should go to the 'Preferences' pages and reset its password to ensure that it doens't expire overnight. Any questions/comments/concerns etc, please let us know. -- Robert J. Clay rjclay(a)gmail.com