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.
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
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
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.plhttp://192.168.88.15:5762/login.plhttp://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
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
