Sorry Bill: I meant to send it to the list :-0
Please see the network info I've added, in response to both Bill and Erik.
On Mon, Mar 18, 2019 at 6:45 PM Xboxboy Mageia <xboxboy.mageia(a)gmail.com>
I was sick over Xmas, and since then business has been booming, only now
can I have a second look. Thank you all for you help.
On Thu, Jan 10, 2019 at 10:38 AM bill Ott <billott(a)theotts.org> wrote:
Running "brctl show" w/o/ the quotes on
the VM's host will show you the
bridge and the interfaces that are connected to it. 'ifconfig" w/o the
quotes on the VM's host will show you the all of interfaces.
bridge name bridge id STP enabled
virbr0 8000:525400da324e yes
enp5s0 is on 192.168.1.109
lo is on 127.0.0.1
virbr0 is on 192.168.122.1
(sorry can't ssh in at the moment, let me know if you need all the details)
Might help chasing down the problem.
Email: Mailto:email@example.com <billott(a)theotts.org>
On 1/9/19 5:21 PM, Erik Huelsmann wrote:
Ok, so the debian install went simply. I used debian 9 (Stretch), without
'ip addr' gives 192.168.1.101, which sounds right, as that's my lan,
I then followed the instructions on https://apt.ledgersmb.org/index.html
but I installed version 1.5, and did not add the 'test component', I don't
know what that means, sorry.
I was able to add the DB admin user where the
prompt comes up: Now do I
need to reset/config mysql's root user and password also?
So from my desktop I tried to access via firefox
192.168.1.101:5762/setup.pl, but it's unable to connect.
Ok. Are you able to ping that ip address from your desktop? That should
indicate if you should expect to be able to connect to the web server as
Yes, I can ping the debian VM with "ping 192.168.1.118"
I can access the
default debian apache web server at 192.168.1.118, but no
luck with 192.168.1.188:5762/setup.pl
I have a functioning fedora os VM on 192.168.1.107 with nextcloud working
I have the VM network set to bridged, networking
is my downfall, and the
other thing I suspect is that I need to open the
firewall for the webserver.
Bridged sounds fine. quick question: Is the "eth0" (or enpXs0 with X a
number) network on the VM's host part of the bridge? If not, you probably
need to enable IP forwarding. Before we go that route, lets start by
checking you can 'ping' the address though. (And: can you ping the host
that the VM is running on?)
I can ping the host with "ping 192.168.1.109"
All advice appreciated.
-- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
users mailing list