Micro Collection API with Nginx returns error 500 on non basic endpoints (url's)

it seems like loader "problem"

i dont see where you define where phalcon should load your controller files

https://docs.phalcon.io/en/3.2/loader#registering-namespaces

PHP message: PHP Fatal error: Class 'Ot\Controllers\Api\V1\Web\Bq\AnnouncementsController' not found in /home/runcloud/webapps/ot-api-1/public/index.php on line 49

You should check your loader.php if the class was properly registered.

Thanks @Izo and @Lajos for responding.

I find it strange that Nginx doesn't load the controllers correctly while Apache does.

This is my loader.php file:

<?php

$loader = new \Phalcon\Loader();

/**
 * We're a registering a set of directories taken from the configuration file
 */
$loader->registerDirs(
    [
        $config->application->controllersDir,
        $config->application->modelsDir,
    ]
)->register();

$loader->registerNamespaces(
    [
        //EXAMPLE     "Example\Base"    => "vendor/example/base/",        USAGE     $var = new Example\Base();
        'Ot\Controllers\Api\V1' => APP_PATH . '/controllers/v1/',
        'Ot\Models' => APP_PATH . '/models/',
        'Ot\Vendors' => $config->application->vendorDir,
    ]
)->register();

Structure of application:

• app
• • collections
• • • v1
• • config
• • controllers
• • • v1
• • • • AuthController.php
• • • • ControllerBase.php
• • • • web
• • • • • bq
• • • • • • AnnouncementsController.php
• • public
• • • index.php
• • models

Head of ControllerBase.php

<?php

namespace Ot\Controllers\Api\V1;

class ControllerBase extends Controller
{

Head of AuthController.php

<?php

namespace Ot\Controllers\Api\V1;

class AuthController extends ControllerBase
{

Head of AnnouncementsController.php

<?php

namespace Ot\Controllers\Api\V1\Web\Bq;

class AnnouncementsController extends \Ot\Controllers\Api\V1\ControllerBase
{

HAH! Im guessing your apache is a local setup on win, and nginx is the live server on nix.

Make sure that physical paths and namespace path case matches from the origin of registration, since nix systems are case-sensitive.

Try renaming v1/web/bq to v1/Web/Bq. You can leave v1 as it is the root folder of the namespace registration.

HAH! Im guessing your apache is a local setup on win, and nginx is the live server on nix.

Make sure that physical paths and namespace path case matches from the origin of registration, since nix systems are case-sensitive.

Try renaming v1/web/bq to v1/Web/Bq. You can leave v1 as it is the root folder of the namespace registration.

My Apache is indeed used on a Windows development machine. I can't believe this was the issue. Thank you so much for your help!

Changing the setHandler of a collection endpoint after the V1 to lowercase did the trick for me!

Another one. I wonder will devs ever learn that Windows will only cause you problems. Use Virtualbox or some containers next time and save your time and energy.

I'm glad that was the only issue, and you can deploy your app!

P.S. I'd suggest you change a bit in your nginx confing and Router component: instead of: try_files $uri $uri/ /index.php?_url=$uri&$args; modify to: try_files $uri $uri/ /index.php$is_args$query_string;

Router in services:

$di->setShared('router', function (){
// Phalcon\Mvc\Router has a default behavior that provides a very simple routing that always expects a URI that matches the following pattern: /:controller/:action/:params

        $router = new \Phalcon\Mvc\Router(false); //Create the router without default routes

        //we're using Front Page Controller pattern in relation from nginx -> Phalcon
        $router->setUriSource($router::URI_SOURCE_SERVER_REQUEST_URI); // Use $_SERVER['REQUEST_URI']

        //Set whether router must remove the extra slashes in the handled routes
        $router->removeExtraSlashes(true);

    return $router;
});

Of course, it's up to you whenever you want to use default routes or not, but for API it's not required, so I'd disable it.