[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
installed ledgersmb-1.3.23-1 on debian-6.0.6, access denied
- Subject: installed ledgersmb-1.3.23-1 on debian-6.0.6, access denied
- From: ario <..hidden..>
- Date: Fri, 02 Nov 2012 08:16:40 +0000
I'm in the process of upgrading to ledgersmb 1.3 from 1.2.21 and for
that purpose I (did) set up a brand new VM with debian 6.0.6 ("squeeze")
installed as a headless server.
The VM is running in an x86_64 kvm (on a Fedora 17 running AMD 64 bit
machine) and setup from a netinstall.iso image as a basic-only install.
So there's no server, no graphics UI etc.
On top of this totally clean system, I (only) installed
ledgersmb-1.3.23-1 using apt-get, but am not able to access the
ledgersmb page from my browser.
The apache2 server itself works ("It Works!", it says in the browser),
but browsing to ledgersmb/login.pl and/or ledgersmb/setup.pl gives me a
I listed the whole procedure that I followed below (I think it's
basically the default one), and would be very pleased with any help on
this one that can get me further.
After installing the basic debian 6.0.6 (squeeze) system from within
netinstall.iso, the VM was rebooted and the following procedure was
1. Edit apt-get's sources.list to add sid main:
# nano /etc/apt/sources.list
deb http://ftp.de.debian.org/debian sid main
was added as suggested on
2. Then I run
# apt-get update
# apt-get upgrade
# apt-get dist-upgrade
(just to be sure :)
# apt-get install ledgersmb
3. Then, for configuring ledgersmb, "Automatic" was chosen
4. A LedgerSMB database administrative user & password were given
5. Configure database for ledgersmb with dbconfig-common?: yes
6. The password for ledgersmb to register with the database server were
given (ident based authentication has not specifically been initiated by
7. # service apache2 restart
was invoked due to a short message passing by, mentioning that it would
be necessary. Didn't read quite fast enough to see wether this was
already automatically done by the script, but considered it not
dangerous if apache were restarted again.
It "could not reliably establish the domain name" so the script chose to
use 127.0.0.1 instead, which seemed ok to me.
8. Then the PostgreSQL application password for ledgersmb was given when
9. From ifconfig the VM's IP was found (192.168.122.95 in this case).
10. In the (proxy-less) browser on the host where the VM resides, the
apache2 server's was entered ( http://192.168.122.95 ) resulting in a
screen, saying that it works, but that no content had been added yet.
11. Going to http://192.168.122.95/ledgersmb and
http://192.168.122.95/ledgersmb/setup.pl however, I get:
You don't have permission to access /ledgersmb/setup.pl on this server.
Apache/2.2.22 (Debian) Server at 192.168.122.95 Port 80"