- users - lists.freelock.com

Looking for translators of Malay, Various Spanish variants and Portugese
by Erik Huelsmann 22 Feb '22

22 Feb '22

Hi! The project received a Hebrew translation last week. Which is great! Unfortunately, we have a few translations without translators. These translations have very good translation levels already and merely need to be kept up to date. We're looking for translators for: - Malay - Spanish (various variants; e.g. Colombian, Paraguayan) - Portugese For any other languages without translators - for which the effort required to get to a good translation level might be a bit higher, though - please have a look at https://www.transifex.com/ledgersmb/ledgersmb/dashboard/ If you need help getting started, please drop by in our chat channel at https://app.element.io/#/room/#ledgersmb:matrix.org or reply to this e-mail on this mailing list so we can help you get started! Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

LedgerSMB 1.9.10 released
by Erik Huelsmann 22 Feb '22

22 Feb '22

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains the following fixes and improvements: Changelog for 1.9.10 * Second fix for sending e-mail due to the incompatibility in Workflow 1.59 * Freshly contributed Hebrew translation For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.9.10/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.9.10 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.9.10 Or pulled from GitHub Container Registry using the command $ docker pull ledgersmb/ledgersmb:1.9.10 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.9.10 These are the sha256 checksums of the uploaded files: 3432498a93d72f2b7a250b32595a2930d539bb9b086e0de68bb46e7fd5348203 ledgersmb-1.9.10.tar.gz 203f2cc83045937eb5627f1ba2a1615f3b2c2b1bd8a4344531e3f3c2264f8e94 ledgersmb-1.9.10.tar.gz.asc

1 0

Re: nginx Error
by Erik Huelsmann 20 Feb '22

20 Feb '22

Hi Mathew, On Sat, Feb 19, 2022 at 10:49 PM Mathew Cox <edmondshire(a)live.com> wrote: > The directions I was using was the following: > > > > https://ledgersmb.org/content/installing-ledgersmb-19 > > > Where things broke down for me was from the sections titled “Configuring a > Reverse Proxy” all the way to the end. I had initially ignored the reverse > proxy section and that didn’t really suit my purposes. > Ok. So, I think the quickest and simplest way to resolve your situation is to change the content of your "ledgersmb-starman.service" file. If you change the line --listen localhost:5762 \ to --port 5762 \ and run systemctl daemon-reload and then restart the service (systemctl restart ledgersmb-starman), you should see netstat output with column 4 " 0.0.0.0:5762" and column 5 "0.0.0.0:*" for the ledgersmb starman server. You should also be able to access the service from any other devices on your home network. Please note that your password can be snooped by anybody with access to your network with this setup (at login time) because the connection won't be encrypted to the server. (I already understood you to be aware of this, but whoever reads this conversation on the mailing list, might have missed that earlier part of the conversation.) > There is much I don’t understand from this point because I can simply go > to the machine address (192.168.88.15) and I get the standard nginx > greeting. > > > > Everything else has worked flawlessly. > There's just a single other downside to not using the proxy: when using the proxy, the static assets will be served by the ledgersmb-starman instead of by Nginx and in terms of speed and resource use, nginx is much faster and more efficient. The one time this is most noticeable is when you log in, so if you're satisfied with the login speed you get, then there's no reason to try to set up the reverse proxy for that purpose. > I did try and connect through port (http://192.168.88.15:5762) and that > page couldn’t be reached. > Yea. As Pete pointed out: the ledgersmb-starman server isn't listening on 192.168.88.15; it's only listening on ::1/128 and/or 127.0.0.1 (on the same port). > Now take what I’m about to say with a grain of salt as it comes from a > place of ignorance: > To keep focus, I'll wait for you to make the above changes and see if you're satisfied with those. After you are (or if you need the reverse proxy after all so you need the steps below), we can go oven the steps below and what they should have been. Regards, Erik. > > > I don’t understand how nginx references the install directory with the > standard nginx configuration. I copied: > > > > within the nginx-vhost.conf file I edited the part where it says root > WORKING_DIR/UI to root /opt/ledgersmb/UI > > > > then > > > > sudo cp /opt/ledgersmb/doc/config/webserver/nginx-vhost.conf > /etc/nginx/available-sites/ledgersmb.conf > > > > within the nginx-vhost.conf file I edited the part where it says root > /opt/ledgersmb/UI > > and then created the link > > ln -s /etc/nginx/sites-available/ledgersmb.conf /etc/nginx/sites-enabled/ > > > > This naturally failed to enable nginx because I assume this line: > > > > server { > > listen 443 ssl; > > listen [::]:443 ssl ipv6only=on; > > > > Was not correct, which I changed to: > > > > server { > > listen 80; > > #listen [::]:443 ssl ipv6only=on; > > > > This seemed to work as nginx fired right up but I was still getting the > standard nginx greeting page on port 80 (which might be normal) but the > connection was still refused on 5762. > > > > So then in the nginx.conf file under the http{} section I added > > > > Include /etc/nginx/sites-available/ledgersmb.conf > > > > Which again was the nginx-vhost.conf file I modified and changed the name > to ledgersmb.conf. > > > > Though I now can’t recall if that failed to start the nginx service or not > as much of what has happened is pretty much egg soufflé. If it didn’t > start nginx I just deleted it but if it did start it, I still can’t pullup: > > > > http://192.168.88.15:5762/setup.pl > > > > > > > > I hope some or all of this makes sense as I’m trying to be as clear as > possible so to avoid confusion. > > > > I sincerely thank you for your time. > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows > > > ------------------------------ > *From:* Erik Huelsmann <ehuels(a)gmail.com> > *Sent:* Saturday, February 19, 2022 12:34:17 PM > *To:* Mathew Cox <edmondshire(a)live.com> > *Cc:* users(a)lists.ledgersmb.org <users(a)lists.ledgersmb.org> > *Subject:* Re: [ledgersmb-users] nginx Error > > Hi Mathew, > > On Sat, Feb 19, 2022 at 8:34 PM Mathew Cox <edmondshire(a)live.com> wrote: > > I’m still confused. > > > Hopefully we can resolve that! > > > I tried going the reverse proxy route but that doesn’t help because I > don’t own a domain name so certbot won’t send me any certs. > > > Now I'm confused: The error you presented comes from Nginx. The only role > that Nginx has in the installation instructions *is* as a reverse proxy > (but you're no longer trying to go that route?). From where I stand, those > are contradictory signals. Can you provide a bit more information of what > you *have* done, which information you used to do it (including a link to > the installation instructions you're using) and which steps you considered > successful, if any? > > > Which was unexpected, I just wanted to run this software on my own home > network but that presents a problem as I am at a complete loss how to > install the software and configure it in such a way that I can simply > access it on my private home network. > > > Ok. I think you may have missed the key point of Pete's mail: you are > almost there and if you're the only user, there's no need to have the > reverse proxy, but you *do* need the server to listen on an address which > can be reached from the other devices on your home network. It's the > "reachable from the other devices on your home network" part which you had > not achieved yet in the mail he answered to, because the server was > strictly listening to connections from itself. > > > Is there any guide or lesser known website that lays out what is required > to simply self host the software on a private network without the necessity > of having a domain name? > > > I'm not aware of any lesser known sites which document it. There's > explicitly not a guide on the main site because it might encourage people > to set up LedgerSMB insecurely. However, in your use-case, getting a > certificate is indeed overkill (although you could generate a so called > self-signed certificate, which would eliminate the need of owning a domain > to go to certbot, but that's a whole can of worms in itself). So, when I > know what is your reference documentation and to what step you have > completed the instructions, I can probably indicate what you need to do to > bind the serverprogram to an external address instead of an internal > address. That way it will become reachable from other network devices. > > > Regards, > > -- > Bye, > > Erik. > > http://efficito.com -- Hosted accounting and ERP. > Robust and Flexible. No vendor lock-in. > -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

Re: nginx Error
by Erik Huelsmann 19 Feb '22

19 Feb '22

Hi Mathew, On Sat, Feb 19, 2022 at 8:34 PM Mathew Cox <edmondshire(a)live.com> wrote: > I’m still confused. > Hopefully we can resolve that! > I tried going the reverse proxy route but that doesn’t help because I > don’t own a domain name so certbot won’t send me any certs. > Now I'm confused: The error you presented comes from Nginx. The only role that Nginx has in the installation instructions *is* as a reverse proxy (but you're no longer trying to go that route?). From where I stand, those are contradictory signals. Can you provide a bit more information of what you *have* done, which information you used to do it (including a link to the installation instructions you're using) and which steps you considered successful, if any? > Which was unexpected, I just wanted to run this software on my own home > network but that presents a problem as I am at a complete loss how to > install the software and configure it in such a way that I can simply > access it on my private home network. > Ok. I think you may have missed the key point of Pete's mail: you are almost there and if you're the only user, there's no need to have the reverse proxy, but you *do* need the server to listen on an address which can be reached from the other devices on your home network. It's the "reachable from the other devices on your home network" part which you had not achieved yet in the mail he answered to, because the server was strictly listening to connections from itself. > Is there any guide or lesser known website that lays out what is required > to simply self host the software on a private network without the necessity > of having a domain name? > I'm not aware of any lesser known sites which document it. There's explicitly not a guide on the main site because it might encourage people to set up LedgerSMB insecurely. However, in your use-case, getting a certificate is indeed overkill (although you could generate a so called self-signed certificate, which would eliminate the need of owning a domain to go to certbot, but that's a whole can of worms in itself). So, when I know what is your reference documentation and to what step you have completed the instructions, I can probably indicate what you need to do to bind the serverprogram to an external address instead of an internal address. That way it will become reachable from other network devices. Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

nginx Error
by Mathew Cox 19 Feb '22

19 Feb '22

What does this mean? It is a little confusing as it seems to be stating the error is at line 145 but there are only 144 lines in ledgersmb.conf. -- The job identifier is 2922. Feb 19 06:29:00 cathedral nginx[6008]: nginx: [emerg] unexpected end of file, expecting ";" or "}" in /etc/nginx/sites-enabled/ledgersmb.conf:145 Feb 19 06:29:00 cathedral nginx[6008]: nginx: configuration file /etc/nginx/nginx.conf test failed Feb 19 06:29:00 cathedral systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An ExecStartPre= process belonging to unit nginx.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Feb 19 06:29:00 cathedral systemd[1]: nginx.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit nginx.service has entered the 'failed' state with result 'exit-code'. Feb 19 06:29:00 cathedral systemd[1]: Failed to start A high performance web server and a reverse proxy server. -- Subject: A start job for unit nginx.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

2 1

LedgerSMB 1.9.9 released
by Erik Huelsmann 18 Feb '22

18 Feb '22

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains the following fixes and improvements: Changelog for 1.9.9 * Fix sending e-mail due to an incompatibility in Workflow 1.59 (#6413) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.9.9/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.9.9 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.9.9 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.9.9 These are the sha256 checksums of the uploaded files: 04fa0908671ff9eda443a06201655a75c77bae7a553813a1c316c07150f71f77 ledgersmb-1.9.9.tar.gz 2e12443324293a29c6f734e732e1e416fc0b07427d11de3f8babffddd6408a98 ledgersmb-1.9.9.tar.gz.asc

1 0

Refused to connect
by Mathew Cox 18 Feb '22

18 Feb '22

I’m at a loss and I could use some insight. I’m trying to host SMB on a machine on my local network. I’ve followed the installation directions to the nth degree except for the reverse proxy part and I simply cannot connect to the server from my remote machine. I’m clearly missing something and I’m such a novice that I don’t know what it is. I can see from netstat: tcp 0 0 localhost:5762 0.0.0.0:* LISTEN When I’ve tried to connect I’ve entered the following in my web browser: http://192.168.88.15:5762/setup.pl http://192.168.88.15:5762/login.pl http://192.168.88.15:5762 The remote machine is on the same network as I’m constantly configuring the server through ssh. I would love to give more details but I don’t know what you would want. Thank you for bearing with me. Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

2 1

LedgerSMB 1.9.8 released
by Erik Huelsmann 03 Feb '22

03 Feb '22

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains the following fixes and improvements: Changelog for 1.9.8 * Fix regression in editing e-mail fields being discarded (#6168) * Fix regression in CSV download report being mostly empty (#6389) * Fix authentication failure returning incorrect HTTP error number (#6380) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.9.8/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.9.8 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.9.8 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.9.8 Or alternatively from GitHub Container Repository using $ docker pull ghcr.io/ledgersmb/ledgersmb:1.9.8 These are the sha256 checksums of the uploaded files: 79771d2ff354e81f1e7bdd9e910ebdf9573b1eb053012222fc03c76990087424 ledgersmb-1.9.8.tar.gz 4486af371ba01b53caa68a63a3f44727b299ab9a13f6d3ab28a34ef317968d13 ledgersmb-1.9.8.tar.gz.asc

1 0

Re: Template error: Printing Report to PDF or CSV
by Erik Huelsmann 20 Jan '22

20 Jan '22

On Thu, Jan 20, 2022 at 4:11 PM Erik Huelsmann <ehuels(a)gmail.com> wrote: > > Hi Ismail, > > > > We upgraded our LedgerSMB from 1.6 to 1.8 recently. Since the upgrade we could no longer print to pdf or csv. When we try, we get "Template error: file error - display_report: not found at lib/LedgerSMB/Template.pm line 566.". We are getting the same error with LedgerSMB version 1.9.2 and 1.96. but our version 1.6 still works ok. > > > > This is caused by the fact that "downloadable reports are now stored > in the database for customization" as per the release notes > (https://ledgersmb.org/index.php/content/18-release-notes) > > I'd like to direct your attention specially to the "Note for > upgrades", which says that the reports need to be either re-imported > or uploaded into the database. If you have customized document > templates in place, you better upload the missing templates one-by-one > through the System > Templates menu. The minimum set of templates to > import/upload would be "Balance Sheet", "Income Statement" and > "Reports". > > After you have imported/uploaded these, you should be fine with the > report output. > > > Regards, > > -- > Bye, > > Erik. > > http://efficito.com -- Hosted accounting and ERP. > Robust and Flexible. No vendor lock-in. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

2 1

Template error: Printing Report to PDF or CSV
by itadebayo＠gmail.com 20 Jan '22

20 Jan '22

Hi all, We upgraded our LedgerSMB from 1.6 to 1.8 recently. Since the upgrade we could no longer print to pdf or csv. When we try, we get "Template error: file error - display_report: not found at lib/LedgerSMB/Template.pm line 566.". We are getting the same error with LedgerSMB version 1.9.2 and 1.96. but our version 1.6 still works ok. Kindly assist to resolve this issue. Thanks. Ismail

1 0