Not Found The requested URL was not found on this server. - Printable Version +- HelpDeskZ Community (http://community.helpdeskz.com) +-- Forum: HelpDeskZ 2 (http://community.helpdeskz.com/forum-3.html) +--- Forum: Support (http://community.helpdeskz.com/forum-5.html) +--- Thread: Not Found The requested URL was not found on this server. (/thread-2302.html) |
Not Found The requested URL was not found on this server. - naguibihelek - 07-31-2022 I’ve recently migrated to a CWP server from CPanel, and I had a couple of issues:
I’ve tried a restore from backup but ended in the same boat. Any suggestions would be appreciated? Thanks. Nagui RE: Not Found The requested URL was not found on this server. - cord.schneider - 08-01-2022 (07-31-2022, 10:13 PM)naguibihelek Wrote: I’ve recently migrated to a CWP server from CPanel, and I had a couple of issues:It's not clear what you mean by "rename it". Helpdeskz requires the .htaccess file because it uses Apache's rewrite engine. If you've renamed the file, you'll have to rename it back to .htaccess. If your .htaccess file contains things added by CPanel/CWP you can create a new one using the following: https://github.com/helpdesk-z/helpdeskz-dev/blob/master/.htaccess RE: Not Found The requested URL was not found on this server. - naguibihelek - 08-01-2022 Thanks Cord. I recreated it with sample you provided and I get a "Whoops! We seem to have hit a snag. Please try again later..." I also tried a fresh install using Softaculous and still could not create a working environment. Not sure what else to try. I used Softaculous on old system and everything worked fine. I must be missing something which is required, but all prerequisites are in place. Nagui RE: Not Found The requested URL was not found on this server. - cord.schneider - 08-04-2022 And you're definitely using Apache? If I was troubleshooting this I would start with the server logs. From reading through the Helpdeskz code, it's clear that this error message is shown when an exception is encountered. Obviously, from the error message, it's not clear what exception that might be but it's going to be quite low-level. So start with the server logs and see what errors are thrown. Next, try enable CodeIgnitor debug mode and check out the CodeIgnitor logs. |