FAQ - Install & Connect
First Server Connections
You have created your account, installed your modules, but you can not connect your application with Splash?
Stay calm, the solutions are surely here!
Module Self-Test?
For each module you install, an automatic test sequence is present. The results of these tests are usually visible on the module configuration page. Its purpose is to make sure that the module is working properly on your server and that the configuration is valid. During the test sequence, the module will test to ping and connect with your Splash account. If everything has gone normally, you will see messages of this type.
Self-Test - Remote Client Ping Failed
If your module failed to reach your Splash account, you will see this error.
-
Check that you have entered the correct identifier of your server. Without any additional character.
-
If you have enabled the advanced configuration mode of the module, make sure that the address of the Splash server is correct.
-
Ensure that your hosting allows outgoing connections, that there is no firewall, proxy, or other security that may prevent the module from communicating with the outside.
Self-Test - Remote Client Connection Failed
If your module failed to connect to your Splash account, you will see this error.
-
Check that you have entered the security key of your server. Without any additional character.
My server is declared but do not answer
You have correctly configured your server but once declared, can not refresh the data? Some points to check to ensure proper operation.
-
Check that the declared address is accessible and that it corresponds to the Splash webservice. If the address is not accessible, the module has not been able to detect its location. In this case, check the configuration of your server.
Error : Response not of type text/xml: text/html
More technical, this error indicates the format of the data returned by your server (text/html) does not correspond to that expected by Splash (text/xml). In most cases, you will get this error if your server uses the HTTPS protocol.
- HTTPS
-
If your server requires a connection via the HTTPS protocol and you have not enabled this option on the server form, you may see this error. Activate the HTTPS mode to restore communication.
If you are not in this case, be aware this error isn't due to a wrong configuration of your server, but to default configurations that require the server to responds with in text/html format.
-
NGINX -
If you are using a NGINX server, open your server's configuration file and look for the add_header Content-Type text/html; line. If you find it, delete it...
location ~ .php$ { ...add_header Content-Type text/html;... } -
APACHE -
Even rarer, if you're using an APACHE server, it is also possible that the response type was forced. To solve it, browse your configuration files, but also your .htaccess files, looking for a ForceType text/html directive. If you find it, delete it ...
...ForceType text/html...