I'm not familiar with an ET folder ever being in osTicket. It sounds to me like a path got munged... I personally think that I would nuke the database and restart.

Some "stuff" just manages to find me :

"Nuke the database"... do you mean to DROP the mySQL database or more?

I guess I just have a black cloud hanging over my head :(

While awaiting a reply I decided to start the install fresh and recreate everything... (good practice ;))... and report problems as they occur...

Downloaded a fresh copy from the OST web site, uploaded it and proceeded with the install...

When I reached the install.php screen and clicked on some of the ? buttons it displayed the tips box but NO verbiage... since I get notified of all 404 errors on my web site, I checked and there was one: /osticket/setup/tips.html

That file does not exist anywhere... decided to stop and resolve this before continuing on...

The problem seems to be surrounding a disagreement between the DOCUMENT_ROOT given by your http server software and the actual location of the main.inc.php file.

Could you temporarily modify main.inc.php on line 63-68 to look like this and send the var_dump output? (Basically, just add the var_dump call)

$here = substr(realpath(dirname(__file__)),

strlen($_SERVER));

// Determine the path in the URI used as the base of the osTicket

// installation

if (!defined('ROOT_PATH'))

define('ROOT_PATH', str_replace('\\', '/', $here.'/')); //root path. Damn directories

var_dump(array(

"DOCUMENT_ROOT" => $_SERVER,

"main.inc.php" => realpath(__file__),

"(root)" => realpath(dirname(__file__)),

));

OK, done... ran /osticket/setup, clicked on ?balloon... where would I find the var_dump you want sent?

Sorry, I missed the part about the tips. My request was in reference to the first post. I can confirm that the tips.html file is missing from the download zip file. I'm in the process of fixing that and releasing a new download file.

It doesn't concern the actual installation, though. You should be able to install the system without the tips.html file.

OK, I will then proceed with the install and then run things from there... and respond with what is displayed...

Thanks!

OK, I will then proceed with the install and then run things from there... and respond with what is displayed...

Thanks

OK, after the install I ran /osticket/spc/admin.php and here is the resulting screen display:

array(3) { => string(38) "/kunden/homepages/43/d151159610/htdocs" => string(53) "/homepages/43/d151159610/htdocs/osticket/main.inc.php" => string(40) "/homepages/43/d151159610/htdocs/osticket" }

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /homepages/43/d151159610/htdocs/osticket/main.inc.php) in /homepages/43/d151159610/htdocs/osticket/include/class.ostsession.php on line 43

Warning: session_regenerate_id(): Cannot regenerate session id - headers already sent in /homepages/43/d151159610/htdocs/osticket/include/class.staff.php on line 671

Warning: Cannot modify header information - headers already sent by (output started at /homepages/43/d151159610/htdocs/osticket/main.inc.php) in /homepages/43/d151159610/htdocs/osticket/include/class.http.php on line 35

Warning: Cannot modify header information - headers already sent by (output started at /homepages/43/d151159610/htdocs/osticket/main.inc.php) in /homepages/43/d151159610/htdocs/osticket/include/class.http.php on line 36

Warning: Cannot modify header information - headers already sent by (output started at /homepages/43/d151159610/htdocs/osticket/main.inc.php) in /homepages/43/d151159610/htdocs/osticket/include/class.http.php on line 37

Warning: Cannot modify header information - headers already sent by (output started at /homepages/43/d151159610/htdocs/osticket/main.inc.php) in /homepages/43/d151159610/htdocs/osticket/include/class.http.php on line 38

Warning: Cannot modify header information - headers already sent by (output started at /homepages/43/d151159610/htdocs/osticket/main.inc.php) in /homepages/43/d151159610/htdocs/osticket/include/class.http.php on line 39

Valid CSRF Token Required

AND still getting the 404 errors when attempting to login.... /et/ problem as described above.....

Is apache chrooted into /kunden? I'm not sure where '/kunden' went in the location of main.inc.php

I really can't answer that... this is a hosted system and I have NEVER had issues installing many other apps that needed the "root full path....", etc AND "knuden" has always been part of that path...

My host is 1and1.com

Could you try replacing this block

$here = substr(realpath(dirname(__file__)),

strlen($_SERVER));

// Determine the path in the URI used as the base of the osTicket

// installation

if (!defined('ROOT_PATH'))

define('ROOT_PATH', str_replace('\\', '/', $here.'/')); //root path. Damn directories

with this one

#Set Dir constants

$root = str_replace('\\', '/', realpath(dirname(__file__)));

$root2 = str_replace('\\','/', $_SERVER);

$path = '';

while (strpos($_SERVER, $root) === false) {

$lastslash = strrpos($root, '/');

$path = substr($root, $lastslash) . $path;

$root = substr($root, 0, $lastslash);

}

// Determine the path in the URI used as the base of the osTicket

// installation

if (!defined('ROOT_PATH'))

define('ROOT_PATH', $path.'/'); //root path. Damn directories

You can remove the var_dump line as well

OK, made the change and tried logging into ADMIN (/osticket/scp/admin.php) and could not login.. keep getting the login screen with an error "Authentication Required"... trying /osticket/ it works fine, which it did not yesterday

Was this error encountered accessing the helpdesk by http://localhost/...?(http://localhost/...?)

NO.... by http://myWebSite/osticket/scp/admin.php(http://myWebSite/osticket/scp/admin.php)

Well another 'twist'..... for the past few days every time I tried to login I encountered the 'authentication.... ' error and it would loop back to request the login info....

TODAY (a few minutes ago) I tried to login again and lo and behold I am met with an different error .... not sure but something to the effect that my previous login had timed out (if this happens again I will remember to get the exact wording)... so I attempted a login again and IT WORKED!!!

We shall see if this continues to work.... and hopefully it will give you another CLUE as to where the problem lies....