Skip to main content

No input file specified. on new account

Comments

14 comments

  • DarkxPunk
    Hey there, So I built a php script for a client on one of my other domains, tested working. Created a new account for them on my server and copied over the script. Now I get No input file specified. No additional changes have been made to php, and everything works on every other account. This an error on account creation or what am I missing? Thanks!

    To add more I went through the logs and see the following [Sun Feb 11 16:17:29.533959 2018] [proxy_fcgi:error] [pid 6427] [client 99.230.xxx.xx:65484] AH01071: Got error 'Unable to open primary script: /home/candycutlery/example.com/submitDebug.php (No such file or directory)\n', referer: http://www.example.com/indexDebug.html
    Now when I check /home/candycutlery/example.com/submitDebug.php I clearly see the file there... I am terribly confused.
    0
  • rpvw
    I would hazard a guess your path is wrong. In cPanel a standard webroot would be /home//public_html/~ and all the html, css and php etc files would be in this folder or in a sub folder of this location. So unless the full path looks like : /home//public_html/home/candycutlery/example.com/submitDebug.php it probably will never work unless you change the default webroot for the domain (which I would strongly advise against doing) If you are running this in a sub domain, you will need to change the Document root in your cPanel Subdomains section for this folder. If this is an Addon domain, set the Document root in the Addon Domains section for this folder. Looks like you have some rearranging of your files to do :-D Hope this helps.
    0
  • DarkxPunk
    I would hazard a guess your path is wrong. In cPanel a standard webroot would be /home//public_html/~ and all the html, css and php etc files would be in this folder or in a sub folder of this location. So unless the full path looks like : /home//public_html/home/candycutlery/example.com/submitDebug.php it probably will never work unless you change the default webroot for the domain (which I would strongly advise against doing) Looks like you have some rearranging of your files to do :-D

    I am aware the default is /home/username/public_html/ I change all my accounts domains to the root of /username/ so in this case /home/candycutlery/example.com/ I can confirm it exists cuz I can look right at it in both the file manage and FTP. I have done this with all my other users on my server and never had an issue. This is a brand new account I created and first time ever I have had this error. Also you can confirm my root change worked because you can visit the website.
    0
  • rpvw
    I change all my domains to the room of /username/

    You obviously know far more about it than I do, as you state that you are already running some special and non-standard file structure to serve your files out of. Sorry I couldn't help.
    0
  • DarkxPunk
    You obviously know far more about it than I do, as you state that you are already running some special and non-standard file structure to serve your files out of. Sorry I couldn't help.

    No worries mate :) - Thanks for the input.
    0
  • rpvw
    This might help: No input file specified
    0
  • DarkxPunk
    Sadly still no go from that post. No Cpanel staff with any clues?
    0
  • DarkxPunk
    Hey everyone, So found a solution after doing a ticket. Problem was my PHP-FPM did not update the change, which we are unsure as to why. So if you ever create an account and this happens again here is the fix: "/opt/cpanel/ea-php70/root/etc/php-fpm.d/example.com.conf" and you are changing: php_admin_value[doc_root] = "/home/user/example.com" then: /usr/local/cpanel/scripts/php_fpm_config --rebuild All solved. If anyone knows why the account had to be updated manually however that would be great :).
    0
  • cPanelMichael
    Hello, I'm glad to see the issue was solved. Thank you for sharing the outcome. As far as the document root change, what method did you use to change the document root for the domain name? Thank you.
    0
  • Miguel G
    I am having the same issue, I had to manually edit the /opt/cpanel/ea-php70/root/etc/php-fpm.d conf file. And some accounts that I had move the main domain to somewhere else in the public_html folder got broken. The Ticket ID is 9573999
    0
  • cPanelMichael
    Hello @Miguel G, Per the support ticket, it looks like the following case in cPanel & WHM version 70 should address the issue you reported: Fixed case CPANEL-18184: Rebuild PHP-FPM config for subdomain document root changes. Thank you.
    0
  • Miguel G
    So in WHM 70 can I move main documentroot somewhere than public_html without suffering this issue anymore?
    0
  • cPanelMichael
    So in WHM 70 can I move main documentroot somewhere than public_html without suffering this issue anymore?

    Hello @Miguel G, Internal case CPANEL-18184 ensures the PHP-FPM configuration is now automatically rebuilt upon changing the document root of a subdomain. Can you verify how exactly you are changing the document root so we can verify this case will solve your specific issue? Thank you.
    0
  • WisTex
    So I built a php script for a client on one of my other domains, tested working. Created a new account for them on my server and copied over the script. Now I get No input file specified. No additional changes have been made to php, and everything works on every other account. This an error on account creation or what am I missing?

    I had a similar issue, but a slightly different cause. I thought I would mention it in case someone has a similar issue. If you are transferring the files over from another server, especially a Windows Plesk server, you might have also copied over config files with server specific values. In my case, there was a user.ini file that had references to the C:\ drive, which obviously does not exist on the Linux server. I deleted that file, and the "No input file specified" error went away. Even if you are not transferring from a Windows server, your previous Linux server might have had a different directory structure and put that in the config files. Look for:
    • .htaccess
    • user.ini
    • web.config
    Edit or delete as appropriate. You probably need the ,htaccess, but the user.ini and web.config probably aren't needed. Pro Tip: Rename the file instead of deleting it if you are not sure of its effect. That way you can easily restore it if it didn't fix the issue as you expected. Note: If you ever transfer the same script to a Windows server, you'll need the web.config again most likely, since .htaccess doesn't work on Windows.
    0

Please sign in to leave a comment.