To be completed by the original poster:
CMS Version
4.0.8
Installation Method
Custom install
Operating System
The operating system the CMS is installed on Linux
Issue
404 Not Found
The application could not run because of the following error:
Details
Type: Slim\Exception\HttpNotFoundException
Code: 404
Message: Not found.
File: /var/www/vhosts/mkcmoto.tv/instoretv.mkcmoto.tv/vendor/slim/slim/Slim/Middleware/RoutingMiddleware.php
Line: 76
Trace
#0 /var/www/vhosts/mkcmoto.tv/instoretv.mkcmoto.tv/vendor/slim/slim/Slim/Middleware/RoutingMiddleware.php(44): Slim\Middleware\RoutingMiddleware->performRouting() #1 /var/www/vhosts/mkcmoto.tv/instoretv.mkcmoto.tv/vendor/slim/slim/Slim/MiddlewareDispatcher.php(121): Slim\Middleware\RoutingMiddleware->process() #2 /var/www/vhosts/mkcmoto.tv/instoretv.mkcmoto.tv/vendor/slim/slim/Slim/Middleware/ErrorMiddleware.php(76): Psr\Http\Server\RequestHandlerInterface@anonymous->handle() #3 /var/www/vhosts/mkcmoto.tv/instoretv.mkcmoto.tv/vendor/slim/slim/Slim/MiddlewareDispatcher.php(121): Slim\Middleware\ErrorMiddleware->process() #4 /var/www/vhosts/mkcmoto.tv/instoretv.mkcmoto.tv/vendor/slim/slim/Slim/MiddlewareDispatcher.php(65): Psr\Http\Server\RequestHandlerInterface@anonymous->handle() #5 /var/www/vhosts/mkcmoto.tv/instoretv.mkcmoto.tv/vendor/slim/slim/Slim/App.php(199): Slim\MiddlewareDispatcher->handle() #6 /var/www/vhosts/mkcmoto.tv/instoretv.mkcmoto.tv/vendor/slim/slim/Slim/App.php(183): Slim\App->handle() #7 /var/www/vhosts/mkcmoto.tv/instoretv.mkcmoto.tv/web/install/index.php(101): Slim\App->run() #8 {main}
Tried the installers from 3.3.9, 4.0.5, 4.0.6, 4.0.7 and 4.0.8
On 2 different physical Plesk servers, with different PHP versions and different Plesk versions, etc…
What does your VirtualHost configuration look like, what is your DocumentRoot?
The error message suggests a possible infinite loop in redirects, as the URL https://instoretv.mkcmoto.tv/web/install/install/install/… implies.
Thanks for your suggestions.
I got it figured out.
The DocumentRoot needs to be updated.
Whoever is on Plesk-servers, it’s very simple to do.
Just add ‘/web’ behind the existing documentroot.
Hello
I don’t know if I should reopen a new topic.
I get the same error message when I try to run the installer on xamp.
My first installation, I had the error that my php version was not recent enough.
So I reinstalled xamp with PHP 8.1
Since then I have this error
a little help?
Hello Mrs. Gabinou,
You can try installing xibo by typing https://localhost/xibo/web/install/index.php/1 on your web browser. I saw the file you sent where you used You can try installing xibo by typing https://localhost:90/xibo/web/install/index.php/
I hope this solves the problem you are experiencing
Best regards,
Ray
Hello,
I have to use ports other than 80 because this one is already used in my company. I use 81 on mamp but I couldn’t use xibo on this one, hence why I downloaded xamp.
I still have the same problem despite my settings.
thank you beforehand
Is your DocumentRoot accurately configured? It should direct to the designated web folder / directory within Xibo.
Follow these steps to change XAMPP DocumentRoot (use correct path):
- Open the XAMPP Control Panel.
- Navigate to
Apache → Config → httpd.conf.
- Locate the following lines:
DocumentRoot "C:/xampp/htdocs"
<Directory "C:/xampp/htdocs">
- Modify them to reflect your new folder path:
DocumentRoot "C:/xampp/htdocs/xibo/web/"
<Directory "C:/xampp/htdocs/xibo/web/">
- Ensure that the contents residing within the designated web directory of the Xibo archive you have acquired are situated within the file path
"C:/xampp/htdocs/xibo/web/".
- Restart Apache.
Will requests directed to http://example.com:81 be seamlessly routed, or are there potential blockages in place? Furthermore, what about SSL requests targeting port 443? Presumably, your organization utilizes SSL connections on that port.
(Instead of resorting to additional port definitions, it would be more optimal for your company to serve the Xibo CMS under a subdomain and manage routing internally. This approach would facilitate a smoother experience, enabling the utilization of a dedicated subdomain such as xibo.example.com, eliminating the need to contend with URLs like http://example.com:81/ and https://example.com:443/.)
