Have had a bit of a play this evening with no joy. Looking
at both your posts:
I changed VBOXWEB_HOST to :: - didn't see any change to
any of the issues I was having
I can get the apache2 home page up by going to
192.168.2.60 - works fine
I can get webmin up by going to 192.168.1.60:10000 - works
fine
My VirtualBox is installed at /var/www/vb and going to
192.168.1.60/vb just gives me "Not Found. The requested URL
/vb was not found on this server."
I don't have a vbox.log in /var/log/ - I do have
vboxwebservice.log though this didn't show anything untoward
(It did include a line "New SOAP thread started" - no other
references to SOAP)
I'm still of the view that this is going to be something
pretty dumb that I have done to myself.
Any particular things I should be checking first to ensure
all things are running ? I wouldn't be surprised to find I
haven't got the process running which is why it might be
difficult to connect to :-)
Thanks,
Rob
----- Original Message Follows -----
Rob,
Can you check the contents of /var/log/vbox.log? (i.e. cat
/var/log/vbox.log)
I suspect you'll find the last line looks something like:
Steve,
Have had a bit of a play this evening with no joy. Looking
at both your posts:
any of the issues I was having
192.168.2.60 - works fine
fine
192.168.1.60/vb just gives me "Not Found. The requested URL
/vb was not found on this server."
vboxwebservice.log though this didn't show anything untoward
(It did include a line "New SOAP thread started" - no other
references to SOAP)
I'm still of the view that this is going to be something
pretty dumb that I have done to myself.
Any particular things I should be checking first to ensure
all things are running ? I wouldn't be surprised to find I
haven't got the process running which is why it might be
difficult to connect to :-)
Thanks,
Rob
----- Original Message Follows -----