Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now

http error 500

Hi, i need your help because i have problem when i create a ticket, i have message error : 
This page does not work

Unable to process this request... HTTP ERROR 500


I have OVH.

How to resolve please ?

Comments

  • Please help us to help you by reading and following the posting guidelines located in this thread: Please read before requesting assistance.  The more information you give us the better we will be able to assist you. Thank you.

    What is OVH?
    Also Please consult your Apache and PHP error logs and provide any errors that are being logged.
    • PHP Error log entries or displayed errors : /
    • Mail Sending: phpMail functions
    • Mail Fetching/Receiving: Server version
    • version d'osTicketv1.10.1 (9ae093d) —  A jour
      Logiciel serveur WebApache
      Version de MySQL5.5.55
      Version PHP5.6.30
    • Hosting : OVH
  • And the Apache error logged error?
  • where can I find this information ?
  • The only people that can tell you that are: you or your system administrator or your webhost.

  • yes i have a problem between OS TICKETS and WORPRESS, you know ?
  • osTicket has nothing to do with Wordpress, so no I have no idea what you are talking about.
  • why OSTICKET do error http 500 ?
  • Quite plainly osTicket does not "do error http 500", your webserver does.

    The 500 Internal Server Error is a very general HTTP status code and means that something has gone wrong on the websites server.  It is incredibly generic. 

    You will need to consult your Apache error logs to get a more detailed explanation of why your webserver is throwing this error.
  • OSTICKET don't work with hosting OVH !
  • If a software works or not is depending on the environment and its configuration
    When the hoster you have chosen has designed his environment in a way that prevent that osticket is running well than you have to contact your logs to see what is going wrong.

    With this information you can ask the forum for more help.

    Then you can try to fix this by yourself (if your web panel let you do this necessary changes) or you must speak to OVH if they can make the changes or see why this happens.

    This is the normal procedure of running web apps in an hosting environment. This is not osticket specific.
    You should know where the logs are and how you can access them. 
    This is important for running software successfully..
  • How to show mode debug to see errors please ?
  • Like ntozier explained to you "You will need to consult your Apache error logs to get a more detailed explanation of why your webserver is throwing this error."

    This the place where you have can find more about the error. Look at your web interface for your hosting to find this log or ask your hoster.

  • i find no errors in apache !!!!! how to see mode debug ?
  • I think that you not consulted the error log from your webserver maybe you mixed it up with the access log (which won't help you).
    With the error log from your webserver you could debug your issue.
  • apache error : 

    error apache.txt
    15K
  • edited September 27
    I recommend taht you contact your host.   The only 500 in the whole file is 

    109.190.254.1 removed.pro - [27/Sep/2017:19:28:30 +0200] "POST /open.php HTTP/1.1" 500 25 "http://removed.pro/open.php" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0"
    My guess is that PHP is throwing an error and logging is turned off (since you didn't provide us with PHP error logs).
  • The content of the log looks for me like the access log of your hosting.
    In my hosting interface there are separate logs: one for errors (error log) and one for all requests processed by the web server (access or weblog).

    I would be very surprised if ovh handles that differently.
    Don't know in which country your hosting is, but the german ovh site clearly describes that the error log is separate from the access log.

    You make it really hard to help you..


Sign In or Register to comment.