On Sat, May 4, 2019 at 1:52 AM Xboxboy Mageia <xboxboy.mageia(a)gmail.com> wrote:
>>
> the browser wont go to http://LedgerSMB/setup.pl
Did you tell the system on which the browser is running, which IP
that 'LedgerSMB' name has? Or put it your local DNS? Also; if you're
using the default setup, you should be using "https", not "http".
And note (in case you don't already know) that browsers like
Chromium really don't like using https with ssl certs like what we're
using by default (a valid ssl cert but not one that is registered
where the browser knows of), but how you get around that and still get
the secure session depends on the browser.
(But yes, despite such dns & ssl issues, we still recommend using
secure broswer session to access the LSMB app.)
> I tried adding the machines IP as the servername, but that didn't work either.
In what way did you try adding it? In the URL?
For instance, although I also have LXCs/VMs running on a local
server, I usually have test containers running on my laptop. And don't
have the networking where those are running accessible outside of the
laptop. So rather than adding the server name for the LXC to the DNS
on the laptop (since the IP can change depending on what other
containers have been started), I just use the IP. For example; if
10.0.0.231 is the IP, then for the LSMB setup login page I would use
https://10.0.0.231/setup.pl. Or, https://10.0.0.231/login.pl for the
login page.
--
Robert J. Clay
rjclay(a)gmail.com
Hi all I sure as hell hope someone can help me.
I have been looking at LedgerSMB now for 2 weeks trying to figure out how I
get this working on a Windows10 PC, and damned if i understand any of it.
I so would love to use this software, sick of paying out thousands of
dollars each year for not much. Ledger SMB from what I have read and seem
on the youtube is perfect it does everything i want and more.
Is there anyone out there that would be willing to give me a hand setting
it up on my PC using TEAMVIEWER.
I live in Australia so you would have to consider the time difference. I am
hoping to do this ASAP so if there is any I would really appreciate your
help.
Thank you
Terry
Greetings!Hello Team, upon configuring the docker command: docker-compose up, i did encounter the following error below:
Starting ledgersmb2019_postgres_1 ... errorERROR: for ledgersmb2019_postgres_1 Cannot start service postgres: network f3a4c456e824f5462dfdedcbb29d41668863f1540aded7bc5c3bd93c2cbec085 not foundERROR: for postgres Cannot start service postgres: network f3a4c456e824f5462dfdedcbb29d41668863f1540aded7bc5c3bd93c2cbec085 not foundERROR: Encountered errors while bringing up the project.PS C:\Windows\System32\ledgersmb2019>
For your kind assistance on how could i successfully run an instance of LSMB thru Docker image.
Warm Regards,/ITD/ Ryle.Msinc/ITDept
Apologies Robert, gmail frustratingly doesn't auto-reply to group :(
On Sat, May 4, 2019 at 3:22 PM Xboxboy Mageia <xboxboy.mageia(a)gmail.com>
wrote:
>
>
> On Mon, Apr 22, 2019 at 7:57 AM Robert J. Clay <rjclay(a)gmail.com> wrote:
>
>>
>>
>> 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:
>>
>> Using the command "hostname" I get "LedgerSMB"
> I've added that to the ledgersmb-1.5-proxy.conf file
>
>
>> a2ensite ledgersmb-1.5-proxy.conf
>>
>> No complaints
>
>
>> 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...)
>>
>> the browser wont go to http://LedgerSMB/setup.pl
>
> So, I'm tripped up again: Sorry.
>
> I tried adding the machines IP as the servername, but that didn't work
> either.
>
> Any questions/comments/concerns etc, please let us know.
>>
>>
>> Thanks for your patience... I will get there though.
>
>>
>> --
>> Robert J. Clay
>> rjclay(a)gmail.com
>>
>