-
Notifications
You must be signed in to change notification settings - Fork 40
Troubleshooting
In case of errors, first check most common errors below.
If none of those help with your problem, do following steps before reporting new issue:
-
Check for configuration file errors
Modify script "
backend/check.php
" and enable the script as instructed in the file. Open url in your browser:http://yourhost/backend/check.php
. If the script tells that file is OK, continue with other steps. Otherwise correct the problem as instructed, and try again. -
Enable server side logging by adding following settings in
configuration.php
:$CONFIGURATION = array( ..., "debug" => TRUE );
This enables detailed logging in the backend, and it will be written in PHP error log file. If you don't know where this file is, ask your service provider.
In case that service provider does not allow access to the log file, custom log file can be set up with following:
$CONFIGURATION = array( ..., "debug" => TRUE, "debug_log" => "/kloudspeaker/debug.log", // CHANGE THIS );
The debug log file path must be located in a folder where PHP has read and write permissions. Using absolute path is recommended.
-
Recreate the error situation
-
Get the log
Get the debug log from PHP error log, or from custom log file (if defined).
Optionally, log can be retrieved with browser:
http://yourhost/backend/r.php/debug
. This option applies only to admin users, and the log is emptied every time this url is opened. -
Copy the debug info and attach into error report
NOTE! Once the logs are reported, remember to disable server side debug logging option as it generates lots of log entries.
Error "Cannot modify header information, headers already sent" means PHP output is started prematurely before the Kloudspeaker session is initialized.
Error "Got malformed JSON response" means response is received to the client, but it's format is not valid.
Usually these are due to following content in configuration.php
file:
- there are extra characters outside php tags: spaces, line feeds, tabs etc. There must be nothing before or after "
<?php
" and "?>
" - the file has been saved in UTF-8 without BOM information
Some features, like sharing file links, requires the public URL to access the resources. If possible, Kloudspeaker will try to resolve this, but in some cases this information is not available.
In this case, you need to define this manually with setting "host public address", see option host public address
Error "Parse error: syntax error, unexpected '{'
" occurs when PHP version is lower than the minimum required.
With IIS server, JSON file downloads may require configuration:
- make sure "Application Development Features" are enabled
- make sure JSON file type has mime type configured (application/json)
Kloudspeaker uses REST HTTP protocol for the requests, which means all HTTP methods (ie. GET, PUT, POST and DELETE) must be supported by the web server. If these are not supported, many operations will fail (error in the server log indicate protocol error or missing resource).
To fix this, Kloudspeaker can be set to operate on limited HTTP methods mode.
Kloudspeaker operates on UTF-8, so all the data handled must be in UTF-8. First make sure your Kloudspeaker web page is set to display UTF-8 content, with following tag in head section:
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
If this is correct, then most likely your filesystem does not operate on UTF-8 (usually Windows). In this case you need to configure charset conversion:
-
If you are using MySQL, make sure the charset used is UTF-8. See Configuration.
-
Setup conversion as instructed in configuration
-
Enter the Godaddy Hosting Control Center
-
Choose settings-file extensions management-default extensions
-
In the table that is presented edit ".php" Runs under "PHP 5.2.x" (instead of "PHP 5.2.x FastCGI")
- Add "
include 'Sabre/DAV/UUIDUtil.php';
" inSabre.includes.php
- Ensure write access in both "
temp
" and "data
" folder
Make sure configuration.php
does not have any characters outside <?php
- ?>
tags, including spaces or line feeds. These characters are interpreted as output, and will corrupt file downloads.
See troubleshooting step 1 to check your configuration.php
.
- Home
- Installation
- Migration from Mollify
- Configuration
- Client configuration options
- Backend configuration options
- Languages
- Uploader
- Troubleshooting
- Plugins
- Quota
- History
- File viewer editor
- Registration
- Comments
- Share
- Archiver
- Item details
- Notificator
- Event logging
- Lost password
- Item collection
- Trash bin
- WebDAV
- Permissions
- Security
- External interface
- Command line interface
- Customizations
- Resources
- Client resource map
- Development
- Client modules
- Plugin
- Creating UI
- Client API
- Development environment
- Change log