Solved “No input file specified” error after installing UVdesk

[sergiisav]

After the installation, I was getting a “No input file specified” error. To fix it, I’ve changed this

RewriteRule ^(.*)$ ./index.php/$1 [QSA,L]

To this

RewriteRule ^(.*)$ ./index.php?/$1 [QSA,L]

in .htaccess as was suggested on the internet.

Which helped, but I’ve got another problem.

It resulted in 500-error for Ajax on this page
/en/member/agents

Somehow, the XHR request URL looks like this: http://<mydomain>/en/member/agents/xhr?%2Fen%2Fmember%2Fagents%2Fxhr=

NOTE: Everything works fine if I add “index.php” in the URL itself. E.g.:
http://<mydomain>/index.php/en/member/agents
Then the XHR request looks like:
http://<mydomain>/index.php/en/member/agents/xhr

I feel like I'm missing some simple stuff, but can't Google anything for over 4 hrs already... Any help? Thanks!

[peopleinside]

@sergiisav I'm glad you resolved, thanks for sharing what worked for your case.
The suggested .htaccess content here should work:

<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^(.*)$ ./index.php/$1 [QSA,L]
    RewriteCond %{HTTP:Authorization} ^(.*)
    RewriteRule .* - [e=HTTP_AUTHORIZATION:%1]
</IfModule>

But can be maybe ok if you simply applied the same code used in Wordpress.

[peopleinside]

Hi @sergiisav ,
have you tried to look at the following post?
https://forums.uvdesk.com/topic/1925/installing-and-setup-uvdesk-for-the-first-time/3?_=1643926600411

[peopleinside]

@sergiisav You should add more details for be helped.

• What version of UVdesk have you installed?
• What PHP version are you running?
• How did you installed UVdesk: SSH, Control Panel, Softacolous, FTP?

After the installation you get the first error when: when you logged in in the dashboard?
You added htaccess file? If so maybe if you add some wrong code you can get 500 server error, maybe check error server log can help.

[sergiisav]

Hi @peopleinside ! Thanks a lot for your quick replies.
I've tried the thread you've mentioned, but it didn't help. I've tried to apply this suggestion several ways:

Option #1

<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteCond %{REQUEST_FILENAME} !-f
    #RewriteRule ^(.*)$ ./index.php?/$1 [QSA,L]
    RewriteCond %{THE_REQUEST} ^GET.*index\.php [NC]
    RewriteRule (.*?)index\.php/*(.*) /$1$2 [R=301,NE,L]
    RewriteCond %{HTTP:Authorization} ^(.*)
    RewriteRule .* - [e=HTTP_AUTHORIZATION:%1]
</IfModule>

This resulted in 404 errors for any page I am trying to access.

Option #2

<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^(.*)$ ./index.php?/$1 [QSA,L]
    RewriteCond %{THE_REQUEST} ^GET.*index\.php [NC]
    RewriteRule (.*?)index\.php/*(.*) /$1$2 [R=301,NE,L]
    RewriteCond %{HTTP:Authorization} ^(.*)
    RewriteRule .* - [e=HTTP_AUTHORIZATION:%1]
</IfModule>

This didn't make any difference from the original problem that I've faced with XHR acting weird. Everything works except XHRs, e.g. at the Agents page.

---

I'll try to give more insights into our setup below:

• I believe this is UVdesk 1.0.17
• PHP 7.4.27
• I've installed UVdesk via SSH, using composer and this guide https://www.uvdesk.com/en/blog/open-source-helpdesk-installation-on-ubuntu-uvdesk/
• I have my virtual host pointing right into /public folder
• The htaccess was already in place after installation, I didn't add it manually
• The first error "No input file specified." I got right away, when accessing the website root. It is shown for any URL, if I don't manually add "index.php" to the URL
• I've just added a question mark to this line:

RewriteRule ^(.*)$ ./index.php?/$1 [QSA,L]

As per some suggestions on Symphony forums.

Any suggestion where to dig?

Thanks in advance!

[peopleinside]

@sergiisav thanks for the reply.

You should run the latest UVdesk version that is 1.0.18 and should be showed on the footer of the operator Dashboard.

If you installed UVdesk recently the latest version mentioned should be the version that is running on your instance.

If your server point directly to the public folder maybe you don't need set the .htaccess rule.. but you setup this pointing to the public html folder after the installation?

You are getting an error just when you log-in into the operator Dashboard and load agent activity page? All other functions (user and operator interface) are working without errors?

If so you may try to debug the issue: How to debug errors by activating the dev mode (if you are not) then load the page that give errors and made a screenshot of the error showed. Be sure no personal info is present but should not.

Also checking your server error logs can help to understand what server logs say about error 500 your server may encountered.

Consider that PHP 7.4 will be soon deprecated:https://www.php.net/supported-versions.php
also if security patch are provided for other 9 months. Do you have the possibility to try if the same issue is present by running PHP 8.0 or PHP 8.1?

[sergiisav]

@peopleinside thanks for your help! The dev mode was already enabled, and I was basically digging through the logs trying to understand the issue.
Anyways, it seems to be the htaccess issue, not something PHP-wise.

Accidentally, I've got everything working by applying part of the default WordPress htaccess file

Maybe this will help somebody. Here is my public/.htaccess file:

<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    RewriteCond %{HTTP:Authorization} ^(.*)
    RewriteRule .* - [e=HTTP_AUTHORIZATION:%1]
</IfModule>

Thanks a lot! I think this can be closed as Solved

[peopleinside]

@sergiisav I'm glad you resolved, thanks for sharing what worked for your case.
The suggested .htaccess content here should work:

<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^(.*)$ ./index.php/$1 [QSA,L]
    RewriteCond %{HTTP:Authorization} ^(.*)
    RewriteRule .* - [e=HTTP_AUTHORIZATION:%1]
</IfModule>

But can be maybe ok if you simply applied the same code used in Wordpress.