IguanaCMS - The first ever CMS written in FreeBasic

[Julcar]

Yes, the linux compiler script is a bit outdated and needs to be fixed, what I need is some more spare time xD

This shouldn't be the build script. I think it's the code itself is not tested on Linux and to some extern being Windows only. I'm not sure, though.

The missing functions are implemented based on WINAPI, a #if 0 before every function name should do the trick

[nehakakar]

Mmm, make sure you have enabled Rewrite Module in httpd.conf, if that does not work, you could look if apache is running under administrator privileges.
My experience says that apache is very tricky when executing this kind of binary cgi, especially on Windows

What about nginx? Is it a little easier? Not only me but other reported .htaccess is ignored in XAMPP/WAMPP (don't blame Laragon because it was derived from those). Nginx has Windows version, it's a zip. Could you try Nginx and give a step by step guide? Thank you.

https://nginx.org/en/download.html

(I tried to use TinyWeb Server but it doesn't work or I don't know how to configure it but it expects an index.html not index.exe).

Nginx does not support CGI, only FastCGI and SCGI (I have plans to implement SCGI in the future)
In the other side, to get Tinyweb working you have to create a blank index.html in root and copy index.exe to cgi-bin, then you can init http://127.0.0.1/cgi-bin/index.exe
Alternatively you can use the "refresh" meta tag to redirect automagically to cgi-bin/index.exe
Note that if using Tinyweb, you must change in settings.json the site_fancy_url property to false, as Tinyweb does not support url rewrites
Other alternative is Hiawatha Webserver which supports cgi and url rewrite (I can supply a config file if needed)

Check sitelist.json is in the same folder as index.exe and correctly configured with the base path where '/data' can be found. This may resolve the 403 Forbidden error when accessing http://127.0.0.1/users/register.html or live url.
Manually test, Use browser developer tools to inspect network requests and redirects or use any online tool like redirect checker  This can help you to get detail redirection report might help pinpoint the issue.