Error 404 on Login. api/authenticate and /api/login return a 404 in web console.

[Likogann]

Describe the bug
POST https://192.168.0.101/api/authenticate 404 (Not Found)
POST https://192.168.0.101/api/login 404 (Not Found)

To Reproduce
Steps to reproduce the behavior:

1. Go to Login Page
2. Fill out user/pass "admin", "admin"
3. Check console, error 404.
4. Files do not exist on the server as well.

Expected behavior
Login should occur normally, and files should exist.

Screenshots

Please complete the following information:

• OS: Pop!_OS 20.10
• Browser: Chrome 90.0.4430.93 (Official Build) (64-bit)
• Version: v1.0.2

Additional context
I downloaded v1.0.2.zip, and extracted the files to /var/www/TaskBoard.
I'm using NGINX. Conf:

server {
listen 80;
listen 443 ssl;

    server_name tasks.webbly.dev panel 192.168.0.101;

    root /var/www/TaskBoard;

    location / {
            try_files $uri $uri/ $uri.html index.html index.php =404;
    }

}

I've looked through many issues, and couldn't find anything helpfull.
I have also tried re-install taskboard. Install process:

1. install v1.0.2.zip file
2. Extract in /var/www/TaskBoard
3. sudo chmod +777 api

PHP version installed: 7.2

Notice how the files DON'T exist on the server. I'm not sure what it's trying to call, but it's not there.

[steve-shadbolt]

I am seeing the exact same issue. To test that the htaccess RewriteRule is working I have directed my browser to "TaskBoard/api/login" and get this displayed:

{ message: "Matching API call not found." }

This is generated by the re-written URL target index.php, so I am confident that my "AllowOverride" setting is correct and "mod_rewrite" is loaded.

The "login" and "authenticate" targets seem to be something to do with JWT. Does this indicate I have something JWT related missing from my Apache 2.2 web server ?

TaskBoard 1.02, PHP 7.4, Apache 2.2. FPM running on Synology NAS

[doergeph]

I have exactly the same problem after the installation. Did you find a solution?

[steve-shadbolt]

Hi @doergeph . Unfortunately I did not find a solution, so I have switched to using Kanboard instead. For what I wanted, it seems the same as TaskBoard, and worked first time.

[XeroXer]

From what I can tell the problem @Likogann is having is because they are running nginx, which with the default setup is not supported out-of-the-box. The "files" should not exist, there is an .htaccess file that in apache redirects all traffic in the /api/ directory for a file that does not exist, to the /api/index.php. Since nginx does not read .htaccess files this has to be done in the server-block in the nginx configuration.

My nginx config right now has two location blocks for TaskBoard:

location / {
    try_files $uri $uri/ /index.html;
}
location /api/ {
    try_files $uri $uri/ /api/index.php;
}

Then I also have a location block catching all the php-files but that one looks a bit different on different systems so some internet searching might come up with a good match for you.
This is in no way a supported setup by TaskBoard but has been working for me with nginx.

From what I can tell the problem @steve-shadbolt is reporting has something to do with apache and is not the same issue.