New Installation ViciBox v.8.1

[ammar]

Hello Everyone,

I have installed fresh new installation of Vicibox 8.1 on my VM, After completing the installation following the from the manuals (http://download.vicidial.com/iso/vicibo ... nstall.pdf) i am getting error opening its GUI. Can you please assist?

https://imgur.com/a/U7h3fLY

[thephaseusa]

If you pointed your browser to the correct web address, then you didn’t install apache on your server, or it’s not running now.

systemctl status apache2

If its installed but not running:

systemctl start apache2

If its installed but not enabled:

systemctl enable apache2

If its not installed you can install it yourself or run vicibox-install again

[williamconley]

If you pointed your browser to the correct web address, then you didn’t install apache on your server, or it’s not running now.

Um ... not true. The response "not found on this server" wasn't referring to the Web Software, but to the page he tried to surf to. Which means apache is running, apache tried to find the page he requested, but he entered a URL that does not exist. You don't get a "404" from a NONrunning web server. 404 not found is an actual web server response. If apache isn't running, you get "Unable to connect" (which is a Browser message) instead.

So, he could be on the wrong server (ie: the domain shown could be pointed to a different IP address) or he just entered the wrong URL. It's also possible his apache configuration is messed up and that URL doesn't exist as a result. But with the information available the ONLY information we have is that whatever he typed did not point to a valid web page on whatever server responded.

Showing the full url would be helpful. For instance: http://viciboxtest.mdkjapan.com/vikidial/welcome.php wouldn't work because it's vicidial, not vikidial. But we can't see the URL.

I've even had some instances where the local /etc/hosts file on the requesting workstation had an overriding IP address which hijacked the domain name and sent the request to the wrong server.

But make no mistake: Whatever server replied to that request *did* have apache running. Note that the last word on the 404 page was ... "Apache" in italics.