[Bug]: API enabled and 404 not found

[nlarenti]

Describe the problem

Good morning, I enabled the APIs as documented at: https://docs.poweradmin.org/configuration/api/
I'm attaching a configuration extract:

'api' => [
'enabled' => true,                              // Enable API functionality (including API keys)
'basic_auth_enabled' => false,           // Enable HTTP Basic Authentication for public API endpoints
'log_requests' => true,                       // Log all API requests
 'docs_enabled' => true,                      // Enable API documentation at /api/docs endpoint

making the call from the application or with curl (after configuring the API Keys inside the web console you get the error:
{"error":"Not Found","message":"The requested resource was not found","status":404}.

Analyzing the error.log and access.log file of Apache, we can see:
==> error.log <==
[Tue Sep 02 00:32:17.242684 2025] [php:notice] [pid 474:tid 474] [client XXX.XXX.XXX.XXX] Class \Poweradmin\Application\Controller\Api\v1\ZonesController not found
[Tue Sep 02 00:32:17.242707 2025] [php:notice] [pid 474:tid 474] [client XXX.XXX.XXX.XXX] #0 /var/www/poweradmin/index.php(68): Poweradmin\Application\Routing\BasicRouter->process()\n#1 {main}

==> access.log <==
2a01:4f8:2191:308d:b10:127:240:17 - - [02/Sep/2025:00:32:17 +0200] "GET /api/v1/zones HTTP/1.1" 404 414 "-" "curl/7.88.1"

The Apache configuration, as per the documentation, includes:

<Directory /var/www/poweradmin>
                Options -Indexes +FollowSymLinks
                AllowOverride All
                Require all granted
</Directory>

Steps to reproduce

Launch:
curl -H "X-API-Key: pwa_95d529f91615afaf3036fdc38cdccbbc3a4804e4d534e4100ffc010b6a7d1ec4" -H "Content-Type: application/json" https://dns.mydomain.com/api/v1/zones

Poweradmin version

4.0.1

Database

PostgreSQL

Additional information (optional)

No response

[edmondas]

@nlarenti The provided .htaccess file is insufficient. Please refer to the one in the released version branch. While the next version will include a simplified .htaccess configuration, the current version requires a more detailed setup.
https://github.com/poweradmin/poweradmin/blob/release/4.0.x/.htaccess

[edmondas]

Documentation updated - apologies for the confusion. I couldn't implement the transition to a minimal .htaccess file in the current release due to the number of features already in place.
https://docs.poweradmin.org/installation/manual/#important-apache-htaccess-file

[SirGrady]

Hiya,

is one of those .htacces files found at https://docs.poweradmin.org/installation/manual/#important-apache-htaccess-file supposed to work on padmin 4.0.1 ?
If so, this issue should be re-opened as I still get {"error":"Not Found","message":"The requested resource was not found","status":404}

Regards,
Grady

[edmondas]

@nlarenti The router was generating lowercase v1 in the namespace, but the actual controller classes are in the uppercase V1 directory. Fixed the case mismatch so API endpoints can find their controllers.

@SirGrady .htaccess file from the 4.0.x branch should work, as I use it for local API testing.

[SirGrady]

hmm, I can't get it to run. I see /api/docs thou, but yet 404 resource not found. Doesn't matter if I use curl or the swagger page.

In apache error logs i get:

[...] [php:notice] [...] Class \\Poweradmin\\Application\\Controller\\Api\\v1\\ZonesController not found
[...] [php:notice] [...] #0 /var/www/dmgmt-test.test-dom.de/docs/index.php(71): Poweradmin\\Application\\Routing\\BasicRouter->process()\n#1 {main}

apache setup:

<VirtualHost *:80>
    ServerName  dmgmt-test.test-dom.de
    Redirect    permanent / https://dmgmt-test.test-dom.de/
</VirtualHost>


<VirtualHost *:443>

    ServerName      dmgmt-test.test-dom.de
    DocumentRoot    /var/www/dmgmt-test.test-dom.de/docs

    ErrorLog  ${APACHE_LOG_DIR}/dmgmt-test.test-dom.de-error.log
    CustomLog ${APACHE_LOG_DIR}/dmgmt-test.test-dom.de-access.log combined

    SSLEngine on

    SSLCertificateFile      /etc/apache2/ssl/dmgmt-test.test-dom.de/cert.pem
    SSLCertificateKeyFile   /etc/apache2/ssl/dmgmt-test.test-dom.de/key.pem
    SSLCertificateChainFile /etc/apache2/ssl/dmgmt-test.test-dom.de/chain.pem

    SSLProtocol All -SSLv2 -SSLv3
    SSLHonorCipherOrder On
    SSLCompression off

    <Directory /var/www/dmgmt-test.test-dom.de/docs>
        Options -Indexes +FollowSymLinks
        AllowOverride All
		Require all granted
    </Directory>

</VirtualHost>

settings.php

    'api' => [
        'enabled'               => true,
        'basic_auth_enabled'    => false,
        'basic_auth_realm'      => 'DNS Management API',
        'log_requests'          => true,
        'docs_enabled'          => true,
    ],

this

curl -v -H "X-API-Key: pwa_5e53ebed75c6954796ddbbcf3301ca2078757185a314d99724924f189e8aaf0b" \
     -H "Content-Type: application/json" \
     https://dmgmt-test.test-dom.de/api/v1/zones

results in this:

* Uses proxy env variable no_proxy == '10.245.16.41, test-dom.de, 127.0.0.1'
* Host dmgmt-test.test-dom.de:443 was resolved.
* IPv6: (none)
* IPv4: 10.245.16.41
*   Trying 10.245.16.41:443...
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=dmgmt-test.test-dom.de
*  start date: Sep 11 11:49:52 2025 GMT
*  expire date: Dec 10 11:49:51 2025 GMT
*  subjectAltName: host "dmgmt-test.test-dom.de" matched cert's "dmgmt-test.test-dom.de"
*  issuer: C=US; O=Let's Encrypt; CN=E8
*  SSL certificate verify ok.
*   Certificate level 0: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA384
*   Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* Connected to dmgmt-test.test-dom.de (10.245.16.41) port 443
* using HTTP/1.x
> GET /api/v1/zones HTTP/1.1
> Host: dmgmt-test.test-dom.de
> User-Agent: curl/8.14.1
> Accept: */*
> X-API-Key: pwa_5e53ebed75c6954796ddbbcf3301ca2078757185a314d99724924f189e8aaf0b
> Content-Type: application/json
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* Request completely sent off
< HTTP/1.1 404 Not Found
< Date: Sat, 20 Sep 2025 12:00:05 GMT
< Server: Apache
< Set-Cookie: PHPSESSID=eb2d2a487ad3934dcdf0fc0672cdc530; path=/; secure; HttpOnly
< Expires: Thu, 19 Nov 1981 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate
< Pragma: no-cache
< Content-Length: 83
< Content-Type: application/json
<
* Connection #0 to host dmgmt-test.test-dom.de left intact
{"error":"Not Found","message":"The requested resource was not found","status":404}# 

[edmondas]

@SirGrady The 'Class not found' error should be resolved with the routing fix in 39132a6. I'm planning to make a patch release soon (4.0.2), so maybe you could try then. Another option is to rename the lib/Application/Controller/Api/V1 folder to lib/Application/Controller/Api/v1 (lowercase v), but this might introduce other issues.